You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Glenn Primmer (JIRA)" <ji...@apache.org> on 2014/02/03 21:01:14 UTC

[jira] [Created] (ACCUMULO-2313) Accumulo Tablet Server failed to retain lock with ZooKeeper

Glenn Primmer created ACCUMULO-2313:
---------------------------------------

             Summary: Accumulo Tablet Server failed to retain lock with ZooKeeper
                 Key: ACCUMULO-2313
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2313
             Project: Accumulo
          Issue Type: Bug
          Components: tserver
    Affects Versions: 1.5.0
         Environment: 40 Node Cluster
Each Node: 64GB RAM, 8 Cores (2.4 GHz) , 4x1.5TB drives, 10 Gb/s Ethernet
            Reporter: Glenn Primmer


On 3 Nodes the Accumulo Tservers did not communicate with ZooKeeper within the timeout period and therefor lost their locks.  Looking at the resource utilization (Nagios) it did not appear that the node CPU/resource utilization was a factor as to why Accumulo Tservers did not communicate with ZooKeeper within the timeout period.

Question is, is there potential thread contention for the thread responsible for retaining the ZooKeeper lock in the Accumulo Tservers?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)