[CURATOR-359] Curator can't connect to Read Only ensemble

Open jira-importer opened this issue 9 years ago • 2 comments

The read requests fail when connecting to a read only ensemble.

I made a class for this using TestingCluster, but it requires to set iptables rules in order to mimic a real (remote) read-only ensemble. The test will do this:
1) start a TestingCluster
2) stop 2 of the 3 nodes
3) user has to run the iptables commands (specified in the logs)
4) a read request is issued every 3 seconds

All the read requests block for approx 2 minutes, then they all throw an exception (ConnectionLoss).

Originally reported by benjamin.jaton, imported from: Curator can't connect to Read Only ensemble

assignee: randgalt
status: Open
priority: Critical
resolution: Unresolved
imported: 2025-01-21

Nov 23 '16 23:11 jira-importer

benjamin.jaton:

code+output

Nov 23 '16 23:11 jira-importer

cammckenzie:

Benjamin Jaton Could you please run a jstack on your JVM when it's in the 2 minute blocked state?

Nov 27 '16 21:11 jira-importer