You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by GitBox <gi...@apache.org> on 2022/11/17 03:57:08 UTC

[GitHub] [rocketmq] lizhanhui commented on issue #5536: [Static Topic] Is it necessary to consider the compatible while upgrade namesrv and broker?

lizhanhui commented on issue #5536:
URL: https://github.com/apache/rocketmq/issues/5536#issuecomment-1318030271

   We should define an upgrade blueprint, allowing clusters of previous versions to update without disruption.
   
   A viable way is to upgrade name servers first, which provides capabilities of serving both broker versions;
   After all name server nodes are updated, then start to upgrade brokers.
   
   Name servers, thus, have to be able to process the transitional states: 1) all brokers miss placement configs; 2) partial brokers miss placement configs; 3) all brokers have placement configs.


-- 
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: commits-unsubscribe@rocketmq.apache.org

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