Gannalyo created SCB-751:
----------------------------
Summary: 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
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}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
