Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of
 ramkrishna.s.vasudevan@gmail.com designates 209.85.220.50 as permitted
 sender)
MIME-Version: 1.0
Date: Fri, 31 Jan 2014 01:18:41 +0530
Message-ID: 
 <CAAT7MkrCRuJaZbbNGHJgBonsNOTDkn7-uni1PBEkaceuVv3BCg@mail.gmail.com>
Subject: StoreScanner created for memstore flush should be bothered about
 updated readers?
From: ramkrishna vasudevan <ramkrishna.s.vasudevan@gmail.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a1134519a3103a804f13558b7

--001a1134519a3103a804f13558b7
Content-Type: text/plain; charset=ISO-8859-1

Hi All

In case of flush we create a memstore flusher which in turn creates a
 StoreScanner backed by a Single ton MemstoreScanner.

But this scanner also registers for any updates in the reader in the
HStore.  Is this needed?
If this happens then any update on the reader may nullify the current heap
and the entire Scanner Stack is reset, but this time with the other
scanners for all the files that satisfies the last top key.  So the flush
that happens on the memstore holds the storefile scanners also in the heap
that was recreated but originally the intention was to create a scanner on
the memstore alone.

Am i missing something here?  Or what i observed is right?  If so, then I
feel that this step can be avoided.

Regards
Ram

--001a1134519a3103a804f13558b7--