accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3147) Replication table should be user-controlled or live in accumulo namespace
Date Thu, 18 Sep 2014 23:19:34 GMT


Josh Elser commented on ACCUMULO-3147:

So context/confirmation -- yes, the replication table is lazily created. Early on, I had tried
to automate creating this table which has a bunch of pain behind it (initialization and upgrades
suddenly get changed). Creating it before users need it also could create some confusion about
why it even exists (rightfully so).

I really don't want to introduce special credentials to be used for replication (I think the
tracer configuration is currently sub-par with the way it must be configured now). The larger
replication feature needs to write to metadata in addition to the replication table and these
writes are performed by the tabletserver, master or garbage collector which system credentials
really simplifies. I also really don't like requiring manual setup of additional features
(I think configuration is hard enough -- we can hide this). I think putting it in its own
namespace or the system namespace makes the most sense.

> Replication table should be user-controlled or live in accumulo namespace
> -------------------------------------------------------------------------
>                 Key: ACCUMULO-3147
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: replication
>            Reporter: Christopher Tubbs
>            Assignee: Josh Elser
>             Fix For: 1.7.0
> At present, it looks like the replication table is managed by/written to by the system
user, yet the table lives in the default namespace, which is where user tables live.
> This appears to violate the namespace model of segregating system tables from user tables.
> There's a few options for resolution:
> # Move the replication table into the reserved accumulo system namespace (there's some
complication with this, because the system namespace is currently static, and the replication
table may be created at any time; additionally, if users are expected to interact with this
table... and I'm not sure if they are at all, the system namespace is probably not appropriate).
> # Create an additional reserved system namespace for replication (my least preferred
> # Use user credentials to manage/write to this table, rather than the system user (this
is what the tracer/trace table does, and this is my preferred solution.)

This message was sent by Atlassian JIRA

View raw message