You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by GitBox <gi...@apache.org> on 2021/07/03 15:41:08 UTC

[GitHub] [hbase] virajjasani edited a comment on pull request #3455: HBASE-22923 Consider minVersionToMoveSysTables while moving region and creating regionPlan (ADDENDUM)

virajjasani edited a comment on pull request #3455:
URL: https://github.com/apache/hbase/pull/3455#issuecomment-873425641


   > So what's the problem here?
   
   With earlier patch of HBASE-22923, we only covered case of "AssignmentManager taking care of excluding lower version servers for system table assignment" for the thread that keeps track of version differences in the cluster and soon as it finds new version, it tries to move system tables there, so this is auto-migration of system tables use-case. But we missed the case of graceful stop and balancer's plans generation. Graceful stop prepares `move` commands based on RSGroup but if we don't change the logic of "excluding servers with lower version for system table assignment", system table regions will be in hanging state when we execute graceful stop command.
   With the current patch, we have covered all cases that master uses to coordinate region movement, regardless of whether it is auto-migration of regions by AM or whether we execute graceful stop manually.


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

To unsubscribe, e-mail: issues-unsubscribe@hbase.apache.org

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