I'm wondering how people ensure that their masters stay connected to the ZooKeeper server during long periods of time when no config changes are made. I'm referring specifically to the issues raised in FLUME-60 ( https://issues.apache.org/jira/browse/FLUME-60):
This seems related to long pauses or breakpoints. Disconnecting from ZK is probably reasonable in these conditions, but ideally the connection should be recovered. As an example, after a long pause, a command that modifies ZK state has this error message: Not connected to ZooKeeper: CLOSED I'm trying to think of possible solutions that don't require restarting the master. One idea is to have a test agent periodically issue configuration statements to each master, but are there any other ideas out there? Thanks, Jay
