[
https://issues.apache.org/jira/browse/HBASE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620454#action_12620454
]
Jim Kellerman commented on HBASE-711:
-------------------------------------
> stack - 06/Aug/08 12:57 PM
> IIUC, region A with key a start key of 10 and an end key of 12 will be named
> A,10,12. When it splits, the lower
> halves new name will be A,10,11 which sorts before A,10,12. We don't want
> that, right?
Yes, this is a problem given that we use getRowAtOrBefore. If we exposed
something like getRowAtOrAfter, this would work.. I have been playing around
with strategies that do not require additional APIs, but have not been
successful in constructing a key that would sort to the right spot if we got a
result back that said that the region was split,offline. I think it is do-able,
but just don't have an exact handle on it yet.
> Complain if clock skew across the cluster is badly out of sync
> --------------------------------------------------------------
>
> Key: HBASE-711
> URL: https://issues.apache.org/jira/browse/HBASE-711
> Project: Hadoop HBase
> Issue Type: New Feature
> Reporter: stack
> Assignee: Jim Kellerman
> Priority: Minor
>
> hbase-710 and hbase-609 are issues where the system has broken in presence of
> clock skew over the cluster. Would be a nice service if master could flag
> very bad clock skew. Regionservers could report their local time when they
> ping the master. It could do a compare.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
