You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/05 15:16:02 UTC
[jira] [Commented] (FLINK-7803) Update savepoint Documentation
[ https://issues.apache.org/jira/browse/FLINK-7803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352524#comment-16352524 ]
ASF GitHub Bot commented on FLINK-7803:
---------------------------------------
Github user GJL commented on a diff in the pull request:
https://github.com/apache/flink/pull/4809#discussion_r166001086
--- Diff: docs/ops/state/savepoints.md ---
@@ -120,6 +120,10 @@ This will atomically trigger a savepoint for the job with ID `:jobid` and cancel
If you don't specify a target directory, you need to have [configured a default directory](#configuration). Otherwise, cancelling the job with a savepoint will fail.
+<div class="alert alert-warning">
--- End diff --
Should be something like:
```
<div class="alert alert-warning">
<strong>Attention:</strong> <code>targetDirectory</code> has to be a location accessible by both the JobManager(s) and TaskManager(s), e.g., a location on a distributed file system.
</div>
```
because markdown is not rendered within HTML tags.
Also, the *warning* you have added is currently in the *Cancel Job with Savepoint* section. I think it should be moved to the section above (*Trigger a Savepoint*), or somewhere else since it does not only apply to the cancelation case.
@uce
> Update savepoint Documentation
> ------------------------------
>
> Key: FLINK-7803
> URL: https://issues.apache.org/jira/browse/FLINK-7803
> Project: Flink
> Issue Type: Bug
> Components: Documentation
> Reporter: Razvan
> Assignee: Razvan
> Priority: Major
>
> Can you please update https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/savepoints.html to specify the savepoint location *MUST* always be a location accessible by all hosts?
> I spent quite some time believing it'S a bug and trying to find solutions, see https://issues.apache.org/jira/browse/FLINK-7750. It's not obvious in the current documentation and other might waste time also believing it's an actual issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)