[
https://issues.apache.org/jira/browse/HBASE-11202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007423#comment-14007423
]
stack commented on HBASE-11202:
-------------------------------
An observer CP being able to obtain a row lock made it so Victor Xu was able to
avoid a server-halt in 0.94. Our locking/CP interaction had holes, at least in
his production install.
The sequence id handling/locking is different in trunk. I'd be good w/ letting
go of these methods in HRegion trunk. If an issue arises around sequence ids
and flush, it will have a different form in trunk. Lets address it when we see
it.
> Cleanup on HRegion class
> ------------------------
>
> Key: HBASE-11202
> URL: https://issues.apache.org/jira/browse/HBASE-11202
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.99.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Priority: Minor
> Fix For: 0.99.0
>
> Attachments: 11202.v1.patch
>
>
> This is mostly trivial stuff
> - remove some methods not used
> - typos
> - remove some @param w/o any info
> - change the code that uses deprecated methods
> The only non trivial change is when we get the store from a cell: instead of
> using the map, we iterate on the key set. Likely, it would be better to hava
> a sorted array instead of a Map, as the number of store is fixed. Could be
> done in a later patch.
--
This message was sent by Atlassian JIRA
(v6.2#6252)