[ 
https://issues.apache.org/jira/browse/HBASE-27793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728593#comment-17728593
 ] 

Rajeshbabu Chintaguntla commented on HBASE-27793:
-------------------------------------------------

[~apurtell]  sorry for not following the committer guidelines and wasting your 
time and [~zhangduo] s time. Will not repeat the same again.

bq.1. Making this change in HBCK2.
I will work on making the changes in HBCK2 in another JIRA.

bq.2. Reporting unknown servers with informational messages only, not as an 
"inconsistency"

bq,3. Following our current committer guidelines, including paying attention to 
precommit results, including use of spotless.

When there are unknown servers hbck only reports assignment issues of the 
regions held by the server,  fixing those assignment alone doesn't help and may 
cause data loss that's the reason felt would be better to report unknown 
servers as inconsistency, log how to fix the unknown server. Sure will initiate 
the discussion regarding the same in dev@ list and make changes in hbck2 based 
on the conclusion.

bq.4. Proper attention to fix versions.

Sure.

> Make HBCK be able to report unknown servers
> -------------------------------------------
>
>                 Key: HBASE-27793
>                 URL: https://issues.apache.org/jira/browse/HBASE-27793
>             Project: HBase
>          Issue Type: Bug
>          Components: hbck
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>            Priority: Major
>             Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.5
>
>
> Currently hbck is not reporting unknown servers it would be helpful to report 
> those as inconsistencies so that directly hbck2 schedulerecoveries  option 
> can be used to recover on unknown servers otherwise the taking the action for 
> inconsistencies reported due to unknown servers may corrupt if not done 
> properly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to