hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-15224) Undo "hbase.increment.fast.but.narrow.consistency" option; it is not necessary since HBASE-15213
Date Fri, 17 Jun 2016 19:52:05 GMT

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

Mikhail Antonov updated HBASE-15224:
------------------------------------
    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.

  was:
HBASE-15031 “Fix merge of MVCC and SequenceID performance regression in branch-1.0 for Increments”
and HBASE-15092 ‘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.


> Undo  "hbase.increment.fast.but.narrow.consistency" option; it is not necessary since
HBASE-15213 
> --------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-15224
>                 URL: https://issues.apache.org/jira/browse/HBASE-15224
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Performance
>            Reporter: stack
>            Assignee: stack
>             Fix For: 1.2.0, 1.1.4, 1.0.4
>
>         Attachments: 0001-HBASE-15224-Undo-hbase.increment.fast.branch-1.2.patch, 0001-HBASE-15224-branch-1.2.patch,
15224.branch-1.2.addendum.patch, 15224.branch-1.2.patch, HBASE-15224.branch-1.2.patch, HBASE-15224v2-branch-1.2.patch
>
>
> 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.



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

Mime
View raw message