InternalPartitionService.See: Description
| Class | Description |
|---|---|
| AbstractPartitionPrimaryReplicaAntiEntropyTask | |
| InternalMigrationListener |
Internal synchronous/blocking listener to intercept migration cycle
on master member and migration participants.
|
| InternalMigrationListener.NopInternalMigrationListener | |
| InternalPartitionImpl | |
| InternalPartitionServiceImpl |
The
InternalPartitionService implementation. |
| MigrationManager |
Maintains migration system state and manages migration operations performed within the cluster.
|
| MigrationStats |
Collection of stats for partition migration tasks.
|
| NopPartitionListener |
No-op partition listener which does nothing on partition change events.
|
| PartitionDataSerializerHook | |
| PartitionEventManager |
Maintains registration of partition-system related listeners and dispatches corresponding events.
|
| PartitionPortableHook | |
| PartitionReplicaChangeEvent | |
| PartitionReplicaManager |
Maintains the version values for the partition replicas and manages the replica-related operations for partitions
|
| PartitionReplicaStateChecker |
Verifies up-to-dateness of each of partition replicas owned by this member.
|
| PartitionStateManager |
Maintains the partition table state.
|
| ReplicaFragmentSyncInfo |
The information for a replica synchronization - which partition and replica index needs synchronization and what is
the target (the owner of the partition).
|
| Enum | Description |
|---|---|
| InternalMigrationListener.MigrationParticipant | |
| PartitionServiceState |
Represents partition service state of current member.
|
InternalPartitionService.
It is very important that should be the least amount of dependencies to this package. Preferably only the
InternalPartitionServiceImpl is called while constructing an instance and after
that all communication should go through the InternalPartitionService interface.
Nobody needs to know about the actual implementing classes because this gives a very tight coupling and
this is undesirable. This is not only undesirable for external people because they could easily be tightly
coupled to the internals of Hazelcast, but it also is undesirable for us because it becomes a tangled mess
that prevent easy replacement/changes.Copyright © 2020 Hazelcast, Inc.. All Rights Reserved.