[ 
https://issues.apache.org/jira/browse/YUNIKORN-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169821#comment-17169821
 ] 

Wilfred Spiegelenburg commented on YUNIKORN-337:
------------------------------------------------

This is a major refactor. We have not decided how and what as yet. We first 
need to work out a plan to take this forward.
There is also the complicating factor around the plugin that has not been 
described here as yet which we need to take into account.
I short:
The current way the plugin is described and included is left out of the 
interface and we should look at a way to correctly integrate  and incorporate 
that into the shim to core interaction. The current definition only works for a 
shim which is deployed with the core as one executable, i.e. the current 
k8s-shim and core deployment model. Any change to that currently breaks the 
plugins.

> interface message complexity
> ----------------------------
>
>                 Key: YUNIKORN-337
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-337
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: scheduler-interface
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Critical
>
> The current interface allows us to only send one message between a shim and 
> the core. This provides us with a really simple way of interactions 
> definition.
> The complexity is however hidden in the message itself. Every message serves 
> multiple purposes and when the message is received the core and shim need to 
> unpack it and process each part separately and for certain parts in a real 
> specific order.
> Because the message serves a number of purposes it has a large overhead. This 
> might not show up in the code directly as the heavy lifting is done in the 
> generated code. It will show up in the amount of data as a message, even if 
> it does not have all fields, still needs to be encoded in a way that it 
> unpacks correctly on the other side.
> The trade off between having one message with a simple interface or multiple 
> more focussed messages with a slightly more complex interface needs to be 
> assessed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to