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

stack updated HBASE-609:
------------------------

    Attachment: skew-0.1-v3.patch

Here is new version of patch made after study of all uses of 
System.currentMillis.  Testing, this version of patch fixes HBASE-478, 
"offlining of table does not run reliably"

Please review.

{code}
When we scan, use LATEST_TIMESTAMP rather than currentTimeMillis.
When we use current time, its the time on the machine that is running
the scan.  If clock skew, it may be asking for a view on table that
is behind latest version.  This for sure is problem in catalog tables.

M  src/test/org/apache/hadoop/hbase/MultiRegionTable.java
M  src/java/org/apache/hadoop/hbase/HMerge.java
M src/java/org/apache/hadoop/hbase/HBaseAdmin.java
    Use LATEST_TIMESTAMP opening scanners.
M  src/java/org/apache/hadoop/hbase/HMaster.java
    Use LATEST_TIMESTAMP opening scanners. Also, use new batchUpdate
    method - one that doesn't take a timestamp rather than specify
    current time of this server.
M  src/java/org/apache/hadoop/hbase/HRegionInterface.java
    Added overload of batchUpdate that doesn't take a timestamp
M  src/java/org/apache/hadoop/hbase/HRegion.java
    Use batchUpdate that doesn't take an argument.
M src/java/org/apache/hadoop/hbase/HRegionServer.java
    Add overload of batchUpdate.
{code}

> Master doesn't see regionserver edits because of clock skew
> -----------------------------------------------------------
>
>                 Key: HBASE-609
>                 URL: https://issues.apache.org/jira/browse/HBASE-609
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Priority: Blocker
>             Fix For: 0.2.0, 0.1.2
>
>         Attachments: skew-0.1-v2.patch, skew-0.1-v3.patch, skew.patch
>
>
> The streamy folks had a cluster where regionserver was 2 minutes in advance 
> of the master.  On split, regionserver would update .META. with split info 
> but scanners opened on the master wouldn't see the edits because they were 
> being opened using current time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to