[ACCUMULO-1568] Make configuration changes Atomic

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Assignee: Christopher Tubbs
• Reporter: Keith Turner
• Created: 12/Jul/13 16:08
• Updated: 20/Oct/20 17:19
• Resolved: 20/Oct/20 17:19

Description

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.

Issue Links

• is duplicated by: ACCUMULO-1067 InstanceOperations.setProperty / getSystemConfiguration inconsistent state
• is related to: ACCUMULO-3591 Update FATE serialization to use a serialization library
• is related to: ACCUMULO-3530 alterTable/NamespaceProperty should use Fate locks
• is related to: ACCUMULO-2757 millions of zookeeper watches
• is related to: ACCUMULO-2861 Make all config stored in zookeeper human readable
• relates to: ACCUMULO-3842 [UMBRELLA] Remove non-transient data from ZooKeeper

Sub-Tasks

• Serialize table configs into a single ZK node: Resolved
• Create API for updating multiple properties at once: Resolved