Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.90.4
-
None
-
None
-
Reviewed
Description
I've experienced this problem a few times, ReplicationSink calls are received through the normal handlers and potentially can call itself which, in certain situations, call fill up all the handlers. For example, 10 handlers that are all replication calls are all trying to talk to the local server at the same time.
HRS.replicateLogEntries should have @QosPriority(priority=HIGH_QOS) to use the other set of handlers.