jinrongluo opened a new issue #546:
URL: https://github.com/apache/incubator-eventmesh/issues/546


   In production deployment of eventmesh in cloud environment, eventmesh 
cluster of multiple instances is required for high availability and fault 
tolerance.
   
   From the code study, eventmesh runtime using local cache Concurrent Map to 
store client and session information. For example, 
   - HTTP Server side: localConsumerGroupMapping and localClientInfoMapping
   - TCP Server side:  sessionTable and clientGroupMap
   
   My question is when multiple eventmesh runtime is running, how these local 
cache map synchronized? 
   
   If these local cache are not synchronized, problem happen when incoming 
requests are load balanced into the cluster.
   
   For example, a **SUBSCRIBE** request is routed to eventmesh runtime instance 
1. then later **UNSUBSCRIBE** request is routed to to instance 2,  UNSUBSCRIBE 
request will failed.  (That's because the actual subscriber is in instance1)
   
    
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to