TaskRestoreManager (samza-api 1.9.0-SNAPSHOT API)
JavaScript is disabled on your browser.
Skip navigation links
Overview
Package
Class
Tree
Deprecated
Index
Help
Prev Class
Next Class
Frames
No Frames
All Classes
Summary: 
Nested | 
Field | 
Constr | 
Method
Detail: 
Field | 
Constr | 
Method
org.apache.samza.storage
Interface TaskRestoreManager
public interface TaskRestoreManager
The helper interface restores task state.
Method Summary
All Methods Instance Methods Abstract Methods 
Modifier and Type
Method and Description
void
close()
Closes all initiated resources include storage engines
void
init(Checkpoint checkpoint)
Initialize state resources such as store directories.
java.util.concurrent.CompletableFuture<java.lang.Void>
restore()
Restore state from checkpoints, state snapshots and changelogs.
Method Detail
init
void init(Checkpoint checkpoint)
Initialize state resources such as store directories.
restore
java.util.concurrent.CompletableFuture<java.lang.Void> restore()
Restore state from checkpoints, state snapshots and changelogs.
Currently, store restoration happens on a separate thread pool within ContainerStorageManager. In case of
interrupt/shutdown signals from SamzaContainer, ContainerStorageManager may interrupt the restore
thread.
Note: Typically, interrupt signals don't bubble up as InterruptedException unless the restore thread is
waiting on IO/network. In case of busy looping, implementors are expected to check the interrupt status of the
thread periodically and shutdown gracefully before throwing InterruptedException upstream.
SamzaContainer will not wait for clean up and the interrupt signal is the best effort by the container
to notify that its shutting down.
close
void close()
Closes all initiated resources include storage engines
Skip navigation links
Overview
Package
Class
Tree
Deprecated
Index
Help
Prev Class
Next Class
Frames
No Frames
All Classes
Summary: 
Nested | 
Field | 
Constr | 
Method
Detail: 
Field | 
Constr | 
Method