THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
To better separate concerns, we will remove the checkpoint storage methods from the StateBackend interface and placed them into a new interface, CheckpointStorage. Flink runtime currently contains an internal interface called CheckpointStorage; it will be renamed to CheckpointStorageAccess.
| Code Block | ||
|---|---|---|
| ||
/**
* CheckpointStorage defines how checkpoint snapshots are persisted for fault tolerance
*. Various implementations store their checkpoints in different fashions and have different requirements and
* availability guarantees.
*
*<p>For example, JobManagerCheckpointStorage stores checkpoints in the memory of the JobManager.
* It is lightweight and without additional dependencies but is not highly available
* and only supports small state sizes. This checkpoint storage policy is convenient for
* local testing and development.
*
*<p>FileSystemCheckpointStorage stores checkpoints in a filesystem. For systems like
* HDFS, NFS Drives, S3, and GCS, this storage policy supports large state size,
* in the magnitude of many terabytes while providing a highly available foundation
* for stateful applications. This checkpoint storage policy is recommended for most
* production deployments.
*/
public interface CheckpointStorage extends java.io.Serializable {
CompletedCheckpointStorageLocation resolveCheckpoint(String externalPointer);
CheckpointStorageAccess createCheckpointStorage(JobID jobId);
}
|
...