RapperCL commented on issue #5197: URL: https://github.com/apache/rocketmq/issues/5197#issuecomment-1260351712
> Can you describe the scene? E.g 1 time: now = System.currentTimeMillis(), The faultItem corresponding to the two brokers: faultItemA[currentLatency = 400, startTimestamp=now + 2500L]; faultItemB[currentLatency=500, startTimestamp=now+100L]; 2 At this time, since the startTimestamp of the two faultItems> ts, they are considered unavailable by the isAvailable method. At this time, faultItem1 will be selected according to the default comparison method; It stands to reason that you can also choose faultItem2 here. I think the two properties of each faultItem represent performance and availability respectively, priority currentLatency corresponds to performance priority, priority startTimestamp corresponds to availability priority. So I think we should provide two choice comparison strategies (performance and availability) to choose from. -- 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]
