[
https://issues.apache.org/jira/browse/HBASE-17339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15783473#comment-15783473
]
stack commented on HBASE-17339:
-------------------------------
bq. We can add a step-0 where the region queries all relevant stores to
determine if they all maintain monotonicity and if so apply the optimization.
Sounds reasonable?
On each Get or once at startup?
bq. As Phil suggested we can use the TimeRangeTracker at each store to
understand whether or not monotonicity is maintained.
This an existing TRT or a new one (TRT is expensive -- it is our main
contention point writing... FYI).
> Scan-Memory-First Optimization for Get Operation
> ------------------------------------------------
>
> Key: HBASE-17339
> URL: https://issues.apache.org/jira/browse/HBASE-17339
> Project: HBase
> Issue Type: Improvement
> Reporter: Eshcar Hillel
> Attachments: HBASE-17339-V01.patch
>
>
> The current implementation of a get operation (to retrieve values for a
> specific key) scans through all relevant stores of the region; for each store
> both memory components (memstores segments) and disk components (hfiles) are
> scanned in parallel.
> We suggest to apply an optimization that speculatively scans memory-only
> components first and only if the result is incomplete scans both memory and
> disk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
