accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-2313) Accumulo Tablet Server failed to retain lock with ZooKeeper
Date Tue, 10 Jun 2014 15:42:01 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser resolved ACCUMULO-2313.
----------------------------------

    Resolution: Cannot Reproduce

Insufficient information presently to pursue this any further. Please re-open if you have
more information to support the problems you were seeing.

> 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.2#6252)

Mime
View raw message