accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russ Weeks (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2883) Add API method(s) that support fetching currently assigned locations for tablets
Date Sun, 12 Jul 2015 18:13:05 GMT

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

Russ Weeks commented on ACCUMULO-2883:
--------------------------------------

Another 3rd-party use case: I'd love to see functionality similar to HBase's [RegionLocator|https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/RegionLocator.html]
in order to support Accumulo as a storage back-end for Titan.

Titan seems to have some [optimizations to put KV pairs on a local partition of the key space|https://github.com/thinkaurelius/titan/blob/47e9b35efaa4d1eb8722c1db0b1e599336a2c049/titan-hbase-parent/titan-hbase-core/src/main/java/com/thinkaurelius/titan/diskstorage/hbase/HBaseStoreManager.java#L545],
if possible. I'm not sure if this makes sense for Accumulo (or HBase for that matter)... just
trying to follow precedent.


> Add API method(s) that support fetching currently assigned locations for tablets
> --------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-2883
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2883
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Josh Elser
>             Fix For: 2.0.0
>
>
> TabletLocator already exists, but isn't officially a part of the "public API" and is
clunky for users to invoke. In trying to co-locate external processes with the tabletservers
that are hosting some data, it would be nice to have some means that users can invoke that
will return them these assignments.
> Memory concerns are an issue for tables with many splits (e.g. avoiding creating a Set
of 100k tablet locations for a table), but we also want to provide the ability to ask pointed
questions. Likely building something that accepts a Range (or Collection<Range>) would
be best.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message