[
https://issues.apache.org/jira/browse/TEPHRA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013324#comment-16013324
]
ASF GitHub Bot commented on TEPHRA-230:
---------------------------------------
GitHub user poornachandra opened a pull request:
https://github.com/apache/incubator-tephra/pull/43
TEPHRA-230 Fix reading of saved regions during invalid pruning run
JIRA - https://issues.apache.org/jira/browse/TEPHRA-230
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/poornachandra/incubator-tephra
feature/fix-invalid-prune
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tephra/pull/43.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #43
----
commit 667144a99cd3863bf68982fb745d15786f294a92
Author: poorna <[email protected]>
Date: 2017-05-17T00:47:15Z
Port to other compat modules
commit daf57aa167c0c6c240ba04642d0c328211cb1b20
Author: poorna <[email protected]>
Date: 2017-05-17T00:51:32Z
TEPHRA-230 Fix reading of saved regions during invalid pruning run
----
> Improve the logic used to find recorded regions during invalid list pruning
> ---------------------------------------------------------------------------
>
> Key: TEPHRA-230
> URL: https://issues.apache.org/jira/browse/TEPHRA-230
> Project: Tephra
> Issue Type: Bug
> Affects Versions: 0.10.0-incubating
> Reporter: Poorna Chandra
> Assignee: Poorna Chandra
> Fix For: 0.11.0-incubating
>
>
> During an invalid list pruning run, the plugin records the regions present on
> the HBase cluster at that time. It also records the count of regions as a
> checksum.
> While reading the list of recorded regions, if the checksum does not match
> the number of regions read at time {{t}}, then the plugin will move on to
> regions at time {{t - 1}}. However, the {{t-1}} computation in inefficient
> today, and leads to microsecond decrements. It can be improved to use the
> time at which the current set of regions were recorded.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)