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 2020/10/21 14:24:22 UTC

[GitHub] [flink] azagrebin commented on pull request #13730: [FLINK-19552][coordination] Consider only available input location preferences for slot profile in pipelined region scheduling

azagrebin commented on pull request #13730:
URL: https://github.com/apache/flink/pull/13730#issuecomment-713615180


   I also working on an integration test.
   `PipelinedRegionSchedulingConcurrentFailureTest`, suggested in #13628, reproduces the exact original problem which is a combination of several discovered problems but the overall test looks a bit complicated.
   
   I will try the following graph of disjoint pipelines:
   v1 (ssg1) -> v2 (ssg3)
   v3 (ssg2) -> v4 (ssg3)
   with 2 slots.
   e.g. v1 need to be canceled with its location and (v3 -> v2) region needs to be scheduled afterwards
   then while deploying v2 and its SSG3, we will ask for v4 input (canceled v3).


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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