[jira] [Updated] (YARN-7323) Data structure update in service REST API
[ https://issues.apache.org/jira/browse/YARN-7323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-7323: -- Description: Changes include - removed the functionality of creating default component if no component specified, this means we always expect user to specify a component. - removed number_of_containers, launch_command, containers from the Service resource object, assuming that each Component has to specify these. resource and artifact in Service object will still remain as the default value for component. - Added a ComponentState object. - Changed the actionCreate to look for the example service from a secondary location. - Fixed a bug in ComponentInstance to handle STOP event on INIT, in case container completed before it gets launched. was: Changes include - removed the functionality of creating default component if no component specified, this means we always expect user to specify a component. - removed number_of_containers, launch_command, containers from the Service resource object, assuming that each Component has to - specify these. resource and artifact in Service object will still remain as the default value for component. - Added a ComponentState object. - Changed the actionCreate to look for the example service from a secondary location. - Fixed a bug in ComponentInstance to handle STOP event on INIT, in case container completed before it gets launched. > Data structure update in service REST API > - > > Key: YARN-7323 > URL: https://issues.apache.org/jira/browse/YARN-7323 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Jian He >Assignee: Jian He > Attachments: YARN-7323.yarn-native-services.01.patch, > YARN-7323.yarn-native-services.02.patch, > YARN-7323.yarn-native-services.03.patch > > > Changes include > - removed the functionality of creating default component if no component > specified, this means we always expect user to specify a component. > - removed number_of_containers, launch_command, containers from the Service > resource object, assuming that each Component has to > specify these. resource and artifact in Service object will still remain as > the default value for component. > - Added a ComponentState object. > - Changed the actionCreate to look for the example service from a secondary > location. > - Fixed a bug in ComponentInstance to handle STOP event on INIT, in case > container completed before it gets launched. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7323) Data structure update in service REST API
[ https://issues.apache.org/jira/browse/YARN-7323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-7323: -- Description: Changes include - removed the functionality of creating default component if no component specified, this means we always expect user to specify a component. - removed number_of_containers, launch_command, containers from the Service resource object, assuming that each Component has to - specify these. resource and artifact in Service object will still remain as the default value for component. - Added a ComponentState object. - Changed the actionCreate to look for the example service from a secondary location. - Fixed a bug in ComponentInstance to handle STOP event on INIT, in case container completed before it gets launched. was: Unix terminology implies daemon process, such as httpd as a service. In Hadoop terminology, hdfs is a file system service, and hdfs has various components such as namenode, journal nodes, and datanodes. YARN service data model was more closely describing daemon process as a service. This JIRA propose to remap the YARN service data model to align with Hadoop terminology. Service is composed of a collection of components. Component is either a unix process or docker container. Data structure for Yarnfile organized launched_command and state at Service level, but the grouping definition was following Hadoop terminology. For clarity, we will change data structure to match Hadoop terminology. State and launch commands are moved to component level. > Data structure update in service REST API > - > > Key: YARN-7323 > URL: https://issues.apache.org/jira/browse/YARN-7323 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Jian He >Assignee: Jian He > Attachments: YARN-7323.yarn-native-services.01.patch, > YARN-7323.yarn-native-services.02.patch, > YARN-7323.yarn-native-services.03.patch > > > Changes include > - removed the functionality of creating default component if no component > specified, this means we always expect user to specify a component. > - removed number_of_containers, launch_command, containers from the Service > resource object, assuming that each Component has to - > specify these. resource and artifact in Service object will still remain as > the default value for component. > - Added a ComponentState object. > - Changed the actionCreate to look for the example service from a secondary > location. > - Fixed a bug in ComponentInstance to handle STOP event on INIT, in case > container completed before it gets launched. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7323) Data structure update in service REST API
[ https://issues.apache.org/jira/browse/YARN-7323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-7323: -- Attachment: YARN-7323.yarn-native-services.03.patch Chatted with Gour, made two changes - rename ServiceState#Ready to be stable to be consistent with ComponentState - removed ComponentState#INIT, because it's a state that will never be seen. > Data structure update in service REST API > - > > Key: YARN-7323 > URL: https://issues.apache.org/jira/browse/YARN-7323 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Jian He >Assignee: Jian He > Attachments: YARN-7323.yarn-native-services.01.patch, > YARN-7323.yarn-native-services.02.patch, > YARN-7323.yarn-native-services.03.patch > > > Unix terminology implies daemon process, such as httpd as a service. In > Hadoop terminology, hdfs is a file system service, and hdfs has various > components such as namenode, journal nodes, and datanodes. YARN service data > model was more closely describing daemon process as a service. This JIRA > propose to remap the YARN service data model to align with Hadoop > terminology. Service is composed of a collection of components. Component > is either a unix process or docker container. > > Data structure for Yarnfile organized launched_command and state at Service > level, but the grouping definition was following Hadoop terminology. For > clarity, we will change data structure to match Hadoop terminology. State > and launch commands are moved to component level. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7323) Data structure update in service REST API
[ https://issues.apache.org/jira/browse/YARN-7323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang updated YARN-7323: Description: Unix terminology implies daemon process, such as httpd as a service. In Hadoop terminology, hdfs is a file system service, and hdfs has various components such as namenode, journal nodes, and datanodes. YARN service data model was more closely describing daemon process as a service. This JIRA propose to remap the YARN service data model to align with Hadoop terminology. Service is composed of a collection of components. Component is either a unix process or docker container. Data structure for Yarnfile organized launched_command and state at Service level, but the grouping definition was following Hadoop terminology. For clarity, we will change data structure to match Hadoop terminology. State and launch commands are moved to component level. was:Data structure for Yarnfile organized state at service level. > Data structure update in service REST API > - > > Key: YARN-7323 > URL: https://issues.apache.org/jira/browse/YARN-7323 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Jian He >Assignee: Jian He > Attachments: YARN-7323.yarn-native-services.01.patch, > YARN-7323.yarn-native-services.02.patch > > > Unix terminology implies daemon process, such as httpd as a service. In > Hadoop terminology, hdfs is a file system service, and hdfs has various > components such as namenode, journal nodes, and datanodes. YARN service data > model was more closely describing daemon process as a service. This JIRA > propose to remap the YARN service data model to align with Hadoop > terminology. Service is composed of a collection of components. Component > is either a unix process or docker container. > > Data structure for Yarnfile organized launched_command and state at Service > level, but the grouping definition was following Hadoop terminology. For > clarity, we will change data structure to match Hadoop terminology. State > and launch commands are moved to component level. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7323) Data structure update in service REST API
[ https://issues.apache.org/jira/browse/YARN-7323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang updated YARN-7323: Summary: Data structure update in service REST API (was: Some changes in service REST API) > Data structure update in service REST API > - > > Key: YARN-7323 > URL: https://issues.apache.org/jira/browse/YARN-7323 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Jian He >Assignee: Jian He > Attachments: YARN-7323.yarn-native-services.01.patch, > YARN-7323.yarn-native-services.02.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7323) Data structure update in service REST API
[ https://issues.apache.org/jira/browse/YARN-7323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang updated YARN-7323: Description: Data structure for Yarnfile organized state at service level. > Data structure update in service REST API > - > > Key: YARN-7323 > URL: https://issues.apache.org/jira/browse/YARN-7323 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Jian He >Assignee: Jian He > Attachments: YARN-7323.yarn-native-services.01.patch, > YARN-7323.yarn-native-services.02.patch > > > Data structure for Yarnfile organized state at service level. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
