[
https://issues.apache.org/jira/browse/HBASE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277622#comment-13277622
]
Anoop Sam John commented on HBASE-6015:
---------------------------------------
My doubt was like below
One region found to be problematic and it is fixed. In the rerun we should
recheck this region right. Now the timelag factor can apply and can remove this
region from checking in the rerun [If this region fix has changed the modtime
of the HRegionInfo]
Also at the 1st run some of the regions might have been excluded because those
are changed recently [As per the timelag value] In the rerun do we need to
check those regions? What if those at this time check happens and reports some
issues? Will it look like for the use that the HBCK was not able to fix the
issues which it reported in the 1st run?
These are my thought after seeing the timelag concept... Pls correct me if my
understanding is wrong :)
> HBCK rerun should check all the regions which it checked in the first run
> -------------------------------------------------------------------------
>
> Key: HBASE-6015
> URL: https://issues.apache.org/jira/browse/HBASE-6015
> Project: HBase
> Issue Type: Bug
> Components: hbck
> Reporter: Anoop Sam John
>
> When after the 1st round of run and possible fixes, HBCK does a rerun to
> check the consistency of the regions. At this rerun
> 1.It should check all the regions which it checked in the 1st round.
> 2.It should check only those regions which it checked in the 1st round. Might
> be some other regions can come out of the timelag check at rerun time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
