accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3842) [UMBRELLA] Remove non-transient data from ZooKeeper
Date Fri, 22 May 2015 19:10:17 GMT


Josh Elser commented on ACCUMULO-3842:

Thanks for taking a read over this (very) bare outline so far.

bq. I'm not sure how the change proposed would manifest the third benefit you mention (consistent
updates of table props). Can you explain that, please? As I understand it, we use ZooKeeper,
because it has watchers, which we can use to get consistency. I'm not aware of any similar
mechanism with any alternatives.

So, right now, we have eventually consistent configuration updates for tables. We don't know
when the watchers will fire, but (IIRC) we know they will fire in the correct order and ever
server will eventually see all updates.

What we should really have to mimic the API we present is a strongly consistent means to update
configurations. ZooKeeper doesn't keep us from accomplishing this. We would need to write
code to actually get the strong consensus for ourselves. I know this is very hand-wavy at
this point, but I think we're at the point where this is a problem we need to start thinking
about because it's been a repeated problem for ourselves just in writing reasonable tests
for Accumulo for ~2years now.

> [UMBRELLA] Remove non-transient data from ZooKeeper
> ---------------------------------------------------
>                 Key: ACCUMULO-3842
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client, tserver
>            Reporter: Josh Elser
>             Fix For: 1.8.0
> Wanted to start brainstorming about this.
> We store a lot of persistent data in ZooKeeper that would better stored in something
backed by HDFS. ZooKeeper can be a very convenient place to store persisted data so that it's
available to all nodes, but it comes at a price and often must be asynchronously accessed
to achieve good performance.
> * Table/Namespace configuration
> * Users/Authorizations
> * Problem reports (maybe?)
> * System configuration overrides (maybe?)
> Some benefits we'd see from this:
> * Loss of ZooKeeper doesn't lose table configuration and users.
> * Greatly reduce zookeeper watchers (assume watchers=50*num_tables*num_tservers)
> * Consistent updates of table constraints and all other table properties
> The last note is the most important one IMO. The number of test issues alone that we've
had with constraints not being seen on all servers are bound to affect users.

This message was sent by Atlassian JIRA

View raw message