accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-715) use curator
Date Fri, 28 Jun 2013 22:39:19 GMT

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

John Vines commented on ACCUMULO-715:
-------------------------------------

8. migrate a lot of the tablet gets into using the cache. There is an additional option down
the road we can do which is using zookeeper to handle some of these tablet events without
the master having to message the tablet to do it. If we trust zookeeper. But that's just food
for thought.
                
> use curator
> -----------
>
>                 Key: ACCUMULO-715
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-715
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master, tserver
>            Reporter: Eric Newton
>            Assignee: John Vines
>             Fix For: 1.6.0
>
>
> Curator seems to have distilled a lot of zookeeper lesson's learned. Consider using it
as our interface to zookeeper.
> Curator advantages:
>  * handles zookeeper retries, via configurable policies
>  * works around some very strange failure scenarios
>  * simplified API
>  * unlike ZooCache and ZooLock, Curator does not need to be maintained by Accumulo developers

--
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

Mime
View raw message