[jira] [Updated] (YARN-3684) Change ContainerExecutor's primary lifecycle methods to use a more extensible mechanism for passing information.
[ https://issues.apache.org/jira/browse/YARN-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-3684: Attachment: YARN-3684.002.patch Attaching a (correctly-named) patch with fixes to findbugs issues > Change ContainerExecutor's primary lifecycle methods to use a more extensible > mechanism for passing information. > - > > Key: YARN-3684 > URL: https://issues.apache.org/jira/browse/YARN-3684 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana > Attachments: YARN-3648.001.patch, YARN-3684.002.patch > > > As per description in parent JIRA : Adding additional arguments to key > ContainerExecutor methods ( e.g startLocalizer or launchContainer ) would > break the existing ContainerExecutor interface and would require changes to > all executor implementations in YARN. In order to make this interface less > brittle in the future, it would make sense to encapsulate arguments in some > kind of a ‘context’ object which could be modified/extended without breaking > the ContainerExecutor interface in the future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-3684) Change ContainerExecutor's primary lifecycle methods to use a more extensible mechanism for passing information.
[ https://issues.apache.org/jira/browse/YARN-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-3684: Attachment: YARN-3648.001.patch Uploading patch - modifying key methods to use use context objects instead of an argument list. This is more extensible and less brittle. > Change ContainerExecutor's primary lifecycle methods to use a more extensible > mechanism for passing information. > - > > Key: YARN-3684 > URL: https://issues.apache.org/jira/browse/YARN-3684 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana > Attachments: YARN-3648.001.patch > > > As per description in parent JIRA : Adding additional arguments to key > ContainerExecutor methods ( e.g startLocalizer or launchContainer ) would > break the existing ContainerExecutor interface and would require changes to > all executor implementations in YARN. In order to make this interface less > brittle in the future, it would make sense to encapsulate arguments in some > kind of a ‘context’ object which could be modified/extended without breaking > the ContainerExecutor interface in the future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-3684) Change ContainerExecutor's primary lifecycle methods to use a more extensible mechanism for passing information.
[ https://issues.apache.org/jira/browse/YARN-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-3684: Description: As per description in parent JIRA : Adding additional arguments to key ContainerExecutor methods ( e.g startLocalizer or launchContainer ) would break the existing ContainerExecutor interface and would require changes to all executor implementations in YARN. In order to make this interface less brittle in the future, it would make sense to encapsulate arguments in some kind of a ‘context’ object which could be modified/extended without breaking the ContainerExecutor interface in the future. > Change ContainerExecutor's primary lifecycle methods to use a more extensible > mechanism for passing information. > - > > Key: YARN-3684 > URL: https://issues.apache.org/jira/browse/YARN-3684 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana > > As per description in parent JIRA : Adding additional arguments to key > ContainerExecutor methods ( e.g startLocalizer or launchContainer ) would > break the existing ContainerExecutor interface and would require changes to > all executor implementations in YARN. In order to make this interface less > brittle in the future, it would make sense to encapsulate arguments in some > kind of a ‘context’ object which could be modified/extended without breaking > the ContainerExecutor interface in the future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
