jira-importer

cammckenzie: No, the only way I could vaguely reproduce the problem was by going through with a debugger. The only time I could really see it being an issue is...

[Originally related to: CURATOR-499]

randgalt: Please provide a PR with the proposed solution.

kenco: From analysing the log files, it looks like the ConnectionState fluctuated between SUSPENDED and RECONNECTED a few times, and was LOST twice. The first time the connection was LOST,...

kenco: Updating the status to major. After a network outage we saw the Curator status was STARTED, but the Zookeeper client was not connected. This resulted in an outage and...

randgalt: I don't understand what the bug is here. Curator status "STARTED" does not mean you are connected. You must look at Curator's ConnectionState. Please see details here: http://curator.apache.org/errors.html No...

kenco: Thanks Jordan Zimmerman - I think the confusion just comes from the lack of good examples or explanation of the behaviour of Curator in different scenarios. We did have...

randgalt: That's mostly correct. However, it depends on lot on the recipes you use. For example, if you use InterProcessMutex you must have a ConnectionStateListener that interrupts your locks when...

kenco: That's perfect - thanks Jordan Zimmerman. Yep, I'll see if I can work up something documentation/example wise and submit it back. It will probably be a week or two...

randgalt: P.S. We have Tech Notes too where things can be clarified: https://cwiki.apache.org/confluence/display/CURATOR/Tech+Notes