Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Motivation
As for now, RW requests to primary replica (see calls of `ReplicaService#invoke` ) are sent to raft leader, for which the refresh leader operation is needed. In presence of placement driver which is responsible for assigning primary replicas, this is not needed, the request can be sent directly to primary replica node.
Th information about primary replicas assigned by placement driver should be available on every node after IGNITE-18859 . This task is about switching primary replica calls and eliminating excessive code related to refreshing leader of raft group.
Definition of done
Requests to primary replica are made to those nodes that are assigned by placement driver, and no related Raft calls are made.
Attachments
Issue Links
- blocks
-
IGNITE-19619 Term-bases to lease-based switch in SQL engine
- Resolved
-
IGNITE-20330 Create an abstraction for building indexes
- Resolved
- causes
-
IGNITE-20376 ItServerDataStreamerTest.testManyItems is flaky: PrimaryReplicaMissException
- Resolved
- is blocked by
-
IGNITE-20148 Explicit writeIntent cleanup on primary replica
- Resolved
-
IGNITE-19532 Introduce happends before relation between local meta storage safe time publication and completion of corresponding meta storage listners
- Resolved
-
IGNITE-19428 Implement placement driver API
- Resolved
-
IGNITE-19578 Decrease count of lease messages to meta storage
- Resolved
- is duplicated by
-
IGNITE-17256 Introduce lease-based engine for primary replica stability (primary replica selection and failover)
- Resolved
-
IGNITE-15083 Implement leaseholder selection and failover
- Resolved
- links to