[HBASE-7721] Atomic multi-row mutations in META

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.98.0, 0.95.0
• Component/s: Coprocessors, regionserver
• Hadoop Flags: Reviewed
• Tags: 0.96notable
• Assignee: Enis Soztutar
• Reporter: Enis Soztutar
• Created: 30/Jan/13 22:06
• Updated: 15/Oct/13 04:46
• Resolved: 08/Mar/13 19:50

Description

Thanks to Lars' local transactions patch (HBASE-5229), we can entertain the possibility of doing local transactions within META regions.

We need this mainly for region splits and merges. Clients scan the META concurrent to the split/merge operations, and to prevent the clients from seeing overlapping region boundaries or holes in META, we just through hoops. For more backgroun, see BlockingMetaScannerVisitor, HBASE-5986, and my comments at https://reviews.apache.org/r/8716/.

Now, for the actual implementation options:
1. As outlined in http://hadoop-hbase.blogspot.com/2012_02_01_archive.html,

• We have to implement a Custom RegionSplitPolicy for the META regions to ensure that a table's regions are always co-located in the same META region. Then we can add MultiRowMutationEndpoint as a system level coprocessor, and use it for META operations.
  2. Do smt like HBASE-7716, and expose local atomic multi-row operations as a native API.
  3. Move META to zookeeper. Use zookeeper.multi.

Then we can change region split / merge logic to make use of atomic META operations.

Thoughts, suggestions?

Issue Links

• is related to: HBASE-7716 Row Groups / Row Family / Entity Groups in HBase
• relates to: HBASE-7777 HBCK check for lingering split parents should check for child regions
• relates to: HBASE-7748 Add DelimitedKeyPrefixRegionSplitPolicy