[jira] [Resolved] (SCB-660) Update the dubbo example compose file
[ https://issues.apache.org/jira/browse/SCB-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-660. -- Resolution: Fixed Fix Version/s: saga-0.3.0 > Update the dubbo example compose file > -- > > Key: SCB-660 > URL: https://issues.apache.org/jira/browse/SCB-660 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Eric Lee >Priority: Minor > Fix For: saga-0.3.0 > > > It's could be more convince if we can separate the AlphaServer start with the > common service of the dubbo example. > You can take a > [spring-cloud-demo|https://github.com/apache/incubator-servicecomb-saga/tree/master/saga-demo/saga-spring-cloud-demo] > docker-compose as an example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-660) Update the dubbo example compose file
[ https://issues.apache.org/jira/browse/SCB-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-660: Assignee: Eric Lee > Update the dubbo example compose file > -- > > Key: SCB-660 > URL: https://issues.apache.org/jira/browse/SCB-660 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Eric Lee >Priority: Minor > > It's could be more convince if we can separate the AlphaServer start with the > common service of the dubbo example. > You can take a > [spring-cloud-demo|https://github.com/apache/incubator-servicecomb-saga/tree/master/saga-demo/saga-spring-cloud-demo] > docker-compose as an example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-639) upgrade docker maven plugin
[ https://issues.apache.org/jira/browse/SCB-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-639. -- Resolution: Fixed > upgrade docker maven plugin > --- > > Key: SCB-639 > URL: https://issues.apache.org/jira/browse/SCB-639 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-639) upgrade docker maven plugin
Eric Lee created SCB-639: Summary: upgrade docker maven plugin Key: SCB-639 URL: https://issues.apache.org/jira/browse/SCB-639 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee Assignee: Eric Lee Fix For: saga-0.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-632) reformat code according to the google code style
Eric Lee created SCB-632: Summary: reformat code according to the google code style Key: SCB-632 URL: https://issues.apache.org/jira/browse/SCB-632 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee Assignee: Eric Lee Fix For: saga-0.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-628) correct the naming of demos
Eric Lee created SCB-628: Summary: correct the naming of demos Key: SCB-628 URL: https://issues.apache.org/jira/browse/SCB-628 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee Assignee: Eric Lee Fix For: saga-0.2.0 As there is new dubbo-demo added, we need to update the demo directory and accept test directory rightly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-615) fix typos in EventScanner
Eric Lee created SCB-615: Summary: fix typos in EventScanner Key: SCB-615 URL: https://issues.apache.org/jira/browse/SCB-615 Project: Apache ServiceComb Issue Type: Bug Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee Assignee: Eric Lee Fix For: saga-0.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-458) add blogs to introduce saga's evolution
[ https://issues.apache.org/jira/browse/SCB-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-458. -- Resolution: Fixed > add blogs to introduce saga's evolution > --- > > Key: SCB-458 > URL: https://issues.apache.org/jira/browse/SCB-458 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-458) add blogs to introduce saga's evolution
Eric Lee created SCB-458: Summary: add blogs to introduce saga's evolution Key: SCB-458 URL: https://issues.apache.org/jira/browse/SCB-458 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Eric Lee Assignee: Eric Lee -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-400) Add guides to run demo without docker compose
[ https://issues.apache.org/jira/browse/SCB-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-400. -- Resolution: Fixed > Add guides to run demo without docker compose > -- > > Key: SCB-400 > URL: https://issues.apache.org/jira/browse/SCB-400 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.1.0 > > > As the user prefer to run the alpha server and demo application with java > command. > We need to add the guilde to run the demo without docker compose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-397) uniform sha1sum format for release of ServiceComb
Eric Lee created SCB-397: Summary: uniform sha1sum format for release of ServiceComb Key: SCB-397 URL: https://issues.apache.org/jira/browse/SCB-397 Project: Apache ServiceComb Issue Type: Task Components: Service-Center Reporter: Eric Lee Currently, the sha1sum format of service center is in the form of A0B3 B1D2 ... . However, the sha1sum format of java chassis and saga is a0b3b1d2... . We should use the same format for the whole ServiceComb project. Perfer to use the second form. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-224) [pack] retry sub-transaction on failure
[ https://issues.apache.org/jira/browse/SCB-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-224: Assignee: Eric Lee > [pack] retry sub-transaction on failure > --- > > Key: SCB-224 > URL: https://issues.apache.org/jira/browse/SCB-224 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.2.0 > > > as a user, i want to retry transaction in my service, so that it can always > be done eventually. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-347) license compliance
[ https://issues.apache.org/jira/browse/SCB-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-347. -- Resolution: Fixed > license compliance > -- > > Key: SCB-347 > URL: https://issues.apache.org/jira/browse/SCB-347 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-347) license compliance
Eric Lee created SCB-347: Summary: license compliance Key: SCB-347 URL: https://issues.apache.org/jira/browse/SCB-347 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Eric Lee Assignee: Eric Lee -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-344) [pack] use mysql as alpha's backend database
[ https://issues.apache.org/jira/browse/SCB-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-344. -- Resolution: Fixed > [pack] use mysql as alpha's backend database > > > Key: SCB-344 > URL: https://issues.apache.org/jira/browse/SCB-344 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.1.0 > > > As a user, I want to use mysql as alpha's backend database. However, as > mysql-connector-java is under GPL license, we cannot directly add it as > saga's dependency. We need to tell user how to use in from document. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-243) [pack] support to intercept java chassis
[ https://issues.apache.org/jira/browse/SCB-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-243: - Fix Version/s: (was: saga-0.2.0) saga-0.1.0 > [pack] support to intercept java chassis > > > Key: SCB-243 > URL: https://issues.apache.org/jira/browse/SCB-243 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Minor > Fix For: saga-0.1.0 > > > as a sdk, I want to be able to intercept the incoming and outgoing rest > requests of apps developed by java chassis and inject the transaction ids in > its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-243) [pack] support to intercept java chassis
[ https://issues.apache.org/jira/browse/SCB-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-243: - Affects Version/s: (was: saga-0.2.0) saga-0.1.0 > [pack] support to intercept java chassis > > > Key: SCB-243 > URL: https://issues.apache.org/jira/browse/SCB-243 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Minor > Fix For: saga-0.1.0 > > > as a sdk, I want to be able to intercept the incoming and outgoing rest > requests of apps developed by java chassis and inject the transaction ids in > its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-243) [pack] support to intercept java chassis
[ https://issues.apache.org/jira/browse/SCB-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-243: - Summary: [pack] support to intercept java chassis (was: [pack] support java chassis's rest transport) > [pack] support to intercept java chassis > > > Key: SCB-243 > URL: https://issues.apache.org/jira/browse/SCB-243 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Minor > Fix For: saga-0.1.0 > > > as a sdk, I want to be able to intercept the incoming and outgoing rest > requests of apps developed by java chassis and inject the transaction ids in > its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-330) [pack] update documents of saga pack
[ https://issues.apache.org/jira/browse/SCB-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-330. -- Resolution: Fixed > [pack] update documents of saga pack > > > Key: SCB-330 > URL: https://issues.apache.org/jira/browse/SCB-330 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.1.0 > > > As a dev, I want to know how to use the Saga's new architecture pack. > Documents including README and quick start should contain details of its > usages, features and architecture. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-243) [pack] support to intercept java chassis
[ https://issues.apache.org/jira/browse/SCB-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-243. -- Resolution: Fixed > [pack] support to intercept java chassis > > > Key: SCB-243 > URL: https://issues.apache.org/jira/browse/SCB-243 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Minor > Fix For: saga-0.1.0 > > > as a sdk, I want to be able to intercept the incoming and outgoing rest > requests of apps developed by java chassis and inject the transaction ids in > its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-246) [pack] add demo to use pack with dubbo
[ https://issues.apache.org/jira/browse/SCB-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-246: - Description: as a dev, I want to know how to use pack with dubbo. (was: as a sdk, I want to be able to intercept the incoming and outgoing rpc requests of apps developed by dubbo and inject the transaction ids in its header.) > [pack] add demo to use pack with dubbo > -- > > Key: SCB-246 > URL: https://issues.apache.org/jira/browse/SCB-246 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Minor > Fix For: saga-0.2.0 > > > as a dev, I want to know how to use pack with dubbo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-245) [pack] support to intercept dubbo's requests
[ https://issues.apache.org/jira/browse/SCB-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-245: - Description: as a sdk, I want to be able to intercept the incoming and outgoing requests of apps developed by dubbo and inject the transaction ids in its header. (was: as a sdk, I want to be able to intercept the incoming and outgoing rest requests of apps developed by dubbo and inject the transaction ids in its header.) > [pack] support to intercept dubbo's requests > > > Key: SCB-245 > URL: https://issues.apache.org/jira/browse/SCB-245 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Minor > Fix For: saga-0.2.0 > > > as a sdk, I want to be able to intercept the incoming and outgoing requests > of apps developed by dubbo and inject the transaction ids in its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-246) [pack] add demo to use pack with dubbo
[ https://issues.apache.org/jira/browse/SCB-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-246: - Summary: [pack] add demo to use pack with dubbo (was: [pack] support dubbo's rpc transport) > [pack] add demo to use pack with dubbo > -- > > Key: SCB-246 > URL: https://issues.apache.org/jira/browse/SCB-246 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Minor > Fix For: saga-0.2.0 > > > as a sdk, I want to be able to intercept the incoming and outgoing rpc > requests of apps developed by dubbo and inject the transaction ids in its > header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-245) [pack] support to intercept dubbo's requests
[ https://issues.apache.org/jira/browse/SCB-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-245: - Summary: [pack] support to intercept dubbo's requests (was: [pack] support dubbo's rest transport) > [pack] support to intercept dubbo's requests > > > Key: SCB-245 > URL: https://issues.apache.org/jira/browse/SCB-245 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Minor > Fix For: saga-0.2.0 > > > as a sdk, I want to be able to intercept the incoming and outgoing rest > requests of apps developed by dubbo and inject the transaction ids in its > header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-244) [pack] add demo to use pack with java chassis
[ https://issues.apache.org/jira/browse/SCB-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-244: - Summary: [pack] add demo to use pack with java chassis (was: [pack] support java chassis's highway transport) > [pack] add demo to use pack with java chassis > - > > Key: SCB-244 > URL: https://issues.apache.org/jira/browse/SCB-244 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Minor > Fix For: saga-0.2.0 > > > as a sdk, I want to be able to intercept the incoming and outgoing highway > requests of apps developed by java chassis and inject the transaction ids in > its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-244) [pack] add demo to use pack with java chassis
[ https://issues.apache.org/jira/browse/SCB-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-244: - Description: as a dev, I want to know how I can use pack with Java Chassis. (was: as a sdk, I want to be able to intercept the incoming and outgoing highway requests of apps developed by java chassis and inject the transaction ids in its header.) > [pack] add demo to use pack with java chassis > - > > Key: SCB-244 > URL: https://issues.apache.org/jira/browse/SCB-244 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Minor > Fix For: saga-0.2.0 > > > as a dev, I want to know how I can use pack with Java Chassis. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-344) [pack] use mysql as alpha's backend database
[ https://issues.apache.org/jira/browse/SCB-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-344: Assignee: Eric Lee > [pack] use mysql as alpha's backend database > > > Key: SCB-344 > URL: https://issues.apache.org/jira/browse/SCB-344 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.1.0 > > > As a user, I want to use mysql as alpha's backend database. However, as > mysql-connector-java is under GPL license, we cannot directly add it as > saga's dependency. We need to tell user how to use in from document. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-344) [pack] use mysql as alpha's backend database
Eric Lee created SCB-344: Summary: [pack] use mysql as alpha's backend database Key: SCB-344 URL: https://issues.apache.org/jira/browse/SCB-344 Project: Apache ServiceComb Issue Type: Task Components: Saga Affects Versions: saga-0.1.0 Reporter: Eric Lee Fix For: saga-0.1.0 As a user, I want to use mysql as alpha's backend database. However, as mysql-connector-java is under GPL license, we cannot directly add it as saga's dependency. We need to tell user how to use in from document. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-239) [pack] omega recovery
[ https://issues.apache.org/jira/browse/SCB-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-239. -- Resolution: Fixed > [pack] omega recovery > - > > Key: SCB-239 > URL: https://issues.apache.org/jira/browse/SCB-239 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.1.0 > > > as a user, I want to have the pending data stored persistently and be able to > resume the execution of these data if omega fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-243) [pack] support java chassis's rest transport
[ https://issues.apache.org/jira/browse/SCB-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-243: Assignee: Eric Lee > [pack] support java chassis's rest transport > > > Key: SCB-243 > URL: https://issues.apache.org/jira/browse/SCB-243 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Minor > Fix For: saga-0.2.0 > > > as a sdk, I want to be able to intercept the incoming and outgoing rest > requests of apps developed by java chassis and inject the transaction ids in > its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-342) [pack] secure gRPC transport
Eric Lee created SCB-342: Summary: [pack] secure gRPC transport Key: SCB-342 URL: https://issues.apache.org/jira/browse/SCB-342 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee As a user, I want to secure the transport between alpha and omega. Configurations of security should be visible to developers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-341) [pack] multi tenant support
[ https://issues.apache.org/jira/browse/SCB-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-341: - Summary: [pack] multi tenant support (was: multi tenant support) > [pack] multi tenant support > --- > > Key: SCB-341 > URL: https://issues.apache.org/jira/browse/SCB-341 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Major > > As a user, I want to have my access control among alpha cluster. Access to > different tenant's services should be restricted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-341) multi tenant support
Eric Lee created SCB-341: Summary: multi tenant support Key: SCB-341 URL: https://issues.apache.org/jira/browse/SCB-341 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee As a user, I want to have my access control among alpha cluster. Access to different tenant's services should be restricted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-340) [pack] load balance omega
[ https://issues.apache.org/jira/browse/SCB-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-340: - Summary: [pack] load balance omega (was: load balance omega) > [pack] load balance omega > - > > Key: SCB-340 > URL: https://issues.apache.org/jira/browse/SCB-340 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Major > > As omega is stateless, there is no need to store instanceId any more. > However, we need to load balance the access to omegas in case of too much > stress on some omegas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-340) load balance omega
Eric Lee created SCB-340: Summary: load balance omega Key: SCB-340 URL: https://issues.apache.org/jira/browse/SCB-340 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee As omega is stateless, there is no need to store instanceId any more. However, we need to load balance the access to omegas in case of too much stress on some omegas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-333) support for Java 8's LocalDate and LocalDateTime
[ https://issues.apache.org/jira/browse/SCB-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-333: - Description: Currently, java chassis does not support Java 8's new Type LocalDate and LocalDateTime. It seems the jackson is unable to deserialize LocalDate because it does not have the default constructor. (was: Currently, java chassis do not support Java 8's new Type LocalDate and LocalDateTime. It seems the jackson is unable to deserialize LocalDate because it does not have the default constructor.) > support for Java 8's LocalDate and LocalDateTime > > > Key: SCB-333 > URL: https://issues.apache.org/jira/browse/SCB-333 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > > Currently, java chassis does not support Java 8's new Type LocalDate and > LocalDateTime. It seems the jackson is unable to deserialize LocalDate > because it does not have the default constructor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-335) more accurate log when user mistype the uri in CseRestTemplate
Eric Lee created SCB-335: Summary: more accurate log when user mistype the uri in CseRestTemplate Key: SCB-335 URL: https://issues.apache.org/jira/browse/SCB-335 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: Eric Lee As a user, I may mistype the uri with its port which will make the original request uri from "abc:1234" to "abc:abc:1234" which is very confusing in the user side. We should log more accurate to tell the user the cause instead of the result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-334) log more detail when user misuse the query parameter as request body in rest
Eric Lee created SCB-334: Summary: log more detail when user misuse the query parameter as request body in rest Key: SCB-334 URL: https://issues.apache.org/jira/browse/SCB-334 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: Eric Lee As a dev get used to traditional springmvc development, if I need to post a request with customize type as its body, I just need to pass that in the methods argument without annotations. However, in Java Chassis, the argument in methods are query parameter by default. If I pass a customize instance as the parameter, it will throw exception saying it does not support complex type. This is very confusing. Maybe we should tell user to add the RequestBody annotation or when we detect the complex type in post request query parameter, we just take it as the request body? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-333) support for Java 8's LocalDate and LocalDateTime
Eric Lee created SCB-333: Summary: support for Java 8's LocalDate and LocalDateTime Key: SCB-333 URL: https://issues.apache.org/jira/browse/SCB-333 Project: Apache ServiceComb Issue Type: New Feature Components: Java-Chassis Reporter: Eric Lee Currently, java chassis do not support Java 8's new Type LocalDate and LocalDateTime. It seems the jackson is unable to deserialize LocalDate because it does not have the default constructor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-330) [pack] update documents of saga pack
Eric Lee created SCB-330: Summary: [pack] update documents of saga pack Key: SCB-330 URL: https://issues.apache.org/jira/browse/SCB-330 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.1.0 Reporter: Eric Lee Assignee: Eric Lee As a dev, I want to know how to use the Saga's new architecture pack. Documents including README and quick start should contain details of its usages, features and architecture. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-313) Add 8th live streaming material
[ https://issues.apache.org/jira/browse/SCB-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-313. -- Resolution: Fixed > Add 8th live streaming material > --- > > Key: SCB-313 > URL: https://issues.apache.org/jira/browse/SCB-313 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-323) inconsistent port in saga demo
[ https://issues.apache.org/jira/browse/SCB-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-323: - Component/s: Saga > inconsistent port in saga demo > -- > > Key: SCB-323 > URL: https://issues.apache.org/jira/browse/SCB-323 > Project: Apache ServiceComb > Issue Type: Bug > Components: Saga >Reporter: Eric Lee >Priority: Major > > Details can refer to: > https://github.com/apache/incubator-servicecomb-saga/issues/131 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-323) inconsistent port in saga demo
Eric Lee created SCB-323: Summary: inconsistent port in saga demo Key: SCB-323 URL: https://issues.apache.org/jira/browse/SCB-323 Project: Apache ServiceComb Issue Type: Bug Reporter: Eric Lee Details can refer to: https://github.com/apache/incubator-servicecomb-saga/issues/131 -- 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 ] Eric Lee updated SCB-240: - Fix Version/s: (was: saga-0.1.0) saga-0.2.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: saga-0.2.0 > > > as a user, I want to know how much performance loss if I introduce pack as my > transaction consistency solution. -- 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 ] Eric Lee updated SCB-240: - Affects Version/s: (was: saga-0.1.0) saga-0.2.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: saga-0.2.0 > > > as a user, I want to know how much performance loss if I introduce pack as my > transaction consistency solution. -- 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 ] Eric Lee updated SCB-241: - Affects Version/s: (was: saga-0.1.0) saga-0.2.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 > > 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] [Created] (SCB-313) Add 8th live streaming material
Eric Lee created SCB-313: Summary: Add 8th live streaming material Key: SCB-313 URL: https://issues.apache.org/jira/browse/SCB-313 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Eric Lee Assignee: Eric Lee -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-226) Add 7th live streaming material
[ https://issues.apache.org/jira/browse/SCB-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-226: - Issue Type: Sub-task (was: Task) Parent: SCB-312 > Add 7th live streaming material > --- > > Key: SCB-226 > URL: https://issues.apache.org/jira/browse/SCB-226 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-312) Add live streaming materials
Eric Lee created SCB-312: Summary: Add live streaming materials Key: SCB-312 URL: https://issues.apache.org/jira/browse/SCB-312 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Eric Lee Assignee: Eric Lee -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-273) proper indent for navigation
Eric Lee created SCB-273: Summary: proper indent for navigation Key: SCB-273 URL: https://issues.apache.org/jira/browse/SCB-273 Project: Apache ServiceComb Issue Type: Bug Reporter: Eric Lee Assignee: Eric Lee Currently, the indent in _data/navigation.yml is incorrect in the yaml format. Local server refuse to start because of it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-239) [pack] omega recovery
[ https://issues.apache.org/jira/browse/SCB-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-239: Assignee: Eric Lee > [pack] omega recovery > - > > Key: SCB-239 > URL: https://issues.apache.org/jira/browse/SCB-239 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.1.0 > > > as a user, I want to have the pending data stored persistently and be able to > resume the execution of these data if omega fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-226) Add 7th live streaming material
[ https://issues.apache.org/jira/browse/SCB-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-226. -- Resolution: Fixed > Add 7th live streaming material > --- > > Key: SCB-226 > URL: https://issues.apache.org/jira/browse/SCB-226 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-247) [pack] integrate with orchestration framework
Eric Lee created SCB-247: Summary: [pack] integrate with orchestration framework Key: SCB-247 URL: https://issues.apache.org/jira/browse/SCB-247 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.3.0 Reporter: Eric Lee Fix For: saga-0.3.0 Currently, pack needs user to provide a starting point for a transaction which acts as an aggregator. Introducing orchestration framework can greatly reduce these kind of work by using DSL and supports more EIP. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-246) [pack] support dubbo's rpc transport
Eric Lee created SCB-246: Summary: [pack] support dubbo's rpc transport Key: SCB-246 URL: https://issues.apache.org/jira/browse/SCB-246 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee Fix For: saga-0.2.0 as a sdk, I want to be able to intercept the incoming and outgoing rpc requests of apps developed by dubbo and inject the transaction ids in its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-245) [pack] support dubbo's rest transport
Eric Lee created SCB-245: Summary: [pack] support dubbo's rest transport Key: SCB-245 URL: https://issues.apache.org/jira/browse/SCB-245 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee Fix For: saga-0.2.0 as a sdk, I want to be able to intercept the incoming and outgoing rest requests of apps developed by dubbo and inject the transaction ids in its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-244) [pack] support java chassis's highway transport
Eric Lee created SCB-244: Summary: [pack] support java chassis's highway transport Key: SCB-244 URL: https://issues.apache.org/jira/browse/SCB-244 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee Fix For: saga-0.2.0 as a sdk, I want to be able to intercept the incoming and outgoing highway requests of apps developed by java chassis and inject the transaction ids in its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-243) [pack] support java chassis's rest transport
Eric Lee created SCB-243: Summary: [pack] support java chassis's rest transport Key: SCB-243 URL: https://issues.apache.org/jira/browse/SCB-243 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee Fix For: saga-0.2.0 as a sdk, I want to be able to intercept the incoming and outgoing rest requests of apps developed by java chassis and inject the transaction ids in its header. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-242) [pack] omega strong consistent support
Eric Lee created SCB-242: Summary: [pack] omega strong consistent support Key: SCB-242 URL: https://issues.apache.org/jira/browse/SCB-242 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.2.0 Reporter: Eric Lee Fix For: saga-0.2.0 as a user, I want to auto compensate my transaction when it fails without hard coded compensated method. -- 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 ] Eric Lee updated SCB-241: - Summary: [pack] visualize transaction status in alpha (was: visualize transaction status in alpha) > [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.1.0 >Reporter: Eric Lee >Priority: Major > > 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] [Created] (SCB-241) visualize transaction status in alpha
Eric Lee created SCB-241: Summary: 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.1.0 Reporter: Eric Lee 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] [Created] (SCB-240) [pack] performance impacts test
Eric Lee created SCB-240: Summary: [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.1.0 Reporter: Eric Lee Fix For: saga-0.1.0 as a user, I want to know how much performance loss if I introduce pack as my transaction consistency solution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-239) [pack] omega recovery
Eric Lee created SCB-239: Summary: [pack] omega recovery Key: SCB-239 URL: https://issues.apache.org/jira/browse/SCB-239 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.1.0 Reporter: Eric Lee Fix For: saga-0.1.0 as a user, I want to have the pending data stored persistently and be able to resume the execution of these data if omega fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-234) [pack] fail fast if alpha cluster down
[ https://issues.apache.org/jira/browse/SCB-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-234. -- Resolution: Fixed > [pack] fail fast if alpha cluster down > -- > > Key: SCB-234 > URL: https://issues.apache.org/jira/browse/SCB-234 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.1.0 > > > when alpha cluster is down, future transactions should fail immediately at > @SagaStart instead of keep retrying, in order not to stress the services > further by blocking all the request threads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-227) [pack] stop sub transaction from running when global tx failed
[ https://issues.apache.org/jira/browse/SCB-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-227. -- Resolution: Fixed Fix Version/s: saga-0.1.0 > [pack] stop sub transaction from running when global tx failed > -- > > Key: SCB-227 > URL: https://issues.apache.org/jira/browse/SCB-227 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.1.0 > > > sub transactions may be started in parallel among multiple services. > if one of them failed, none of them shall start at all, if not already > started. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-234) [pack] fail fast if alpha cluster down
[ https://issues.apache.org/jira/browse/SCB-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-234: Assignee: Eric Lee > [pack] fail fast if alpha cluster down > -- > > Key: SCB-234 > URL: https://issues.apache.org/jira/browse/SCB-234 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee >Priority: Major > Fix For: saga-0.1.0 > > > when alpha cluster is down, future transactions should fail immediately at > @SagaStart instead of keep retrying, in order not to stress the services > further by blocking all the request threads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-211) [pack] exponential backoff reconnect on cluster down or network down
[ https://issues.apache.org/jira/browse/SCB-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-211: Assignee: Eric Lee > [pack] exponential backoff reconnect on cluster down or network down > > > Key: SCB-211 > URL: https://issues.apache.org/jira/browse/SCB-211 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee > > when omega is disconnected from alpha cluster, it keeps trying on failure of > sending event. > an exponential back off retry is better for the sake of cpu resources and > disk space due to logs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-227) [pack] stop sub transaction from running when global tx failed
[ https://issues.apache.org/jira/browse/SCB-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-227: Assignee: Eric Lee > [pack] stop sub transaction from running when global tx failed > -- > > Key: SCB-227 > URL: https://issues.apache.org/jira/browse/SCB-227 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee > > sub transactions may be started in parallel among multiple services. > if one of them failed, none of them shall start at all, if not already > started. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-226) Add 7th live streaming material
Eric Lee created SCB-226: Summary: Add 7th live streaming material Key: SCB-226 URL: https://issues.apache.org/jira/browse/SCB-226 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Eric Lee Assignee: Eric Lee -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-213) [pack] proper timing to send out SagaEndedEvent on asynchronous compensation
[ https://issues.apache.org/jira/browse/SCB-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-213: Assignee: Eric Lee > [pack] proper timing to send out SagaEndedEvent on asynchronous compensation > > > Key: SCB-213 > URL: https://issues.apache.org/jira/browse/SCB-213 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee > Fix For: saga-0.1.0 > > > Currently, SagaEndedEvent is sent immediately after receiving responses of > sub transactions. However, this behavior is incorrect when handling > asynchronous compensation as compensation may have some delay. To simplify > this, we suppose the error response code will throw an exception to the > SagaStart node. In this way, the normal responses will send out the > SagaEndedEvent immediately when they finish while the failed transaction will > complement the SagaEndedEvent when the compensations complete. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SCB-213) [pack] proper timing to send out SagaEndedEvent on asynchronous compensation
[ https://issues.apache.org/jira/browse/SCB-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-213. -- Resolution: Fixed > [pack] proper timing to send out SagaEndedEvent on asynchronous compensation > > > Key: SCB-213 > URL: https://issues.apache.org/jira/browse/SCB-213 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee >Assignee: Eric Lee > Fix For: saga-0.1.0 > > > Currently, SagaEndedEvent is sent immediately after receiving responses of > sub transactions. However, this behavior is incorrect when handling > asynchronous compensation as compensation may have some delay. To simplify > this, we suppose the error response code will throw an exception to the > SagaStart node. In this way, the normal responses will send out the > SagaEndedEvent immediately when they finish while the failed transaction will > complement the SagaEndedEvent when the compensations complete. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-218) [pack] mark end of saga event correctly when the alpha in charge is down
Eric Lee created SCB-218: Summary: [pack] mark end of saga event correctly when the alpha in charge is down Key: SCB-218 URL: https://issues.apache.org/jira/browse/SCB-218 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.1.0 Reporter: Eric Lee Currently, we assume that all compensated command are sent out from the same alpha and the compensated results are sent back from different omega to the same alpha. However, when this alpha instance fails, the omega will send the compensated results to another alpha as alpha is stateless. We still need to query the db to keep transaction status consistent. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-213) [pack] proper timing to send out SagaEndedEvent on asynchronous compensation
Eric Lee created SCB-213: Summary: [pack] proper timing to send out SagaEndedEvent on asynchronous compensation Key: SCB-213 URL: https://issues.apache.org/jira/browse/SCB-213 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.1.0 Reporter: Eric Lee Fix For: saga-0.1.0 Currently, SagaEndedEvent is sent immediately after receiving responses of sub transactions. However, this behavior is incorrect when handling asynchronous compensation as compensation may have some delay. To simplify this, we suppose the error response code will throw an exception to the SagaStart node. In this way, the normal responses will send out the SagaEndedEvent immediately when they finish while the failed transaction will complement the SagaEndedEvent when the compensations complete. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SCB-173) [pack] mark start of saga
[ https://issues.apache.org/jira/browse/SCB-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-173. -- Resolution: Fixed > [pack] mark start of saga > - > > Key: SCB-173 > URL: https://issues.apache.org/jira/browse/SCB-173 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee > Fix For: saga-0.1.0 > > > with mark of saga start, we know exactly where the global transaction starts, > so that we can generate the global tx id there, to better support concurrent > sub-transactions to multiple services -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SCB-174) [pack] object serialization/deserialization
[ https://issues.apache.org/jira/browse/SCB-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-174. -- Resolution: Fixed > [pack] object serialization/deserialization > --- > > Key: SCB-174 > URL: https://issues.apache.org/jira/browse/SCB-174 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee > Fix For: saga-0.1.0 > > > as of now, we used java native object serializer, i.e. ObjectInputStream & > ObjectOutputStream, for quick prototyping. > but these serializer/deserializer are problematic and we need to find more > suitable one. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-174) [pack] object serialization/deserialization
[ https://issues.apache.org/jira/browse/SCB-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-174: Assignee: Eric Lee > [pack] object serialization/deserialization > --- > > Key: SCB-174 > URL: https://issues.apache.org/jira/browse/SCB-174 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee > Fix For: saga-0.1.0 > > > as of now, we used java native object serializer, i.e. ObjectInputStream & > ObjectOutputStream, for quick prototyping. > but these serializer/deserializer are problematic and we need to find more > suitable one. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SCB-169) [pack] omega get notified whether events are sent successfully or not
[ https://issues.apache.org/jira/browse/SCB-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-169: - Affects Version/s: saga-0.1.0 Fix Version/s: saga-0.1.0 Component/s: Saga > [pack] omega get notified whether events are sent successfully or not > - > > Key: SCB-169 > URL: https://issues.apache.org/jira/browse/SCB-169 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.1.0 >Reporter: Eric Lee > Fix For: saga-0.1.0 > > > Currently, as the stream is asynchronous, grpc client does not know whether > the events are successfully sent out. It needs to get a ACK response from the > server or use the blocking stub. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-169) [pack] omega get notified whether events are sent successfully or not
Eric Lee created SCB-169: Summary: [pack] omega get notified whether events are sent successfully or not Key: SCB-169 URL: https://issues.apache.org/jira/browse/SCB-169 Project: Apache ServiceComb Issue Type: Improvement Reporter: Eric Lee Currently, as the stream is asynchronous, grpc client does not know whether the events are successfully sent out. It needs to get a ACK response from the server or use the blocking stub. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SCB-138) [pack] omega's callback about transaction state
[ https://issues.apache.org/jira/browse/SCB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-138. -- Resolution: Fixed Fix Version/s: (was: java-chassis-1.0.0-m1) saga-0.1.0 > [pack] omega's callback about transaction state > --- > > Key: SCB-138 > URL: https://issues.apache.org/jira/browse/SCB-138 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Eric Lee >Assignee: Eric Lee > Fix For: saga-0.1.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > as a dev, i want to register callback function in the server side, so the > server can send messages back to the client directly instead of establishing > a new connection to the exact client with its corresponding uri. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SCB-158) Update issues links to JIRA
[ https://issues.apache.org/jira/browse/SCB-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee resolved SCB-158. -- Resolution: Fixed Fix Version/s: java-chassis-1.0.0-m1 > Update issues links to JIRA > --- > > Key: SCB-158 > URL: https://issues.apache.org/jira/browse/SCB-158 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis, Saga, Service-Center, website >Reporter: Eric Lee >Assignee: Eric Lee > Labels: newbie > Fix For: java-chassis-1.0.0-m1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-158) Update issues links to JIRA
[ https://issues.apache.org/jira/browse/SCB-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-158: Assignee: Eric Lee > Update issues links to JIRA > --- > > Key: SCB-158 > URL: https://issues.apache.org/jira/browse/SCB-158 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis, Saga, Service-Center, website >Reporter: Eric Lee >Assignee: Eric Lee > Labels: newbie > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-158) Update issues links to JIRA
Eric Lee created SCB-158: Summary: Update issues links to JIRA Key: SCB-158 URL: https://issues.apache.org/jira/browse/SCB-158 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis, Saga, Service-Center, website Reporter: Eric Lee -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-138) [pack] omega's callback about transaction state
Eric Lee created SCB-138: Summary: [pack] omega's callback about transaction state Key: SCB-138 URL: https://issues.apache.org/jira/browse/SCB-138 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Reporter: Eric Lee Assignee: Eric Lee as a dev, i want to register callback function in the server side, so the server can send messages back to the client directly instead of establishing a new connection to the exact client with its corresponding uri. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-95) [pack] able to link sub-transactions as a single global transaction
[ https://issues.apache.org/jira/browse/SCB-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304276#comment-16304276 ] Eric Lee commented on SCB-95: - Done and PR is merged. PR: https://github.com/apache/incubator-servicecomb-saga/pull/87 > [pack] able to link sub-transactions as a single global transaction > --- > > Key: SCB-95 > URL: https://issues.apache.org/jira/browse/SCB-95 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee > Fix For: saga-0.1.0 > > > as a dev, i want to know which sub-transactions are contained in a global > transaction, so that i can manage their states together -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-95) [pack] able to link sub-transactions as a single global transaction
[ https://issues.apache.org/jira/browse/SCB-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-95: --- Assignee: Eric Lee > [pack] able to link sub-transactions as a single global transaction > --- > > Key: SCB-95 > URL: https://issues.apache.org/jira/browse/SCB-95 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Assignee: Eric Lee > Fix For: saga-0.1.0 > > > as a dev, i want to know which sub-transactions are contained in a global > transaction, so that i can manage their states together -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (SCB-116) Update the repo address in ServiceComb
[ https://issues.apache.org/jira/browse/SCB-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SCB-116: - Comment: was deleted (was: https://github.com/apache/incubator-servicecomb-website/pull/14) > Update the repo address in ServiceComb > --- > > Key: SCB-116 > URL: https://issues.apache.org/jira/browse/SCB-116 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Willem Jiang >Assignee: Eric Lee > > Current ServiceComb repos were transferred in Apache, we need to update the > repo address in the ServiceComb website. > Java Chassis new repo url : > https://github.com/apache/incubator-servicecomb-java-chassis > ServiceCenter new repo url : > https://github.com/apache/incubator-servicecomb-service-center > Saga new repo url : https://github.com/apache/incubator-servicecomb-saga > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-116) Update the repo address in ServiceComb
[ https://issues.apache.org/jira/browse/SCB-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303045#comment-16303045 ] Eric Lee commented on SCB-116: -- https://github.com/apache/incubator-servicecomb-website/pull/14 > Update the repo address in ServiceComb > --- > > Key: SCB-116 > URL: https://issues.apache.org/jira/browse/SCB-116 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Willem Jiang >Assignee: Eric Lee > > Current ServiceComb repos were transferred in Apache, we need to update the > repo address in the ServiceComb website. > Java Chassis new repo url : > https://github.com/apache/incubator-servicecomb-java-chassis > ServiceCenter new repo url : > https://github.com/apache/incubator-servicecomb-service-center > Saga new repo url : https://github.com/apache/incubator-servicecomb-saga > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-116) Update the repo address in ServiceComb
[ https://issues.apache.org/jira/browse/SCB-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee reassigned SCB-116: Assignee: Eric Lee > Update the repo address in ServiceComb > --- > > Key: SCB-116 > URL: https://issues.apache.org/jira/browse/SCB-116 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Willem Jiang >Assignee: Eric Lee > > Current ServiceComb repos were transferred in Apache, we need to update the > repo address in the ServiceComb website. > Java Chassis new repo url : > https://github.com/apache/incubator-servicecomb-java-chassis > ServiceCenter new repo url : > https://github.com/apache/incubator-servicecomb-service-center > Saga new repo url : https://github.com/apache/incubator-servicecomb-saga > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-104) simplify transport rest template implementation
Eric Lee created SCB-104: Summary: simplify transport rest template implementation Key: SCB-104 URL: https://issues.apache.org/jira/browse/SCB-104 Project: Apache ServiceComb Issue Type: Task Components: Saga Reporter: Eric Lee Priority: Minor There already has a _exchange_ implementation in the_RestTemplateTransport_ which include the _get_ implementation. We can remove the _get_ method and add entry in the _exchange_ method for it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-91) All Monitor can convert to Map with plain-key when polling data
[
https://issues.apache.org/jira/browse/SCB-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Lee reassigned SCB-91:
---
Assignee: yangyongzheng
> All Monitor can convert to Map with plain-key when polling data
> ---
>
> Key: SCB-91
> URL: https://issues.apache.org/jira/browse/SCB-91
> Project: Apache ServiceComb
> Issue Type: Sub-task
> Components: Java-Chassis
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>
> Because sample like output file need write metrics into separate files,it's
> better get plain-key Map contains all metrics data rather than get metric
> model.
> This also can use in publish metrics with plain-key mode like Spring boot
> actuator act:
> { "counter.status.200.root": 20, "counter.status.200.metrics": 3,
> "counter.status.200.star-star": 5, "counter.status.401.root": 4,
> "gauge.response.star-star": 6, "gauge.response.root": 2,
> "gauge.response.metrics": 3, "classes": 5808, "classes.loaded": 5808,
> "classes.unloaded": 0, "heap": 3728384, "heap.committed": 986624,
> "heap.init": 262144, "heap.used": 52765, "nonheap": 0, "nonheap.committed":
> 77568, "nonheap.init": 2496, "nonheap.used": 75826, "mem": 986624,
> "mem.free": 933858, "processors": 8, "threads": 15, "threads.daemon": 11,
> "threads.peak": 15, "threads.totalStarted": 42, "uptime": 494836,
> "instance.uptime": 489782, "datasource.primary.active": 5,
> "datasource.primary.usage": 0.25 }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SCB-21) service orchestration
[ https://issues.apache.org/jira/browse/SCB-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297938#comment-16297938 ] Eric Lee commented on SCB-21: - *What is the progress?* Choice of orchestration framework has made. Currently we choose camel due to its flexibility and rich ecosystem. Proposal for the integrating Java Chassis into camel has completed. *What is next?* Camel needs a standalone service center client while the client inside Java Chassis is not good enough and needs to refactor. *How much percent have you done?* 10%. *Where is the relative discussion topic(email or website link)?* See the attachment above. > service orchestration > - > > Key: SCB-21 > URL: https://issues.apache.org/jira/browse/SCB-21 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: Eric Lee > Attachments: Proposal for integrating ServiceComb into Camel.pdf > > > orchestration of service invocation and aggregation of data from multiple > services based on configured rule > eg. a user request requires calling service a/b/c/d in order: request -> a -> > b -> c -> d -> response > this creates a tight coupling among services a/b/c/d. > better solutions: > request -> aggregator -> response (aggregator calls a/b/c/d in sequence based > on configured rule) > request -> a -> message queue -> b -> queue -> c -> queue -> d > both ways no coupling among the services. > this epic is about solution 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-13) refactor service registry module
[ https://issues.apache.org/jira/browse/SCB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297933#comment-16297933 ] Eric Lee commented on SCB-13: - *What is the progress?* Analysis and proposal for the service registry module has completed. *What is next?* Refactor or rewrite the service registry module according to the proposal. *How much percent have you done?* 30%. *Where is the relative discussion topic(email or website link)?* http://servicecomb.io/docs/service-registry-refactor-proposal/ > refactor service registry module > > > Key: SCB-13 > URL: https://issues.apache.org/jira/browse/SCB-13 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: Eric Lee > Labels: service-orchestration > > Currently, the service registry module in Java Chassis has the following > problems: > - Low level components access high level components frequently. The cyclic > relationships make the implementation complicated and introduce some > redundant access points. > - Low level components should be stateless to be reused by high level > components. Introducing state into low level components makes it relies > heavily on the high level components, causing cyclic relationships. > - Hard to integrate with third-party framework. It does not provide a > standalone client with cache capability inside. It also requires the > configurations should be loaded from dynamic properties. > Details: > [http://servicecomb.io/docs/service-registry-refactor-proposal/|http://servicecomb.io/docs/service-registry-refactor-proposal/] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SC-21) service orchestration
[ https://issues.apache.org/jira/browse/SC-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SC-21: --- Attachment: Proposal for integrating ServiceComb into Camel.pdf proposal for integrating ServiceComb into Camel. Before that, we need to refactor the service registry module to provide a more friendly client for camel to use. > service orchestration > - > > Key: SC-21 > URL: https://issues.apache.org/jira/browse/SC-21 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: Eric Lee > Attachments: Proposal for integrating ServiceComb into Camel.pdf > > > orchestration of service invocation and aggregation of data from multiple > services based on configured rule > eg. a user request requires calling service a/b/c/d in order: request -> a -> > b -> c -> d -> response > this creates a tight coupling among services a/b/c/d. > better solutions: > request -> aggregator -> response (aggregator calls a/b/c/d in sequence based > on configured rule) > request -> a -> message queue -> b -> queue -> c -> queue -> d > both ways no coupling among the services. > this epic is about solution 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SC-26) serial service invocations
[ https://issues.apache.org/jira/browse/SC-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lee updated SC-26: --- Description: *Given* aggregator configured with serial service invocations in a configuration file *When* a request goes through services in order a -> b -> c -> d without transformation of data *Then* aggregator invokes the services a/b/c/d in order and returns the response from service d was: Given aggregator configured with serial service invocations in a configuration file When a request goes through services in order a -> b -> c -> d without transformation of data Then aggregator invokes the services a/b/c/d in order and returns the response from service d > serial service invocations > -- > > Key: SC-26 > URL: https://issues.apache.org/jira/browse/SC-26 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Eric Lee > > *Given* > aggregator configured with serial service invocations in a configuration file > *When* > a request goes through services in order a -> b -> c -> d without > transformation of data > *Then* > aggregator invokes the services a/b/c/d in order and returns the response > from service d -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SC-28) fallback invocation on exception
Eric Lee created SC-28: -- Summary: fallback invocation on exception Key: SC-28 URL: https://issues.apache.org/jira/browse/SC-28 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: Eric Lee *Given* aggregator configured with service invocations with fallback in a configuration file *When* a request goes through service a with fallback f without transformation of data *Then* aggregator invokes the services a and returns its response on success *When* invocation of service a failed *Then* aggregator invokes service f and returns its response -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SC-27) parallel service invocations
Eric Lee created SC-27: -- Summary: parallel service invocations Key: SC-27 URL: https://issues.apache.org/jira/browse/SC-27 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: Eric Lee *Given* aggregator configured with parallel service invocations in a configuration file *When* a request goes through services in parallel a/b/c/d without transformation of data *Then* aggregator invokes the services a/b/c/d in parallel and returns the aggregated responses from services a/b/c/d -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SC-26) serial service invocations
Eric Lee created SC-26: -- Summary: serial service invocations Key: SC-26 URL: https://issues.apache.org/jira/browse/SC-26 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: Eric Lee Given aggregator configured with serial service invocations in a configuration file When a request goes through services in order a -> b -> c -> d without transformation of data Then aggregator invokes the services a/b/c/d in order and returns the response from service d -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SC-25) integration with highway transport
Eric Lee created SC-25: -- Summary: integration with highway transport Key: SC-25 URL: https://issues.apache.org/jira/browse/SC-25 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: Eric Lee -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SC-23) integration with zipkin
Eric Lee created SC-23: -- Summary: integration with zipkin Key: SC-23 URL: https://issues.apache.org/jira/browse/SC-23 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: Eric Lee -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SC-22) integration with service center
Eric Lee created SC-22: -- Summary: integration with service center Key: SC-22 URL: https://issues.apache.org/jira/browse/SC-22 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: Eric Lee -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SC-21) service orchestration
Eric Lee created SC-21: -- Summary: service orchestration Key: SC-21 URL: https://issues.apache.org/jira/browse/SC-21 Project: Apache ServiceComb Issue Type: New Feature Components: Java-Chassis Reporter: Eric Lee orchestration of service invocation and aggregation of data from multiple services based on configured rule eg. a user request requires calling service a/b/c/d in order: request -> a -> b -> c -> d -> response this creates a tight coupling among services a/b/c/d. better solutions: request -> aggregator -> response (aggregator calls a/b/c/d in sequence based on configured rule) request -> a -> message queue -> b -> queue -> c -> queue -> d both ways no coupling among the services. this epic is about solution 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
