[jira] [Updated] (SCB-751) The load balancer of Saga may be faced with peak problem.

2020-05-22 Thread Willem Jiang (Jira) 


 [ 
https://issues.apache.org/jira/browse/SCB-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated SCB-751:
-
Fix Version/s: (was: pack-0.6.0)
   pack-0.7.0

> The load balancer of Saga may be faced with peak problem.
> -
>
> Key: SCB-751
> URL: https://issues.apache.org/jira/browse/SCB-751
> Project: Apache ServiceComb
>  Issue Type: Improvement
>  Components: Saga
>Affects Versions: saga-0.2.0
> Environment: project: incubator-servicecomb-saga-0.2.0
>Reporter: Gannalyo
>Assignee: justin li
>Priority: Major
>  Labels: load-balancer, saga
> Fix For: pack-0.7.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently, Saga's load balancer will *select a fastest 'MessageSender'* to 
> send msg from pool.
> My problem:
> At some point, if every Alpha node need take 10 minutes to handle business 
> for some reasons(e.g. network), that means, Saga will handle all following 
> requests by the fastest 'MessageSender' within 10 minutes.
> So, I think that the performance for Saga's load balancer will get a discount.
> Of course, I believe one alpha node can handle many many requests. Just for 
> improving Saga.
> Part of code from LoadBalancedClusterMessageSender.java  
> {code:java}
> ... 
> MessageSender messageSender = fastestSender(); 
> try { 
> long startTime = System.nanoTime();
> AlphaResponse response = messageSender.send(event); 
> senders.put(messageSender, System.nanoTime() - startTime);
> return response; 
> } catch (OmegaException e) {
>  throw e; 
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SCB-751) The load balancer of Saga may be faced with peak problem.

2019-08-22 Thread Willem Jiang (Jira) 


 [ 
https://issues.apache.org/jira/browse/SCB-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated SCB-751:
-
Fix Version/s: (was: pack-0.5.0)

> The load balancer of Saga may be faced with peak problem.
> -
>
> Key: SCB-751
> URL: https://issues.apache.org/jira/browse/SCB-751
> Project: Apache ServiceComb
>  Issue Type: Improvement
>  Components: Saga
>Affects Versions: saga-0.2.0
> Environment: project: incubator-servicecomb-saga-0.2.0
>Reporter: Gannalyo
>Assignee: justin li
>Priority: Major
>  Labels: load-balancer, saga
> Fix For: pack-0.6.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently, Saga's load balancer will *select a fastest 'MessageSender'* to 
> send msg from pool.
> My problem:
> At some point, if every Alpha node need take 10 minutes to handle business 
> for some reasons(e.g. network), that means, Saga will handle all following 
> requests by the fastest 'MessageSender' within 10 minutes.
> So, I think that the performance for Saga's load balancer will get a discount.
> Of course, I believe one alpha node can handle many many requests. Just for 
> improving Saga.
> Part of code from LoadBalancedClusterMessageSender.java  
> {code:java}
> ... 
> MessageSender messageSender = fastestSender(); 
> try { 
> long startTime = System.nanoTime();
> AlphaResponse response = messageSender.send(event); 
> senders.put(messageSender, System.nanoTime() - startTime);
> return response; 
> } catch (OmegaException e) {
>  throw e; 
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Updated] (SCB-751) The load balancer of Saga may be faced with peak problem.

2019-08-21 Thread Willem Jiang (Jira) 


 [ 
https://issues.apache.org/jira/browse/SCB-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated SCB-751:
-
Fix Version/s: pack-0.6.0

> The load balancer of Saga may be faced with peak problem.
> -
>
> Key: SCB-751
> URL: https://issues.apache.org/jira/browse/SCB-751
> Project: Apache ServiceComb
>  Issue Type: Improvement
>  Components: Saga
>Affects Versions: saga-0.2.0
> Environment: project: incubator-servicecomb-saga-0.2.0
>Reporter: Gannalyo
>Assignee: justin li
>Priority: Major
>  Labels: load-balancer, saga
> Fix For: pack-0.5.0, pack-0.6.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently, Saga's load balancer will *select a fastest 'MessageSender'* to 
> send msg from pool.
> My problem:
> At some point, if every Alpha node need take 10 minutes to handle business 
> for some reasons(e.g. network), that means, Saga will handle all following 
> requests by the fastest 'MessageSender' within 10 minutes.
> So, I think that the performance for Saga's load balancer will get a discount.
> Of course, I believe one alpha node can handle many many requests. Just for 
> improving Saga.
> Part of code from LoadBalancedClusterMessageSender.java  
> {code:java}
> ... 
> MessageSender messageSender = fastestSender(); 
> try { 
> long startTime = System.nanoTime();
> AlphaResponse response = messageSender.send(event); 
> senders.put(messageSender, System.nanoTime() - startTime);
> return response; 
> } catch (OmegaException e) {
>  throw e; 
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Updated] (SCB-751) The load balancer of Saga may be faced with peak problem.

2019-04-02 Thread Willem Jiang (JIRA) 


 [ 
https://issues.apache.org/jira/browse/SCB-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated SCB-751:
-
Fix Version/s: (was: pack-0.4.0)
   pack-0.5.0

> The load balancer of Saga may be faced with peak problem.
> -
>
> Key: SCB-751
> URL: https://issues.apache.org/jira/browse/SCB-751
> Project: Apache ServiceComb
>  Issue Type: Improvement
>  Components: Saga
>Affects Versions: saga-0.2.0
> Environment: project: incubator-servicecomb-saga-0.2.0
>Reporter: Gannalyo
>Assignee: justin li
>Priority: Major
>  Labels: load-balancer, saga
> Fix For: pack-0.5.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently, Saga's load balancer will *select a fastest 'MessageSender'* to 
> send msg from pool.
> My problem:
> At some point, if every Alpha node need take 10 minutes to handle business 
> for some reasons(e.g. network), that means, Saga will handle all following 
> requests by the fastest 'MessageSender' within 10 minutes.
> So, I think that the performance for Saga's load balancer will get a discount.
> Of course, I believe one alpha node can handle many many requests. Just for 
> improving Saga.
> Part of code from LoadBalancedClusterMessageSender.java  
> {code:java}
> ... 
> MessageSender messageSender = fastestSender(); 
> try { 
> long startTime = System.nanoTime();
> AlphaResponse response = messageSender.send(event); 
> senders.put(messageSender, System.nanoTime() - startTime);
> return response; 
> } catch (OmegaException e) {
>  throw e; 
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SCB-751) The load balancer of Saga may be faced with peak problem.

2018-12-24 Thread Willem Jiang (JIRA) 


 [ 
https://issues.apache.org/jira/browse/SCB-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated SCB-751:
-
Fix Version/s: (was: pack-0.3.0)
   pack-0.4.0

> The load balancer of Saga may be faced with peak problem.
> -
>
> Key: SCB-751
> URL: https://issues.apache.org/jira/browse/SCB-751
> Project: Apache ServiceComb
>  Issue Type: Improvement
>  Components: Saga
>Affects Versions: saga-0.2.0
> Environment: project: incubator-servicecomb-saga-0.2.0
>Reporter: Gannalyo
>Assignee: justin li
>Priority: Major
>  Labels: load-balancer, saga
> Fix For: pack-0.4.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently, Saga's load balancer will *select a fastest 'MessageSender'* to 
> send msg from pool.
> My problem:
> At some point, if every Alpha node need take 10 minutes to handle business 
> for some reasons(e.g. network), that means, Saga will handle all following 
> requests by the fastest 'MessageSender' within 10 minutes.
> So, I think that the performance for Saga's load balancer will get a discount.
> Of course, I believe one alpha node can handle many many requests. Just for 
> improving Saga.
> Part of code from LoadBalancedClusterMessageSender.java  
> {code:java}
> ... 
> MessageSender messageSender = fastestSender(); 
> try { 
> long startTime = System.nanoTime();
> AlphaResponse response = messageSender.send(event); 
> senders.put(messageSender, System.nanoTime() - startTime);
> return response; 
> } catch (OmegaException e) {
>  throw e; 
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SCB-751) The load balancer of Saga may be faced with peak problem.

2018-07-29 Thread Willem Jiang (JIRA) 


 [ 
https://issues.apache.org/jira/browse/SCB-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated SCB-751:
-
Fix Version/s: saga-0.3.0

> The load balancer of Saga may be faced with peak problem.
> -
>
> Key: SCB-751
> URL: https://issues.apache.org/jira/browse/SCB-751
> Project: Apache ServiceComb
>  Issue Type: Improvement
>  Components: Saga
>Affects Versions: saga-0.2.0
> Environment: project: incubator-servicecomb-saga-0.2.0
>Reporter: Gannalyo
>Assignee: Willem Jiang
>Priority: Major
>  Labels: load-balancer, saga
> Fix For: saga-0.3.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently, Saga's load balancer will *select a fastest 'MessageSender'* to 
> send msg from pool.
> My problem:
> At some point, if every Alpha node need take 10 minutes to handle business 
> for some reasons(e.g. network), that means, Saga will handle all following 
> requests by the fastest 'MessageSender' within 10 minutes.
> So, I think that the performance for Saga's load balancer will get a discount.
> Of course, I believe one alpha node can handle many many requests. Just for 
> improving Saga.
> Part of code from LoadBalancedClusterMessageSender.java  
> {code:java}
> ... 
> MessageSender messageSender = fastestSender(); 
> try { 
> long startTime = System.nanoTime();
> AlphaResponse response = messageSender.send(event); 
> senders.put(messageSender, System.nanoTime() - startTime);
> return response; 
> } catch (OmegaException e) {
>  throw e; 
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SCB-751) The load balancer of Saga may be faced with peak problem.

2018-07-29 Thread Willem Jiang (JIRA) 


 [ 
https://issues.apache.org/jira/browse/SCB-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated SCB-751:
-
Description: 
Currently, Saga's load balancer will *select a fastest 'MessageSender'* to send 
msg from pool.

My problem:
At some point, if every Alpha node need take 10 minutes to handle business for 
some reasons(e.g. network), that means, Saga will handle all following requests 
by the fastest 'MessageSender' within 10 minutes.
So, I think that the performance for Saga's load balancer will get a discount.

Of course, I believe one alpha node can handle many many requests. Just for 
improving Saga.

Part of code from LoadBalancedClusterMessageSender.java  
{code:java}
... 
MessageSender messageSender = fastestSender(); 
try { 
long startTime = System.nanoTime();
AlphaResponse response = messageSender.send(event); 
senders.put(messageSender, System.nanoTime() - startTime);
return response; 
} catch (OmegaException e) {
 throw e; 
}
{code}

  was:
Currently, Saga's load balancer will *select a fastest 'MessageSender'* to send 
msg from pool.

My problem:
At some point, if every Alpha node need take 10 minutes to handle business for 
some reasons(e.g. network), that means, Saga will handle all following requests 
by the fastest 'MessageSender' within 10 minutes.
So, I think that the performance for Saga's load balancer will get a discount.

Of course, I believe one alpha node can handle many many requests. Just for 
improving Saga.

 
{code:java}
//代码占位符
{code}
Part of code from LoadBalancedClusterMessageSender.java  MessageSender 
messageSender = fastestSender(); try \{ long startTime = System.nanoTime(); 
AlphaResponse response = messageSender.send(event); senders.put(messageSender, 
System.nanoTime() - startTime); return response; } catch (OmegaException e) \{ 
throw e; }
{code:java}
//代码占位符
{code}


> The load balancer of Saga may be faced with peak problem.
> -
>
> Key: SCB-751
> URL: https://issues.apache.org/jira/browse/SCB-751
> Project: Apache ServiceComb
>  Issue Type: Improvement
>  Components: Saga
>Affects Versions: saga-0.2.0
> Environment: project: incubator-servicecomb-saga-0.2.0
>Reporter: Gannalyo
>Priority: Major
>  Labels: load-balancer, saga
> Fix For: saga-0.3.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently, Saga's load balancer will *select a fastest 'MessageSender'* to 
> send msg from pool.
> My problem:
> At some point, if every Alpha node need take 10 minutes to handle business 
> for some reasons(e.g. network), that means, Saga will handle all following 
> requests by the fastest 'MessageSender' within 10 minutes.
> So, I think that the performance for Saga's load balancer will get a discount.
> Of course, I believe one alpha node can handle many many requests. Just for 
> improving Saga.
> Part of code from LoadBalancedClusterMessageSender.java  
> {code:java}
> ... 
> MessageSender messageSender = fastestSender(); 
> try { 
> long startTime = System.nanoTime();
> AlphaResponse response = messageSender.send(event); 
> senders.put(messageSender, System.nanoTime() - startTime);
> return response; 
> } catch (OmegaException e) {
>  throw e; 
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)