Hi
You can configure the key `task.cancellation.timeout`[1] to increase
the timeout, and the code about this logic is here[2]
[1]
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#task-cancellation-timeout
[2]
Sorry I mean the 180 seconds. Where does flink decide that 180 seconds is
the cutoff point... And can I increase it.
On Thu., Sep. 29, 2022, 7:02 a.m. John Smith,
wrote:
> Is there a way to increase the 30 seconds to 60? Where is that 30 second
> timeout set?
>
> I have jdbc query timeout but
Is there a way to increase the 30 seconds to 60? Where is that 30 second
timeout set?
I have jdbc query timeout but at some point at night the insert takes a bit
longer cause of index rebuilding.
On Wed., Sep. 28, 2022, 5:02 a.m. Congxian Qiu,
wrote:
> Hi John
>
> Yes, the whole TaskManager
Hi John
Yes, the whole TaskManager exited because the task did not react to
cancelling signal in time
```
2022-08-30 09:14:22,138 ERROR
org.apache.flink.runtime.taskexecutor.TaskExecutor [] - Task
did not exit gracefully within 180 + seconds.
Sorry new file:
https://www.dropbox.com/s/mm9521crwvevzgl/flink-flink-taskexecutor-274-flink-prod-v-task-0001.log?dl=0
On Fri, Sep 23, 2022 at 11:26 AM John Smith wrote:
> Hi I have attached the logs here...
>
>
>
Hi I have attached the logs here...
https://www.dropbox.com/s/12gwlps52lvxdhz/flink-flink-taskexecutor-274-flink-prod-v-task-0001.log?dl=0
1- It looks like a timeout issue. Can someone confirm?
2- The task manager is restarted, since I have restart on failure in
SystemD. But it seems after a few
Actually what's happening is there's a nightly indexing job. So when we
call the insert it takes longer than the specified checkpoint threshold.
JDBC will hapilly continue waiting for a response from the DB until it's
done. So the checkpoint threshold is reached and the job tries to shut down
and
Hi John,
In an ideal scenario you would be able to leverage Flink's backpressure
mechanism. That would effectively slow down the processing until the reason
for backpressure has been resolved. However, given that indexing happens
after you've sinked your result, from a Flink perspective, the
So I know specifically, it's the indexing and I put setQueryTimeout. So the
job fails. And goes into retry. That's fine.
But just wondering is there a way to pause the stream at a specified
time/checkpoint and then resume after a specified time?
On Wed, May 4, 2022 at 10:23 AM Martijn Visser
Hi John,
It is generic, but each database has its own dialect implementation because
they all have their differences unfortunately :)
I wish I knew how I could help you out here. Perhaps some of the JDBC
maintainers could chip in.
Best regards,
Martijn
On Sun, 1 May 2022 at 04:06, John Smith
Plus in a way isn't the flink-jdbc connector kinda generic? At least the
older one didn't seem to be server specific.
On Sat, Apr 30, 2022 at 10:04 PM John Smith wrote:
> Hi Martin, is there anything I need to check for?
>
> On Tue, Apr 26, 2022 at 9:50 PM John Smith wrote:
>
>> Yeah based off
Hi Martin, is there anything I need to check for?
On Tue, Apr 26, 2022 at 9:50 PM John Smith wrote:
> Yeah based off the flink JDBC output format...
>
>
> On Tue, Apr 26, 2022 at 10:05 AM Martijn Visser
> wrote:
>
>> Hi John,
>>
>> Have you built your own JDBC MSSQL source or sink or perhaps a
Yeah based off the flink JDBC output format...
On Tue, Apr 26, 2022 at 10:05 AM Martijn Visser
wrote:
> Hi John,
>
> Have you built your own JDBC MSSQL source or sink or perhaps a CDC driver?
> Because I'm not aware of a Flink Microsoft SQL Server JDBC driver.
>
> Best regards,
>
> Martijn
Hi John,
Have you built your own JDBC MSSQL source or sink or perhaps a CDC driver?
Because I'm not aware of a Flink Microsoft SQL Server JDBC driver.
Best regards,
Martijn Visser
https://twitter.com/MartijnVisser82
https://github.com/MartijnVisser
On Tue, 26 Apr 2022 at 16:01, John Smith
Hi running 1.14.4
Logs included:
https://www.dropbox.com/s/8zjndt5rzd9o80f/flink-flink-taskexecutor-138-task-0002.log?dl=0
1- My task managers shut down with: Terminating TaskManagerRunner with exit
code 1.
2- It seems to happen at the same time every day. Which leads me to believe
it's our
15 matches
Mail list logo
