[
https://issues.apache.org/jira/browse/SLIDER-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi updated SLIDER-1100:
-----------------------------------
Description:
I'd like to be able to specify a set of uniquely named components in a group as
follows:
{noformat}
"ROLE": {
"component.unique.names": "true",
"yarn.role.priority": "1",
"yarn.component.instances": 3,
"yarn.memory": "512",
"yarn.vcores": "2"
}
{noformat}
This ROLE would be a component specified in the metainfo, resources, and
appConfig. When Slider sees the "unique.names" property set to true, it will
create uniquely named components ROLE1, ROLE2, ROLE3, up to the number of
instances specified. Each component will have a unique priority as well,
allowing them to be distinguished from each other and strictly placed if
desired.
This would allow the user to issue a flex command such as "slider flex
clusterName --component ROLE 1" to change the number of instances; in this
case, Slider would set ROLE2 and ROLE3 to zero desired instances, and leave
ROLE1 at one desired instance. Uniquely named components would only have 0 or
1 desired instances. If the user flexed to a larger number of instances,
Slider would create new component names as needed (e.g. ROLE4).
was:
I'd like to be able to specify a set of uniquely named components in a group as
follows:
{noformat}
"ROLE": {
"unique.names": "true",
"yarn.role.priority": "1",
"yarn.component.instances": 3,
"yarn.memory": "512",
"yarn.vcores": "2"
}
{noformat}
This ROLE would be a component specified in the metainfo, resources, and
appConfig. When Slider sees the "unique.names" property set to true, it will
create uniquely named components ROLE1, ROLE2, ROLE3, up to the number of
instances specified. Each component will have a unique priority as well,
allowing them to be distinguished from each other and strictly placed if
desired.
This would allow the user to issue a flex command such as "slider flex
clusterName --component ROLE 1" to change the number of instances; in this
case, Slider would set ROLE2 and ROLE3 to zero desired instances, and leave
ROLE1 at one desired instance. Uniquely named components would only have 0 or
1 desired instances. If the user flexed to a larger number of instances,
Slider would create new component names as needed (e.g. ROLE4).
> Support unique component names
> ------------------------------
>
> Key: SLIDER-1100
> URL: https://issues.apache.org/jira/browse/SLIDER-1100
> Project: Slider
> Issue Type: Sub-task
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Fix For: Slider 0.91
>
>
> I'd like to be able to specify a set of uniquely named components in a group
> as follows:
> {noformat}
> "ROLE": {
> "component.unique.names": "true",
> "yarn.role.priority": "1",
> "yarn.component.instances": 3,
> "yarn.memory": "512",
> "yarn.vcores": "2"
> }
> {noformat}
> This ROLE would be a component specified in the metainfo, resources, and
> appConfig. When Slider sees the "unique.names" property set to true, it will
> create uniquely named components ROLE1, ROLE2, ROLE3, up to the number of
> instances specified. Each component will have a unique priority as well,
> allowing them to be distinguished from each other and strictly placed if
> desired.
> This would allow the user to issue a flex command such as "slider flex
> clusterName --component ROLE 1" to change the number of instances; in this
> case, Slider would set ROLE2 and ROLE3 to zero desired instances, and leave
> ROLE1 at one desired instance. Uniquely named components would only have 0
> or 1 desired instances. If the user flexed to a larger number of instances,
> Slider would create new component names as needed (e.g. ROLE4).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
