[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-277: - Fix Version/s: (was: pack-0.6.0) pack-0.7.0 > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Minor > Fix For: pack-0.7.0 > > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-277: - Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Minor > Fix For: pack-0.6.0 > > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-277: - Fix Version/s: (was: pack-0.4.0) pack-0.5.0 > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Minor > Fix For: pack-0.5.0 > > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-277: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Minor > Fix For: pack-0.4.0 > > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-277: - Fix Version/s: (was: saga-0.2.0) saga-0.3.0 > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Minor > Fix For: saga-0.3.0 > > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-277: Fix Version/s: saga-0.2.0 > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Minor > Fix For: saga-0.2.0 > > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Xiang updated SCB-277: -- Summary: [pack] concurrent event processing issue (was: [pack] persist index of last processed event to avoid concurrency and re-processing issue) > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Yin Xiang >Priority: Major > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > persisting last processed event index can help solve the problems above. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Xiang updated SCB-277: -- Priority: Minor (was: Major) > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Yin Xiang >Priority: Minor > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Xiang updated SCB-277: -- Description: currently, when alpha is down, it starts from the first event till the last on restart. multiple alphas may process the same event at the same time, which results in concurrent update errors when persisting events as commands. it may not affect correctness, but does leave warning logs. was: currently, when alpha is down, it starts from the first event till the last on restart. multiple alphas may process the same event at the same time, which results in concurrent update errors when persisting events as commands. it may not affect correctness, but does leave warning logs. persisting last processed event index can help solve the problems above. > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Yin Xiang >Priority: Major > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)