accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2969) eliminate table watches in clients by using Thrift to find the table map
Date Wed, 02 Jul 2014 15:20:24 GMT

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

Eric Newton commented on ACCUMULO-2969:
---------------------------------------

When accumulo began to support table renames, a lot of tablename -> tableid lookups were
done in client code.  {{Tables}} is used for those lookups.

Given the asynchronous notification of zookeeper, we don't really know the true table state
at the moment a change is made.

How important is it to use zookeeper callbacks to keep the table list current?


> eliminate table watches in clients by using Thrift to find the table map
> ------------------------------------------------------------------------
>
>                 Key: ACCUMULO-2969
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2969
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client, master, tserver
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Minor
>
> Presently, table map information is read directly from zookeeper.  This information is
pulled using the ZooCache, which adds watches to each table znode, and the name znode.  The
shell, in particular, pulls table information to provide table names for tab completion.
> It is surprising that clients have watches on znodes for anything but the root tablet
and the master's lock/address.



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

Mime
View raw message