[HBASE-15224] Undo "hbase.increment.fast.but.narrow.consistency" option; it is not necessary since HBASE-15213

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0, 1.3.0, 1.1.4, 1.0.4
• Component/s: Performance

Release Note

HBASE-15031 “Fix merge of MVCC and SequenceID performance regression in branch-1.0 for Increments” and HBASE-15091 ‘Forward-port to 1.2+ HBASE-15031 "Fix merge of MVCC and SequenceID performance regression in branch-1.0 for Increments"’ added a workaround ‘fast-path’ to restore an increment performance regression that came into hbase 1.0 when we unified mvcc and sequence id in HBASE-8763. The workaround became available in hbase-1.0.3 and hbase-1.1.3. The workaround involved setting the flag "hbase.increment.fast.but.narrow.consistency" in your configuration and restarting.

Subsequently, the regression was fixed in HBASE-15213. The fix will be available in hbase-1.0.4 and hbase-1.1.4 when they are released. hbase-1.2.0 has the flag but as it turns out, it is not needed; there is no regression in 1.2.0.

This issue removes the fast-path flag. If set, it will just be ignored.

• Assignee: Michael Stack
• Reporter: Michael Stack
• Created: 06/Feb/16 03:44
• Updated: 18/Jun/16 02:44
• Resolved: 17/Jun/16 21:12

Description

Remove an escape valve no longer needed after HBASE-15213. Remove so folks don't ever have to worry their pretty-little heads about it.

Let the bulk of HBASE-15031 remain, the issue that added "hbase.increment.fast.but.narrow.consistency" because it mostly cleanup we want to keep.