Package org.infinispan.statetransfer
package org.infinispan.statetransfer
Transfer of state to new caches in a cluster.
- THIS IS NOT PUBLIC API! This is a private implementation detail and must not be referenced by user code.
-
ClassDescriptionSignals that all owners of a key have been lost.Keeps track of the keys updated by normal operation and state transfer.Inbound state transfer task.Outbound state transfer task.An exception signalling that a command should be retried because a newer topology was seen during execution.Encapsulates a chunk of cache entries that belong to the same segment.WARNING: Generated code!Handles inbound state transfers.
StateConsumerimplementation.Handles outbound state transfers.StateProviderimplementation.This interceptor has two tasks: If the command's topology id is higher than the current topology id, wait for the node to receive transaction data for the new topology id. If the topology id changed during a command's execution, retry the command, but only on the originator (which replicates it to the new owners). If the cache is configured with asynchronous replication, owners cannot signal to the originator that they saw a new topology, so instead each owner forwards the command to all the other owners in the new topology.We use the state transfer lock for three different things: We don't want to execute a command until we have the transaction table for that topology id.StateTransferLockimplementation.A component that manages the state transfer when the topology of the cluster changes.StateTransferManagerimplementation.A representation of a transaction that is suitable for transferring between a StateProvider and a StateConsumer running on different members of the same cache.WARNING: Generated code!With the Non-Blocking State Transfer (NBST) in place it is possible for a transactional command to be forwarded multiple times, concurrently to the same node.