hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-18059) The scanner order for memstore scanners are wrong
Date Tue, 16 May 2017 14:01:04 GMT
Duo Zhang created HBASE-18059:

             Summary: The scanner order for memstore scanners are wrong
                 Key: HBASE-18059
                 URL: https://issues.apache.org/jira/browse/HBASE-18059
             Project: HBase
          Issue Type: Bug
          Components: regionserver, scan, Scanners
    Affects Versions: 2.0.0
            Reporter: Duo Zhang
             Fix For: 2.0.0

This is comments for KeyValueScanner.getScannerOrder
   * Get the order of this KeyValueScanner. This is only relevant for StoreFileScanners and
   * MemStoreScanners (other scanners simply return 0). This is required for comparing multiple
   * files to find out which one has the latest data. StoreFileScanners are ordered from 0
   * (oldest) to newest in increasing order. MemStoreScanner gets LONG.max since it always
   * contains freshest data.
  long getScannerOrder();

As now we may have multiple memstore scanners, I think the right way to select scanner order
for memstore scanner is to ordered from Long.MAX_VALUE in decreasing order.

But in CompactingMemStore and DefaultMemStore, the scanner order for memstore scanner is also
start from 0, which will be messed up with StoreFileScanners.

This message was sent by Atlassian JIRA

View raw message