[GitHub] [hbase] anoopsjohn edited a comment on pull request #2113: HBASE-24286: HMaster won't become healthy after after cloning or crea…

[GitBox <gi...@apache.org>]

anoopsjohn edited a comment on pull request #2113:
URL: https://github.com/apache/hbase/pull/2113#issuecomment-662958329


   >Typically, you can just disable all the tables, restart the whole cluster on a new environment, and then enable all the tables.<
   Agree to Duo. That might be a better path for such use case where the cluster is deleted (after persisting all data) and later create pointing to existing FS.
   >In general, in HBase, we only know that something strange happen, but we do not know how we come into this situation so it is not safe for us to just recover automatically
   Ya I am also agreeing to this point.
   In 2.x we store the table's disable/enable state in META.  So we will have that info available in the newly recreated cluster also. (The zk data from old cluster also wont be there in new cluster I believe)


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org