public class RecreateOnResetOperatorCoordinator extends Object implements OperatorCoordinator
OperatorCoordinator instance when reset to checkpoint.| Modifier and Type | Class and Description |
|---|---|
static class |
RecreateOnResetOperatorCoordinator.Provider
The provider for a private RecreateOnResetOperatorCoordinator.
|
OperatorCoordinator.Context, OperatorCoordinator.SubtaskGatewayBATCH_CHECKPOINT_ID, NO_CHECKPOINT| Modifier and Type | Method and Description |
|---|---|
void |
checkpointCoordinator(long checkpointId,
CompletableFuture<byte[]> resultFuture)
Takes a checkpoint of the coordinator.
|
void |
close()
This method is called when the coordinator is disposed.
|
void |
executionAttemptFailed(int subtask,
int attemptNumber,
Throwable reason)
Called when any subtask execution attempt of the task running the coordinated operator is
failed/canceled.
|
void |
executionAttemptReady(int subtask,
int attemptNumber,
OperatorCoordinator.SubtaskGateway gateway)
This is called when a subtask execution attempt of the Operator becomes ready to receive
events.
|
OperatorCoordinator |
getInternalCoordinator() |
void |
handleEventFromOperator(int subtask,
int attemptNumber,
OperatorEvent event)
Hands an OperatorEvent coming from a parallel Operator instance (one attempt of the parallel
subtasks).
|
void |
notifyCheckpointAborted(long checkpointId)
We override the method here to remove the checked exception.
|
void |
notifyCheckpointComplete(long checkpointId)
We override the method here to remove the checked exception.
|
void |
resetToCheckpoint(long checkpointId,
byte[] checkpointData)
Resets the coordinator to the given checkpoint.
|
void |
start()
Starts the coordinator.
|
void |
subtaskReset(int subtask,
long checkpointId)
Called if a subtask is recovered as part of a partial failover, meaning a failover
handled by the scheduler's failover strategy (by default recovering a pipelined region).
|
boolean |
supportsBatchSnapshot()
Whether the operator coordinator supports taking snapshot in no-checkpoint/batch scenarios.
|
public void start()
throws Exception
OperatorCoordinatorstart in interface OperatorCoordinatorException - Any exception thrown from this method causes a full job failure.public void close()
throws Exception
OperatorCoordinatorclose in interface AutoCloseableclose in interface OperatorCoordinatorExceptionpublic void handleEventFromOperator(int subtask,
int attemptNumber,
OperatorEvent event)
throws Exception
OperatorCoordinatorhandleEventFromOperator in interface OperatorCoordinatorException - Any exception thrown by this method results in a full job failure and
recovery.public void executionAttemptFailed(int subtask,
int attemptNumber,
@Nullable
Throwable reason)
OperatorCoordinatorThis method is called every time an execution attempt is failed/canceled, regardless of whether there it is caused by a partial failover or a global failover.
executionAttemptFailed in interface OperatorCoordinatorpublic void subtaskReset(int subtask,
long checkpointId)
OperatorCoordinatorIn contrast to this method, the OperatorCoordinator.resetToCheckpoint(long, byte[]) method is called
in the case of a global failover, which is the case when the coordinator (JobManager) is
recovered.
Note that this method will not be called if an execution attempt of a subtask failed, if the subtask is not entirely failed, i.e. if the subtask has other execution attempts that are not failed/canceled.
subtaskReset in interface OperatorCoordinatorpublic void executionAttemptReady(int subtask,
int attemptNumber,
OperatorCoordinator.SubtaskGateway gateway)
OperatorCoordinatorSubtaskGateway can be used to send events to the execution attempt.
The given SubtaskGateway is bound to that specific execution attempt that became
ready. All events sent through the gateway target that execution attempt; if the attempt is
no longer running by the time the event is sent, then the events are failed.
executionAttemptReady in interface OperatorCoordinatorpublic void checkpointCoordinator(long checkpointId,
CompletableFuture<byte[]> resultFuture)
throws Exception
OperatorCoordinatorTo confirm the checkpoint and store state in it, the given CompletableFuture must
be completed with the state. To abort or dis-confirm the checkpoint, the given CompletableFuture must be completed exceptionally. In any case, the given CompletableFuture must be completed in some way, otherwise the checkpoint will not progress.
The semantics are defined as follows:
checkpointCoordinator in interface OperatorCoordinatorException - Any exception thrown by this method results in a full job failure and
recovery.public void notifyCheckpointComplete(long checkpointId)
OperatorCoordinatorCheckpointListener.notifyCheckpointComplete(long) for more detail semantic of the
method.notifyCheckpointComplete in interface org.apache.flink.api.common.state.CheckpointListenernotifyCheckpointComplete in interface OperatorCoordinatorpublic void notifyCheckpointAborted(long checkpointId)
OperatorCoordinatorCheckpointListener.notifyCheckpointAborted(long) for more detail semantic of the
method.notifyCheckpointAborted in interface org.apache.flink.api.common.state.CheckpointListenernotifyCheckpointAborted in interface OperatorCoordinatorpublic void resetToCheckpoint(long checkpointId,
@Nullable
byte[] checkpointData)
OperatorCoordinatorThis method is called in the case of a global failover of the system, which means a
failover of the coordinator (JobManager). This method is not invoked on a partial
failover; partial failovers call the OperatorCoordinator.subtaskReset(int, long) method for the
involved subtasks.
This method is expected to behave synchronously with respect to other method calls and
calls to Context methods. For example, Events being sent by the Coordinator after
this method returns are assumed to take place after the checkpoint that was restored.
This method is called with a null state argument in the following situations:
In both cases, the coordinator should reset to an empty (new) state.
Restoring to a checkpoint is a way of confirming that the checkpoint is complete. It is safe to commit side-effects that are predicated on checkpoint completion after this call.
Even if no call to OperatorCoordinator.notifyCheckpointComplete(long) happened, the checkpoint can
still be complete (for example when a system failure happened directly after committing the
checkpoint, before calling the OperatorCoordinator.notifyCheckpointComplete(long) method).
resetToCheckpoint in interface OperatorCoordinatorpublic boolean supportsBatchSnapshot()
OperatorCoordinatorOperatorCoordinator.checkpointCoordinator(long, java.util.concurrent.CompletableFuture<byte[]>) and OperatorCoordinator.resetToCheckpoint(long, byte[]) methods supports taking snapshot and restoring from a
snapshot in batch processing scenarios. In such scenarios, the checkpointId will always be
-1.supportsBatchSnapshot in interface OperatorCoordinatorpublic OperatorCoordinator getInternalCoordinator() throws Exception
ExceptionCopyright © 2014–2025 The Apache Software Foundation. All rights reserved.