Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Motivation
Currently, PartitionReplicaListener does not switch its operations to another thread pool when handling ReplicaRequests, so, most of the time, they are handled in the messaging thread (the thread that is used to handle incoming messages). There is only one such thread per Ignite node, and its disruption might harm node liveness a great deal (for instance, it may make the node drop off the Physical Topology due to inability to ack a ping in a timely manner).
Definition of Done
Calls to storages may cause I/O and block on locks, so they should be avoided in the messaging thread.
Implementation Notes
Attachments
Issue Links
- relates to
-
IGNITE-21010 Cluster loses connectivity after some time
- Resolved
-
IGNITE-21144 PartitionReplicaListener should return execution to partition thread pool after calls to PlacementDriver
- Resolved
- links to