[
https://issues.apache.org/jira/browse/HBASE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689946#action_12689946
]
Onur GUN commented on HBASE-7:
------------------------------
Is is possible that we have a case where forcing flush after the checks is more
appropriate than forcing before? When it should be done?
Let's say we have a region1 having faulty data. We have ran hbasck. It forced
flush and we now have region11 and region12. If region1 did not have faulty
data, we would have only region1. Later the compaction resolved this, but split
and compaction ran for nothing in this region server.
If i am wrong, please point me what to look for.
> [hbase] Provide a HBase checker and repair tool similar to fsck
> ---------------------------------------------------------------
>
> Key: HBASE-7
> URL: https://issues.apache.org/jira/browse/HBASE-7
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: util
> Reporter: Jim Kellerman
> Fix For: 0.20.0
>
> Attachments: patch.txt
>
>
> We need a tool to verify (and repair) HBase much like fsck
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
