:2021 Jun. 9 (Wed.) 22:12
>> To:Kezhu Wang
>> Cc:Thomas Wang ; Yun Gao ; user <
>> user@flink.apache.org>
>> Subject:Re: Re: Re: Re: Failed to cancel a job using the STOP rest API
>>
>> Yes good catch Kezhu, IllegalStateException sounds very much like
>
FLINK-21028.
>
> --
> From:Piotr Nowojski
> Send Time:2021 Jun. 9 (Wed.) 22:12
> To:Kezhu Wang
> Cc:Thomas Wang ; Yun Gao ; user <
> user@flink.apache.org>
> Subject:Re: Re: Re: Re: Failed to cancel a job using t
6 04:02:20 2021
Recipients:Yun Gao
CC:user
Subject:Re: Re: Failed to cancel a job using the STOP rest API
One thing I noticed is that if I set drain = true, the job could be stopped
correctly. Maybe that's because I'm using a Parquet file sink which is a
bulk-encoded format and only writes t
ld you also show us the dag of the job ? And does some operators in
>>> the source task
>>> use multiple-threads to emit records?
>>>
>>> Best,
>>> Yun
>>>
>>>
>>> --Original Mail --
>>
: Re: Re: Failed to cancel a job using the STOP rest API
> This is actually a very simple job that reads from Kafka and writes to S3
> using the StreamingFileSink w/ Parquet format. I'm all using Flink's API
> and nothing custom.
>
> Thomas
>
> On Sun, Jun 6, 2021 at
CC:user
Subject:Re: Re: Re: Failed to cancel a job using the STOP rest API
This is actually a very simple job that reads from Kafka and writes to S3 using
the StreamingFileSink w/ Parquet format. I'm all using Flink's API and nothing
custom.
Thomas
On Sun, Jun 6, 2021 at 6:43 PM Yun
:*Thomas Wang
> *Send Date:*Sun Jun 6 04:02:20 2021
> *Recipients:*Yun Gao
> *CC:*user
> *Subject:*Re: Re: Failed to cancel a job using the STOP rest API
>
>> One thing I noticed is that if I set drain = true, the job could be
>> stopped correctly. Maybe that's bec
--
Sender:Thomas Wang
Send Date:Sun Jun 6 04:02:20 2021
Recipients:Yun Gao
CC:user
Subject:Re: Re: Failed to cancel a job using the STOP rest API
One thing I noticed is that if I set drain = true, the job could be stopped
correctly. Maybe that's because I'm using a Parquet file sink which
e
>> TaskManager's log when it could not be stopped ?
>>
>> Best,
>> Yun
>>
>> [1]
>> https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/ops/rest_api/#jobs-jobid-savepoints-triggerid
>>
>>
>>
>> ---
--Original Mail --
> *Sender:*Thomas Wang
> *Send Date:*Sat Jun 5 00:47:47 2021
> *Recipients:*Yun Gao
> *CC:*user
> *Subject:*Re: Failed to cancel a job using the STOP rest API
>
>> Hi Yun,
>>
>> Thanks for your reply. We are not usin
Hi Thomas,
For querying the savepoint status, a get request could be issued to
/jobs/:jobid/savepoints/:savepointtriggerid [1] to get the status and position
of the savepoint. But if the job is running with some kind of per-job mode and
JobMaster is gone after the stop-with-savepoint, the reque
Hi Yun,
Thanks for your reply. We are not using any legacy source. For this
specific job, there is only one source that is using FlinkKafkaConsumer
which I assume has the correct cancel() method implemented.
Also could you suggest how I could use the "request-id" to get the
savepoint location?
T
Hi Thomas,
I think you are right that the CLI is also using the same rest API underlying,
and since
the response of the rest API is ok and the savepoint is triggered successfully,
I reckon
that it might not be due to rest API process, and we might still first focus on
the
stop-with-savepoint p
13 matches
Mail list logo
