You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2018/09/12 09:34:41 UTC

[GitHub] TisonKun edited a comment on issue #6680: [FLINK-10319] [runtime] Too many requestPartitionState would crash JM

TisonKun edited a comment on issue #6680: [FLINK-10319] [runtime] Too many requestPartitionState would crash JM
URL: https://github.com/apache/flink/pull/6680#issuecomment-420577451
 
 
   @Clarkkkkk why do you think it fails the execution eagerly? Former, Task would ask for JM to check the producer state and decide whether fails the execution or not; but now Task would always retry.
   
   You are right that introduce a single-thread thread pool would loose the problem, but without ask for JM, Task is aware of the producer fail later. There is little benefit we gain by ask JM for checkState but burden it.

----------------------------------------------------------------
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