News for hackers. Stuff that matters.
Re:KIP-500: Replace ZooKeeper with a Self-Managed Metadata Q... by coredog64 on Friday August 02, 2019 @06:56PM (#20597348)
We ran into additional troubles based on ZK client bugs in the version that Kafka used. It would only ever resolve the ZK hostname once, at startup. Our workaround required some additional work to allocate an EIP for each host (3 AZs -> 3 EIPs) and then have the ZK host grab the EIP on startup.

Even though Netflix hasn't updated it in a while, Exhibitor was helpful as well, in that it allowed ZK to bootstrap nodes off of state stored in S3. That did come at the cost of an extra 2-3 minutes per node on initial quorum startup.

Re:KIP-500: Replace ZooKeeper with a Self-Managed Metadata Q... by uberduper on Friday August 02, 2019 @09:20PM (#20598016)
Might just need to set networkaddress.cache.ttl=60 in java.security.