You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Sam Corbett (JIRA)" <ji...@apache.org> on 2016/11/14 10:50:58 UTC

[jira] [Created] (BROOKLYN-384) ZookeeperEnsemble configuration error

Sam Corbett created BROOKLYN-384:
------------------------------------

             Summary: ZookeeperEnsemble configuration error
                 Key: BROOKLYN-384
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-384
             Project: Brooklyn
          Issue Type: Bug
            Reporter: Sam Corbett


Reported by a user of Brooklyn: 
{quote}
org.apache.brooklyn.entity.zookeeper.ZooKeeperEnsemble started failing with the latest brooklyn build. Further investigation showed that the communication to zookeeper was the issue.

I define a list of zookeeper nodes (comma separated) for my ZK connection url. Looks like: 10.171.106.89:2181,10.176.71.234:2181,10.171.106.68:2181

The issue was that the nodes aren’t talking to each other

So, if my app writes data to 10.171.106.89 on one step, then tries to read it from 10.176.71.234 on the next step, the data isn’t there
{quote}




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