flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] Clarkkkkk commented on issue #6680: [FLINK-10319] [runtime] Too many requestPartitionState would crash JM
Date Wed, 12 Sep 2018 14:31:56 GMT
Clarkkkkk commented on issue #6680: [FLINK-10319] [runtime] Too many requestPartitionState
would crash JM
URL: https://github.com/apache/flink/pull/6680#issuecomment-420670340
 
 
   @TisonKun Currently, the task will try to ask JM to check producer state. If it is a Timeout
Exception, it will try again and assume it's still running.
   I am not sure about when the triggerPartitionProducerStateCheck get called, is it possible
that the producer state is still running? If it is possible, then we might restart the Execution
which is not necessary and go through the whole task cancellation logic(it might restart the
whole job in Streaming mode). 
   And by using a single-thread thread pool, we will not introduce too much pressure on the
JM and avoid unnecessary task cancellation.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message