[jira] [Updated] (SCB-19) request json generator
[ https://issues.apache.org/jira/browse/SCB-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-19: Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > request json generator > -- > > Key: SCB-19 > URL: https://issues.apache.org/jira/browse/SCB-19 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: pack-0.4.0 > > > as a user, i want to generate saga request json by dragging and dropping > services on GUI, so that i can minimize the manual coding myself and avoid > human error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-240) [pack] performance impacts test
[ https://issues.apache.org/jira/browse/SCB-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-240: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > [pack] performance impacts test > --- > > Key: SCB-240 > URL: https://issues.apache.org/jira/browse/SCB-240 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Major > Fix For: pack-0.4.0 > > > as a user, I want to know how much performance loss if I introduce pack as my > transaction consistency solution. > We need to deploy the application (which has multiple micro services) and > start a client to send the request to the application. > 1. Running the application without Omega enabled. > 2. Running the application with Omega enabled (without inject the error) > 3. Running the application with Omega enabled (with some failed transactions) > > In Pack mode, every transaction's call could generate events from Omega to > Alpha. > We may need to collect the calling information to optimize to performance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-301) [pack] acceptance tests of transaction timeout and retry failed
[ https://issues.apache.org/jira/browse/SCB-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-301: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > [pack] acceptance tests of transaction timeout and retry failed > --- > > Key: SCB-301 > URL: https://issues.apache.org/jira/browse/SCB-301 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: pack-0.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1097) Clean up the distribution of servicecomb-pack
[ https://issues.apache.org/jira/browse/SCB-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1097: -- Fix Version/s: pack-0.3.0 > Clean up the distribution of servicecomb-pack > - > > Key: SCB-1097 > URL: https://issues.apache.org/jira/browse/SCB-1097 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Major > Fix For: pack-0.3.0 > > Time Spent: 40m > Remaining Estimate: 0h > > We need to updated the distribution module for the release of > servicecomb-pack 0.3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-18) stateful service support
[ https://issues.apache.org/jira/browse/SCB-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-18: Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > stateful service support > > > Key: SCB-18 > URL: https://issues.apache.org/jira/browse/SCB-18 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: pack-0.4.0 > > > currently saga sub-transactions are load balanced to multiple service > instances with service discovery, but it doesn't work well with stateful > service. > stateful service support can either be supported with service registry or > caching request address in saga -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-170) [pack] separate serialization from grpc to reuse the same stream
[ https://issues.apache.org/jira/browse/SCB-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-170: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > [pack] separate serialization from grpc to reuse the same stream > > > Key: SCB-170 > URL: https://issues.apache.org/jira/browse/SCB-170 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: pack-0.4.0 > > > currently, messaging protocol, serialization, and transportation are all done > with grpc/protobuf. > doing so makes sharing a single stream among different messages hard to do. > a better way is to separate serialization from grpc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-275) [pack] retry compensation on failure/timeout/crash
[ https://issues.apache.org/jira/browse/SCB-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-275: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > [pack] retry compensation on failure/timeout/crash > -- > > Key: SCB-275 > URL: https://issues.apache.org/jira/browse/SCB-275 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: pack-0.4.0 > > > when omega is unreachable, we may not receive TxCompensatedEvent. > in such case, we have to ask omega to retry on timeout or on omega > disconnected (alpha needs some mechanism to detect connection disruption). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-241) [pack] visualize transaction status in alpha
[ https://issues.apache.org/jira/browse/SCB-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-241: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > [pack] visualize transaction status in alpha > > > Key: SCB-241 > URL: https://issues.apache.org/jira/browse/SCB-241 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Major > Fix For: pack-0.4.0 > > > as a user, I want to see real time transaction status and query history > transaction status to better analysis the whole system. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-302) [pack] acceptance tests of one alpha in cluster of three down
[ https://issues.apache.org/jira/browse/SCB-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-302: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > [pack] acceptance tests of one alpha in cluster of three down > - > > Key: SCB-302 > URL: https://issues.apache.org/jira/browse/SCB-302 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: pack-0.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1011) Saga interceptor should check the gloable transaction ID
[ https://issues.apache.org/jira/browse/SCB-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1011: -- Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > Saga interceptor should check the gloable transaction ID > > > Key: SCB-1011 > URL: https://issues.apache.org/jira/browse/SCB-1011 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Major > Fix For: pack-0.4.0 > > > The interceptor should check if the transaction ID is set before send the > event to the alpha server. In this way we could help user find out if he > setup the distributed transaction rightly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-306) [pack] acceptance tests with all the transaction scenarios
[ https://issues.apache.org/jira/browse/SCB-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-306: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > [pack] acceptance tests with all the transaction scenarios > -- > > Key: SCB-306 > URL: https://issues.apache.org/jira/browse/SCB-306 > Project: Apache ServiceComb > Issue Type: Test > Components: Saga >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: pack-0.4.0 > > -- 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-908) TCC Events restful API
[ https://issues.apache.org/jira/browse/SCB-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-908: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > TCC Events restful API > --- > > Key: SCB-908 > URL: https://issues.apache.org/jira/browse/SCB-908 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: cherrylzhao >Assignee: Mohammad Asif Siddiqui >Priority: Major > Fix For: pack-0.4.0 > > > For TCC workflow, we need provide a rest interface to fetch transaction > status. > user can do manual recovery based on this information. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-303) [pack] acceptance tests of alpha cluster down and recovery
[ https://issues.apache.org/jira/browse/SCB-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-303: - Fix Version/s: (was: pack-0.3.0) pack-0.4.0 > [pack] acceptance tests of alpha cluster down and recovery > -- > > Key: SCB-303 > URL: https://issues.apache.org/jira/browse/SCB-303 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: pack-0.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1097) Clean up the distribution of servicecomb-pack
[ https://issues.apache.org/jira/browse/SCB-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved SCB-1097. --- Resolution: Fixed > Clean up the distribution of servicecomb-pack > - > > Key: SCB-1097 > URL: https://issues.apache.org/jira/browse/SCB-1097 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Major > Fix For: pack-0.3.0 > > Time Spent: 40m > Remaining Estimate: 0h > > We need to updated the distribution module for the release of > servicecomb-pack 0.3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1097) Clean up the distribution of servicecomb-pack
Willem Jiang created SCB-1097: - Summary: Clean up the distribution of servicecomb-pack Key: SCB-1097 URL: https://issues.apache.org/jira/browse/SCB-1097 Project: Apache ServiceComb Issue Type: Task Components: Saga Reporter: Willem Jiang We need to updated the distribution module for the release of servicecomb-pack 0.3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-1097) Clean up the distribution of servicecomb-pack
[ https://issues.apache.org/jira/browse/SCB-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned SCB-1097: - Assignee: Willem Jiang > Clean up the distribution of servicecomb-pack > - > > Key: SCB-1097 > URL: https://issues.apache.org/jira/browse/SCB-1097 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Major > > We need to updated the distribution module for the release of > servicecomb-pack 0.3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1096) change the method to calculate process cpu rate same with htop
何一乐 created SCB-1096: Summary: change the method to calculate process cpu rate same with htop Key: SCB-1096 URL: https://issues.apache.org/jira/browse/SCB-1096 Project: Apache ServiceComb Issue Type: Bug Reporter: 何一乐 Assignee: 何一乐 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1096) [SCB-1096]change the method to calculate process cpu rate same with htop
[ https://issues.apache.org/jira/browse/SCB-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 何一乐 updated SCB-1096: - Summary: [SCB-1096]change the method to calculate process cpu rate same with htop (was: change the method to calculate process cpu rate same with htop ) > [SCB-1096]change the method to calculate process cpu rate same with htop > - > > Key: SCB-1096 > URL: https://issues.apache.org/jira/browse/SCB-1096 > Project: Apache ServiceComb > Issue Type: Bug >Reporter: 何一乐 >Assignee: 何一乐 >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1095) Timer task need catch all throwable to protected from unexpected error
liubao created SCB-1095: --- Summary: Timer task need catch all throwable to protected from unexpected error Key: SCB-1095 URL: https://issues.apache.org/jira/browse/SCB-1095 Project: Apache ServiceComb Issue Type: Bug Reporter: liubao Assignee: liubao Timer task need catch all throwable to protected from unexpected error Or exception happens, no error message will be printed and the task will never execute again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-594) Create a document description for https://github.com/apache/incubator-servicecomb-java-chassis/pull/704
[ https://issues.apache.org/jira/browse/SCB-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-594. Resolution: Fixed Fix Version/s: java-chassis-1.2.0 > Create a document description for > https://github.com/apache/incubator-servicecomb-java-chassis/pull/704 > --- > > Key: SCB-594 > URL: https://issues.apache.org/jira/browse/SCB-594 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: liubao >Assignee: liubao >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > add documents for new added configurations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1089) Fix PrometheusPublisher naming error
[ https://issues.apache.org/jira/browse/SCB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-1089. - Resolution: Fixed Fix Version/s: java-chassis-1.2.0 > Fix PrometheusPublisher naming error > > > Key: SCB-1089 > URL: https://issues.apache.org/jira/browse/SCB-1089 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: liubao >Assignee: liubao >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > https://github.com/apache/servicecomb-java-chassis/issues/974 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
