[
https://issues.apache.org/jira/browse/HBASE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547009#comment-13547009
]
Anoop Sam John commented on HBASE-6015:
---------------------------------------
Another place where the timelag is checked is Getting the table names and
checking whether to be skipped.
One doubt I got after going through the code is
we just consider the Meta modTime of the 1st region to tell table is ignored.
Actually in the consistency check regions are skipped not entire table.
Also there it consider the HDFS modtime.
That area is left as it is as of now. Any way that is being used just to
display the details. No functional issues as such
> 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
> Assignee: Anoop Sam John
> Attachments: HBASE-6015_94.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
