This doesn't sound like proper behavior, could you provide instructions
on how to reproduce this?
On 07.12.2017 13:42, Lasse Nedergaard wrote:
I hope it can be put in 1.4.1.
I have one concern about the rest api. We running 1.3.1 on dc/os and
if we apply parameters as arguments and in our code validate these
parameters and throw an exception during startup if something is wrong
we see that all uploaded jar disappear all running jobs are gone and
sometimes we loss all the task managers. I don’t think it is the
attended behaviour.
Med venlig hilsen / Best regards
Lasse Nedergaard
Den 7. dec. 2017 kl. 13.00 skrev Chesnay Schepler <ches...@apache.org
<mailto:ches...@apache.org>>:
In retrospect I'm quite frustrated we didn't get around to
implementing this for 1.4.
The least-effort implementation would have required copying one
class, and modifying ~10 lines.
Doesn't get any more low-hanging than that.
On 07.12.2017 12:51, Chesnay Schepler wrote:
I've finished the implementation. I created 2 new branches in my
repository, for 1.3.2 and 1.4.
1.3.2: https://github.com/zentol/flink/tree/release-1.3.2-custom
1.4: https://github.com/zentol/flink/tree/release-1.4-custom
Triggering savepoints works exactly like cancel-with-savepoint, just
replace "cancel-with-savepoint" with "trigger-savepoint" in the URL.
* "/jobs/:jobid/trigger-savepoint"
* "/jobs/:jobid/trigger-savepoint/target-directory/:targetDirectory"
* "/jobs/:jobid/trigger-savepoint/in-progress/:requestId"
On 07.12.2017 03:43, Vishal Santoshi wrote:
That would be awesome... we could do it too if that is acceptable...
On Dec 6, 2017 3:56 PM, "Chesnay Schepler" <ches...@apache.org
<mailto:ches...@apache.org>> wrote:
No, this is also not possible in 1.4.
This will be available in 1.5 where we rework the
client-cluster communication to go entirely through the REST API.
This will mean that everything you can do with the command-line
client can also be achieved directly through the REST API.
However, from what i can tell this should be straight-forward
to implement in a custom build. I can take a deeper look if
this would be an acceptable workaround for you.
On 07.12.2017 00:20, Vishal Santoshi wrote:
Is that something 1.4 has?
On Dec 6, 2017 1:01 PM, "Lasse Nedergaard"
<lassenederga...@gmail.com <mailto:lassenederga...@gmail.com>>
wrote:
Hi.
It is not possible through REST in Flink 1.3.2 I’m looking
for the feature. The only option is to use ./Flink
savepoint for now
Med venlig hilsen / Best regards
Lasse Nedergaard
Den 6. dec. 2017 kl. 21.52 skrev Vishal Santoshi
<vishal.santo...@gmail.com
<mailto:vishal.santo...@gmail.com>>:
I was more interested in savepoints WITHOUT cancellation...
On Dec 6, 2017 11:07 AM, "vipul singh"
<neoea...@gmail.com <mailto:neoea...@gmail.com>> wrote:
Hi Vishal,
Job cancellations can be done via a REST API:
https://ci.apache.org/projects/flink/flink-docs-release-1.3/monitoring/rest_api.html#cancel-job-with-savepoint
<https://ci.apache.org/projects/flink/flink-docs-release-1.3/monitoring/rest_api.html#cancel-job-with-savepoint>
Thanks,
Vipul
On Wed, Dec 6, 2017 at 10:56 AM, Vishal Santoshi
<vishal.santo...@gmail.com
<mailto:vishal.santo...@gmail.com>> wrote:
One can submit jobs, upload jars, kill jobs etc
very strange that you can’t do a save point ?
Or am I missing something obvious ?
Vishal
--
Thanks,
Vipul
