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/06 16:04:16 UTC

[GitHub] [flink] zentol commented on pull request #13544: [FLINK-19309][coordination] Add TaskExecutorManager

zentol commented on pull request #13544:
URL: https://github.com/apache/flink/pull/13544#issuecomment-704383090


   The TEM contains literally all logic that is specific to task executors. That was the entire thought process.
   
   Should the SlotManager (SM) handle pending slots? Maybe. But I could also envision a worker allocator that queries the SM for required resources and allocates workers as necessary, fulfilling all current conditions that exist. That would then mean the SM only ever works with actually existing slots via a single code path (the registration of a TM / it's slots).
   The SM does not necessarily need to know about pending slots; it already doesn't now it in case of external systems starting task executors anyway. The only difference in behavior is how many notifications the JM receives, which shouldn't be a problem due to the proposed stabilization protocol.


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