[GitHub] [hbase] z-york commented on pull request #2113: HBASE-24286: HMaster won't become healthy after after cloning or crea…

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

z-york commented on pull request #2113:
URL: https://github.com/apache/hbase/pull/2113#issuecomment-662088554


   I think the code is the same between the two, so let's discuss here since it seems all the info is here (at the moment).
   
   > I'm not sure if we want to discuss here or on #2114, but, copying from [#2114 (review)](https://github.com/apache/hbase/pull/2114#pullrequestreview-452770911),
   > 
   > > While I think the CatalogJanitor approach is probably an effective solution, I wonder if there's a "faster" solution we could do.
   > 
   > > The main question is, when we don't have ZooKeeper telling us that a RegionServer has died, how can we be certain that a RegionServer won't "come back"? If we get into a situation where data was still hosted on a RegionServer we thought was dead, we would double-assign the region and that'd be a big bug.
   > 
   > > Any thoughts on how to try to minimize the chance of us incorrectly marking a RegionServer as dead?
   
   In what cases can a RS be marked as "unknown"? If we think this is a transient state, we can always add a ttl before reassigning (but that will add considerable recovery time).


----------------------------------------------------------------
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