[jira] [Updated] (TEZ-3866) add ability to pass information between plugins

2017-11-16 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated TEZ-3866:
--
Description: 
Distinct from TEZ-3815, since even with a hack that makes plugins aware of each 
other, they cannot store task-specific info without calling into each others' 
per-task structures.

In particular, I need a piece of info that is generated when the custom 
scheduler calls getContext().taskAllocated, to be propagated to communicator 
plugin registerRunningTaskAttempt, so that the custom communicator could 
include additional info in task submission (e.g. a scheduler-specific priority 
or other instructions). There doesn't seem to be any means to do it now.

  was:
Distinct from TEZ-3815, since even with a hack that makes plugins aware of each 
other, they cannot store task-specific info without calling into each others' 
per-task structures.

In particular, I need a piece of info that is generated when the custom 
scheduler calls getContext().taskAllocated, to be propagated to communicator 
plugin registerRunningTaskAttempt, so that the custom communicator could 
include additional info in task submission. There doesn't seem to be any means 
to do it now.


> add ability to pass information between plugins
> ---
>
> Key: TEZ-3866
> URL: https://issues.apache.org/jira/browse/TEZ-3866
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>
> Distinct from TEZ-3815, since even with a hack that makes plugins aware of 
> each other, they cannot store task-specific info without calling into each 
> others' per-task structures.
> In particular, I need a piece of info that is generated when the custom 
> scheduler calls getContext().taskAllocated, to be propagated to communicator 
> plugin registerRunningTaskAttempt, so that the custom communicator could 
> include additional info in task submission (e.g. a scheduler-specific 
> priority or other instructions). There doesn't seem to be any means to do it 
> now.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (TEZ-3866) add ability to pass information between plugins

2017-11-15 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated TEZ-3866:
--
Description: 
Distinct from TEZ-3815, since even with a hack that makes plugins aware of each 
other, they cannot store task-specific info without calling into each others' 
per-task structures.

In particular, I need a piece of info that is generated when the custom 
scheduler calls getContext().taskAllocated, to be propagated to communicator 
plugin registerRunningTaskAttempt, so that the custom communicator could 
include additional info in task submission. There doesn't seem to be any means 
to do it now.

  was:
Distinct from TEZ-3815, since even with the hack that makes plugins aware of 
each other, they cannot store task-specific info without calling into each 
others' per-task structures.

In particular, I need a piece of info that is generated when the custom 
scheduler calls getContext().taskAllocated, to be propagated to communicator 
plugin registerRunningTaskAttempt, so that the custom communicator could 
include additional info in task submission. There doesn't seem to be any means 
to do it now.


> add ability to pass information between plugins
> ---
>
> Key: TEZ-3866
> URL: https://issues.apache.org/jira/browse/TEZ-3866
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>
> Distinct from TEZ-3815, since even with a hack that makes plugins aware of 
> each other, they cannot store task-specific info without calling into each 
> others' per-task structures.
> In particular, I need a piece of info that is generated when the custom 
> scheduler calls getContext().taskAllocated, to be propagated to communicator 
> plugin registerRunningTaskAttempt, so that the custom communicator could 
> include additional info in task submission. There doesn't seem to be any 
> means to do it now.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)