Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FLINK-8657][doc]Fix incorrect description in the document for externalized checkpoint… #5490

Closed
wants to merge 2 commits into from
Closed

[FLINK-8657][doc]Fix incorrect description in the document for externalized checkpoint… #5490

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cf0bc52
Fix incorrect description in the document for externalized checkpoint…
sihuazhou Feb 14, 2018
620ef11
revert description of 'externalized checkpoints vs savepoints'.
sihuazhou Feb 16, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/ops/state/checkpoints.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,8 +83,7 @@ env.setStateBackend(new RocksDBStateBackend("hdfs:///checkpoints-data/");
### Difference to Savepoints

Externalized checkpoints have a few differences from [savepoints](savepoints.html). They
- use a state backend specific (low-level) data format,
- may be incremental,
- use a state backend specific (low-level) data format, may be incremental.
- do not support Flink specific features like rescaling.

### Resuming from an externalized checkpoint
Expand Down
6 changes: 3 additions & 3 deletions docs/ops/state/state_backends.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,11 +56,11 @@ that store the values, triggers, etc.
Upon checkpoints, this state backend will snapshot the state and send it as part of the checkpoint acknowledgement messages to the
JobManager (master), which stores it on its heap as well.

The MemoryStateBackend can be configured to use asynchronous snapshots. While we strongly encourage the use of asynchronous snapshots to avoid blocking pipelines, please note that this is a new feature and currently not enabled
by default. To enable this feature, users can instantiate a `MemoryStateBackend` with the corresponding boolean flag in the constructor set to `true`, e.g.:
The MemoryStateBackend can be configured to use asynchronous snapshots. While we strongly encourage the use of asynchronous snapshots to avoid blocking pipelines, please note that this is currently enabled
by default. To disable this feature, users can instantiate a `MemoryStateBackend` with the corresponding boolean flag in the constructor set to `false`(this should only used for debug), e.g.:

{% highlight java %}
new MemoryStateBackend(MAX_MEM_STATE_SIZE, true);
new MemoryStateBackend(MAX_MEM_STATE_SIZE, false);
{% endhighlight %}

Limitations of the MemoryStateBackend:
Expand Down