[
https://issues.apache.org/jira/browse/YUNIKORN-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500753#comment-17500753
]
Wilfred Spiegelenburg commented on YUNIKORN-1089:
-------------------------------------------------
This looks exactly like the config given above. Driver is _groupA,_ executors
are {_}groupB{_}. _groupA_ is not defined, _groupB_ is in the above config. All
placeholders time out at the same time. It should not matter which task group
they belong to. After the time out the get removed.
For what currently happens: even if the driver does not have a task group
defined it should still work. The driver pod will be scheduled as a normal pod.
It is the same case as when we run out of placeholders for a task group, normal
scheduling will happen.
The left over placeholders do not make sense. I would suggest to open a new
Jira with the logs to get it looked at. I highly doubt it is linked to the
invalid annotation.
> Application handling with invalid task group annotations
> --------------------------------------------------------
>
> Key: YUNIKORN-1089
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1089
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Priority: Major
>
> In YUNIKORN-1076 we added writing an event to the pod if the task group
> annotation parsing for a gang request failed. We currently accept the
> application and schedule it as if it does not have a gang request defined.
> This might not be what the end user expects.
> The Jira also mentioned failing or rejecting the application if the parsing
> failed. This is a major change:
> * the shim currently does never reject an application
> * is a broken annotation enough reason to reject the application
> Moved out the reject or more invasive handling out of the original Jira so we
> can look at it in more detail.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
