Keyed topic - sample state changes to NOT_ALIVE_NO_WRITERS when a reader is added from a PC with multiple network interfaces

1 post / 0 new
Offline
Joined: 05/18/2018
Posts: 5
Keyed topic - sample state changes to NOT_ALIVE_NO_WRITERS when a reader is added from a PC with multiple network interfaces

Hi,

we have a network cluster with multiple clients and one server. The clients and the server only has one network interface. Information is shared via a keyed topic model. The lease duration of the liveliness QOS is set to 5 seconds. The samples are written periodically with 1Hz.

If a new client is started on a PC with multiple network interfaces the instance state of samples changes to NOT_ALIVE_NO_WIRTERS for a short time. (probably until the same instance is published again)

However, if the same client is started on a PC that only has one network interface it behaves as expected. The instance state of samples published by the server or other clients is not influenced.

I do not have any idea what causes that issues or how to solve it and appreciate any help.

Best regards

Olav