Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <178786281.1250135534815.JavaMail.jira@brutus>
Date: Wed, 12 Aug 2009 20:52:14 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-1738) Scanner doesnt reset when a snapshot
 is created, could miss new updates into the 'kvset' (active part)
In-Reply-To: <4972833.1249341434827.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-1738:
-------------------------

    Fix Version/s:     (was: 0.20.1)
                   0.20.0

Moving to 0.20.0.  Bad bug and patch is almost there.

> Scanner doesnt reset when a snapshot is created, could miss new updates into the 'kvset' (active part)
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1738
>                 URL: https://issues.apache.org/jira/browse/HBASE-1738
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: ryan rawson
>            Assignee: stack
>             Fix For: 0.20.0
>
>         Attachments: 1738.patch
>
>
> when a Scanner is created, it creates 2 MemStoreScanners on the kvset and the snapshot (internal names of Memstore)... if the snapshot is originally empty, it only creates the 1, for kvset.  When the snapshot is created, the outstanding Scanners now have a pointer to the tree that is now the snapshot, but no pointer to the kvset.
> When the flush completes, the scanner will reset the memstore scanners and 'see' the new values again.
> If there is a large delay between snapshot and finalization of the flush, there can be a large period of time a scanner doesnt see 'new' values that are being inserted. the canonical 'bad' case where this can do things is the META scanner, and we end up with double assignment.
> The snapshot is really lightweight, it only takes out a small lock in memstore, so im not sure there is an easy mechanism to hook to without building out a bit more code or restructuring the memstore scanner.

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