Based on the Zookeeper logs, Zookeeper was active from 11:18am to 12:02pm PT. There was a period of 1h 12m where there are no logs for Zookeeper, then at 1:15pm PT, Zookeeper has the internal message to signal it should start processing again. The inactive period corresponds to when the user was AFK. Potentially this means that if ZDS disconnects from ZK, the conversation won't resume until re-activated, similar to engine connections. Ideally we shouldn't drop the Zookeeper connection so that Zookeeper can finish its task in a timely manner.
slack thread
Based on the Zookeeper logs, Zookeeper was active from 11:18am to 12:02pm PT. There was a period of 1h 12m where there are no logs for Zookeeper, then at 1:15pm PT, Zookeeper has the internal message to signal it should start processing again. The inactive period corresponds to when the user was AFK. Potentially this means that if ZDS disconnects from ZK, the conversation won't resume until re-activated, similar to engine connections. Ideally we shouldn't drop the Zookeeper connection so that Zookeeper can finish its task in a timely manner.
slack thread