Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
At the moment, two components react to the create index events:
1. IndexManager - creates indexes and other preparations;
2. PartitionReplicaListener - physically creates indexes and starts building them. and also stops building indexes.
It seems that the current implementation looks wrong and should be improved by creating an abstraction that would start and stop building indexes.
Attachments
Issue Links
- blocks
-
IGNITE-20525 Fix ItBuildIndexTest#testChangePrimaryReplicaOnMiddleBuildIndex
- Resolved
-
IGNITE-20530 Start building indexes for write-only indexes
- Resolved
-
IGNITE-20544 Implement the start of building indexes on node recovery
- Resolved
- is blocked by
-
IGNITE-18856 Switch primary replica calls from Raft leader to primary replica
- Resolved
-
IGNITE-20417 Get rid of unused code in the index module
- Resolved
-
IGNITE-20422 Add events of becoming and ceasing to be a primary replica in the PlacementDriver
- Resolved
-
IGNITE-20467 Use replica message instead of directly using raft client when building indexes
- Resolved
-
IGNITE-20505 Preparing to implement IndexBuildController
- Resolved
- is related to
-
IGNITE-19680 Get rid of org.apache.ignite.internal.index.event.IndexEventParameters
- Resolved
-
IGNITE-20339 Get rid of IndexEvent and TableEvent
- Resolved
- links to