yhs0092 commented on pull request #1936: URL: https://github.com/apache/servicecomb-java-chassis/pull/1936#issuecomment-685252276
Current fix solution: - change the type of `ServiceCombServerStats#globalAllowIsolatedServerTryingFlag` from `AtomicBoolean` to `AtomicReference<TryingIsolatedServerMarker>`. The newly defined `TryingIsolatedServerMarker` holds the `Invocation` instance which is holding the trying chance and the timestamp. - in the normal case, when the `Invocation` is finished(checked by `Invocation#isFinished`), the trying chance is released. - in case that some unknown error occurs, causing the invocation procedure ends with the `Invocation#finished` flag not set to true, an new configuration `servicecomb.loadbalance.isolation.maxSingleTestWindow` is added to limit the max occupation period of the global trying chance. ---------------------------------------------------------------- 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: [email protected]
