yx9o commented on PR #9549: URL: https://github.com/apache/rocketmq/pull/9549#issuecomment-3076642580
> > Hi @saz97 , is this all submitted? I understand that when the master switches, the client will be notified to re-acquire the route. Will the client's method of obtaining the route regularly be retained? I think the server should generally rely on the client as little as possible. > > The PR hasn't been fully submitted yet—the current commits are just a demo. Regarding whether to retain the client's periodic route-pulling mechanism, this is open for discussion. After all, scheduled pulling and server-side notifications aren't mutually exclusive. Keeping it as a fallback mechanism shouldn't be an issue. If the scheduled pull is not retained, this method strongly relies on the client, and the client and server must be upgraded together. In fact, in actual production applications, many client and server versions are inconsistent, because the cost of upgrading the client is very high. Is compatibility considered in this way? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
