You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2016/09/08 20:14:20 UTC

[jira] [Updated] (ACCUMULO-1568) Make configuration changes Atomic

     [ https://issues.apache.org/jira/browse/ACCUMULO-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs updated ACCUMULO-1568:
----------------------------------------
    Fix Version/s:     (was: 1.8.1)
                   2.0.0

> Make configuration changes Atomic
> ---------------------------------
>
>                 Key: ACCUMULO-1568
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1568
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>            Assignee: Christopher Tubbs
>             Fix For: 2.0.0
>
>
> I have not seen this issue, but its something I thought of.  Assume the following happens.
>  * iterators I1 ... I10 are configured to Table T1 at time 1
>  * iterators NI1 ... NI10 are configured to Table T1 at time 2
>  * compaction is reading iterator config and reads I1 ... I5  and NI4 ... NI9, a combination of the two iterator configurations w/o NI10, this could be really bad.
> Seems like this could be solved by use of Zookeeper transactions.   The Accumulo API will need to change to allow setting many iterators or config settings at once.
>  
>  



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