I have vertx.io 3.1.0 server which does clustering using vertx-zookeeper (3.0.0 ) . The zookeeper server is on 3.4.6.
My ui app uses vertxbus.js client to talk to vertx.io server and registers for various addresses. These addresses get saved in zookeeper. When I looked at the traffic between vertx and zookeeper
I got events on vertx server from zookeeper stating that /subs has changed.
first one was because the socket id was added to /subs
second one was because the ui socket registered for an address echo.101 which also got added to /subs
This causes the vertx server to getAllChildren of /subs twice
Our concern is on the performance of this flow as we are expecting 10s of thousands of users to use our app . They will be opening sockets and registering for various addresses. This will cause constant nodechildrenchange event for /subs which will cause all our vertx nodes to go fetch the children of /subs again and again.
I have vertx.io 3.1.0 server which does clustering using vertx-zookeeper (3.0.0 ) . The zookeeper server is on 3.4.6.
My ui app uses vertxbus.js client to talk to vertx.io server and registers for various addresses. These addresses get saved in zookeeper. When I looked at the traffic between vertx and zookeeper
I got events on vertx server from zookeeper stating that /subs has changed.
This causes the vertx server to getAllChildren of /subs twice
Our concern is on the performance of this flow as we are expecting 10s of thousands of users to use our app . They will be opening sockets and registering for various addresses. This will cause constant nodechildrenchange event for /subs which will cause all our vertx nodes to go fetch the children of /subs again and again.
Am I interpretting this correctly ?
Thanks