VerneMQ broker with 3 nodes A,B and C is deployed in Kubernetes with clustering enabled. Assume that a client x is connected to Node B and sends data.
Due to some issues (say interface loading failed), data updater plant is requesting VMQ plugin to disconnect the client and the VMQ load balancer lands the request in Node A (where the actual client is connected to Node B), and the client disconnection is not happening. Disconnection is success only when the request is received by the Node where the client is connected (Node B in this case).
As per my understanding, when clustering is enabled, the disconnect request will be propagated to all the nodes in the cluster leading to successful disconnection of the client.
Am I missing any configuration here ? Any help would be much appreciated !
VerneMQ broker with 3 nodes A,B and C is deployed in Kubernetes with clustering enabled. Assume that a client x is connected to Node B and sends data.
Due to some issues (say interface loading failed), data updater plant is requesting VMQ plugin to disconnect the client and the VMQ load balancer lands the request in Node A (where the actual client is connected to Node B), and the client disconnection is not happening. Disconnection is success only when the request is received by the Node where the client is connected (Node B in this case).
As per my understanding, when clustering is enabled, the disconnect request will be propagated to all the nodes in the cluster leading to successful disconnection of the client.
Am I missing any configuration here ? Any help would be much appreciated !