You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2013/06/20 22:44:23 UTC

[jira] [Commented] (ACCUMULO-526) LateLastContact test needs to use a real entry in zookeeper

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

Jonathan Hsieh commented on ACCUMULO-526:
-----------------------------------------

fixed in 1.4.1.
                
> LateLastContact test needs to use a real entry in zookeeper
> -----------------------------------------------------------
>
>                 Key: ACCUMULO-526
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-526
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Minor
>
> The LateLastContact attempts to find troubled tservers by noticing that they are failing to respond to status requests.  If a server does not report status, the master attempts to kill it by removing the zookeeper lock.
> The way the current test works, is that it creates a fake lock using zkCli.sh, which is not always present.  It isn't really creating a proper entry in zookeeper anyhow.  It should be re-written to use java code to create a proper entry.
> Reported by Keys Botzum:
> MapR does not normally install a full zookeeper install on each node. Instead we install a zookeeper "client" on each node which is basically the zookeeper JAR file - /opt/mapr/lib/zookeeper-3.3.2.jar. If I set ZOOKEEPER_HOME to /opt/mapr/lib almost everything works fine since Accumulo seems to only need the JAR file at that location. The one exception is the stress.weird.LateLastContact which directly references zkClient.sh (in stress/weird.py) which isn't part of the MapR install. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira