You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2008/07/17 03:24:31 UTC
[jira] Resolved: (HBASE-610) Autoincrementing cell version
[ https://issues.apache.org/jira/browse/HBASE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman resolved HBASE-610.
---------------------------------
Resolution: Won't Fix
With HBASE-711, this should no longer be an issue.
> Autoincrementing cell version
> -----------------------------
>
> Key: HBASE-610
> URL: https://issues.apache.org/jira/browse/HBASE-610
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
>
> HBASE-609 has an example of clock skew making it so master scanner missed edits placed there by a regionserver whose clock was in advance of the masters. There may be other cases lurking where this kind of issue -- two servers are updating a particular row with off-clocks -- may bite us. Could a regionserver that has a clock a long ways behind the running master's clock enter a split record that went in behind the current inforegion cell's version? If so, the master wouldn't see the split.
> One fix would be a new feature where cells had a version that autoincremented.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.