[ https://issues.apache.org/jira/browse/SCB-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623007#comment-16623007 ]
ASF GitHub Bot commented on SCB-915: ------------------------------------ oliugian commented on issue #311: SCB-915:saga alpha event scanner optimization URL: https://github.com/apache/incubator-servicecomb-saga/pull/311#issuecomment-423400520 All tests have been successful The functionality of ForwardRecovery has been incorporated into defaultRecovery, so delete it and its test code. There is a test code equivalent to ForwardRecover in TransactionAspectTest. (-1) means infinite retry, but it can also be interrupted, throwing an InterruptedException, which is consistent with the logic in the previous ForwardRecovery ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > saga alpha event scanner optimization > ------------------------------------- > > Key: SCB-915 > URL: https://issues.apache.org/jira/browse/SCB-915 > Project: Apache ServiceComb > Issue Type: Improvement > Reporter: FuChenGeng > Assignee: FuChenGeng > Priority: Major > > 1.the compensate logic for retry scenarios is not perfect, in some place it > do not considering retry scenarios. > 2.do one compensation in one event scanner cycle,it mean that if there are > 1000 aborted event, it will cost at lest 500s to compensate it. And it has > some bugs like > [https://github.com/apache/incubator-servicecomb-saga/issues/253] > 3.all hot and cold data are in the same table > 4. omega do not send every try event to alpha.omega do it's try logic by > itself. -- This message was sent by Atlassian JIRA (v7.6.3#76005)