[jira] [Created] (OOZIE-1921) Curator client reports connection loss to ZK under high load

["Mona Chitnis (JIRA)" <ji...@apache.org>]

Mona Chitnis created OOZIE-1921:
-----------------------------------

             Summary: Curator client reports connection loss to ZK under high load
                 Key: OOZIE-1921
                 URL: https://issues.apache.org/jira/browse/OOZIE-1921
             Project: Oozie
          Issue Type: Bug
          Components: HA
    Affects Versions: trunk
            Reporter: Mona Chitnis
             Fix For: trunk


Seeing two types of Connection Loss exceptions via Curator when running Oozie in high load

h5. [1] (znode transaction type: delete)
{code}
org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss
        at org.apache.curator.ConnectionState.checkTimeouts(ConnectionState.java:198)
        at org.apache.curator.ConnectionState.getZooKeeper(ConnectionState.java:88)
        at org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
{code}

h5. [2]
{code}
org.apache.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for
/oozie/locks/0037706-140704041907-oozie-oozi-W
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
        at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1472)
{code}

We should probably implement a fallback approach in Oozie while invoking Curator library to handle any inherent limitations. But not able to find much documentation about Curator benchmarks.




--
This message was sent by Atlassian JIRA
(v6.2#6252)