[jira] [Commented] (CURATOR-359) Curator can't connect to Read Only ensemble

["Cameron McKenzie (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CURATOR-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700332#comment-15700332 ] 

Cameron McKenzie commented on CURATOR-359:
------------------------------------------

[~benjamin.jaton] Could you please run a jstack on your JVM when it's in the 2 minute blocked state?

> Curator can't connect to Read Only ensemble
> -------------------------------------------
>
>                 Key: CURATOR-359
>                 URL: https://issues.apache.org/jira/browse/CURATOR-359
>             Project: Apache Curator
>          Issue Type: Bug
>    Affects Versions: 3.2.1
>            Reporter: Benjamin Jaton
>            Assignee: Jordan Zimmerman
>            Priority: Critical
>         Attachments: TestCuratorRetry.java, output.txt
>
>
> 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).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)