[jira] [Commented] (YARN-7528) Resource types that use units need to be defined at RM level and NM level or when using small units you will overflow max_allocation calculation
[ https://issues.apache.org/jira/browse/YARN-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331209#comment-16331209 ] Grant Sohn commented on YARN-7528: -- You might want to check with [~templedf] on this. He might recall the specific instance better. > Resource types that use units need to be defined at RM level and NM level or > when using small units you will overflow max_allocation calculation > > > Key: YARN-7528 > URL: https://issues.apache.org/jira/browse/YARN-7528 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation, resourcemanager >Affects Versions: 3.0.0 >Reporter: Grant Sohn >Assignee: Szilard Nemeth >Priority: Major > > When the unit is not defined in the RM, the LONG_MAX default will overflow in > the conversion step. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7528) Resource types that use units need to be defined at RM level and NM level or when using small units you will overflow max_allocation calculation
[ https://issues.apache.org/jira/browse/YARN-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327989#comment-16327989 ] Grant Sohn commented on YARN-7528: -- Yes. > Resource types that use units need to be defined at RM level and NM level or > when using small units you will overflow max_allocation calculation > > > Key: YARN-7528 > URL: https://issues.apache.org/jira/browse/YARN-7528 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation, resourcemanager >Affects Versions: 3.0.0 >Reporter: Grant Sohn >Assignee: Szilard Nemeth >Priority: Major > > When the unit is not defined in the RM, the LONG_MAX default will overflow in > the conversion step. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7528) Resource types that use units need to be defined at RM level and NM level or when using small units you will overflow max_allocation calculation
[ https://issues.apache.org/jira/browse/YARN-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327796#comment-16327796 ] Grant Sohn commented on YARN-7528: -- I believe when the resource type unit is `m` you use a value without units to trigger overflow. > Resource types that use units need to be defined at RM level and NM level or > when using small units you will overflow max_allocation calculation > > > Key: YARN-7528 > URL: https://issues.apache.org/jira/browse/YARN-7528 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation, resourcemanager >Affects Versions: 3.0.0 >Reporter: Grant Sohn >Assignee: Szilard Nemeth >Priority: Major > > When the unit is not defined in the RM, the LONG_MAX default will overflow in > the conversion step. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6894) RM Apps API returns only active apps when query parameter queue used
[ https://issues.apache.org/jira/browse/YARN-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310250#comment-16310250 ] Grant Sohn commented on YARN-6894: -- Thanks [~miklos.szeg...@cloudera.com] for committing this on congratulations on your committership! > RM Apps API returns only active apps when query parameter queue used > > > Key: YARN-6894 > URL: https://issues.apache.org/jira/browse/YARN-6894 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, restapi >Reporter: Grant Sohn >Assignee: Gergely Novák >Priority: Minor > Fix For: 3.1.0 > > Attachments: YARN-6894.001.patch, YARN-6894.002.patch, > YARN-6894.003.patch > > > If you run RM's Cluster Applications API with no query parameters, you get a > list of apps. > If you run RM's Cluster Applications API with any query parameters other than > "queue" you get the list of apps with the parameter filters being applied. > However, when you use the "queue" query parameter, you only see the > applications that are active in the cluster (NEW, NEW_SAVING, SUBMITTED, > ACCEPTED, RUNNING). This behavior is inconsistent with the API. If there is > a sound reason behind this, it should be documented and it seems like there > might be as the mapred queue CLI behaves similarly. > http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API -- 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] [Created] (YARN-7627) [ATSv2] When passing a non-number as metricslimit, the error message is wrong
Grant Sohn created YARN-7627:
Summary: [ATSv2] When passing a non-number as metricslimit, the
error message is wrong
Key: YARN-7627
URL: https://issues.apache.org/jira/browse/YARN-7627
Project: Hadoop YARN
Issue Type: Bug
Components: api
Affects Versions: 3.0.0-beta1
Reporter: Grant Sohn
Priority: Trivial
curl
"$ATS_URL/ws/v2/timeline/apps/application_1512430070811_0022/entities/MAPREDUCE_JOB?metricslimit=w"
returns:
{"exception":"BadRequestException","message":"java.lang.Exception: createdTime
start/end or limit or flowrunid is not a numeric
value.","javaClassName":"org.apache.hadoop.yarn.webapp.BadRequestException"}
and:
curl
"$ATS_URL/ws/v2/timeline/apps/application_1512430070811_0022?metricslimit=ALL"
{"exception":"BadRequestException","message":"java.lang.Exception: flowrunid is
not a numeric
value.","javaClassName":"org.apache.hadoop.yarn.webapp.BadRequestException"}
This could be part of YARN-6389 which indicates this functionality was not
completed.
--
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-7549) RM cluster scheduler API does not show resource types usage for fair scheduler
[ https://issues.apache.org/jira/browse/YARN-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-7549: - Summary: RM cluster scheduler API does not show resource types usage for fair scheduler (was: RM cluster scheduler API does not show resource types usage) > RM cluster scheduler API does not show resource types usage for fair scheduler > -- > > Key: YARN-7549 > URL: https://issues.apache.org/jira/browse/YARN-7549 > Project: Hadoop YARN > Issue Type: Bug > Components: fairscheduler, resourcemanager, restapi >Affects Versions: 3.0.0 >Reporter: Grant Sohn > > To maintain consistency with the RM web UI, the resource types should be > added to: > - max resources > - used resources > - demand resources > - steady fair share -- 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-7549) RM cluster scheduler API does not show resource types usage
[ https://issues.apache.org/jira/browse/YARN-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-7549: - Component/s: fairscheduler > RM cluster scheduler API does not show resource types usage > --- > > Key: YARN-7549 > URL: https://issues.apache.org/jira/browse/YARN-7549 > Project: Hadoop YARN > Issue Type: Bug > Components: fairscheduler, resourcemanager, restapi >Affects Versions: 3.0.0 >Reporter: Grant Sohn > > To maintain consistency with the RM web UI, the resource types should be > added to: > - max resources > - used resources > - demand resources > - steady fair share -- 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] [Created] (YARN-7549) RM cluster scheduler API does not show resource types usage
Grant Sohn created YARN-7549: Summary: RM cluster scheduler API does not show resource types usage Key: YARN-7549 URL: https://issues.apache.org/jira/browse/YARN-7549 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager, restapi Affects Versions: 3.0.0 Reporter: Grant Sohn To maintain consistency with the RM web UI, the resource types should be added to: - max resources - used resources - demand resources - steady fair share -- 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] [Commented] (YARN-7451) Resources Types should be visible in the Cluster Apps API "resourceRequests" section
[ https://issues.apache.org/jira/browse/YARN-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261256#comment-16261256 ] Grant Sohn commented on YARN-7451: -- Based on discussions with [~templedf], this should be part of the capability map. > Resources Types should be visible in the Cluster Apps API "resourceRequests" > section > > > Key: YARN-7451 > URL: https://issues.apache.org/jira/browse/YARN-7451 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, restapi >Affects Versions: 3.0.0 >Reporter: Grant Sohn >Assignee: Yufei Gu > > When running jobs that request resource types the RM Cluster Apps API should > include this in the "resourceRequests" object. -- 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] [Commented] (YARN-7545) RM REST API cluster apps missing documentation for "resourceRequests"
[
https://issues.apache.org/jira/browse/YARN-7545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260337#comment-16260337
]
Grant Sohn commented on YARN-7545:
--
An example in the example XML is:
{noformat}
4096
1
0
0
true
*
4096
1
0
20
true
host1.domain.com
4096
1
0
20
true
host2.domain.com
{noformat}
> RM REST API cluster apps missing documentation for "resourceRequests"
> -
>
> Key: YARN-7545
> URL: https://issues.apache.org/jira/browse/YARN-7545
> Project: Hadoop YARN
> Issue Type: Bug
> Components: documentation, resourcemanager, restapi
>Affects Versions: 3.0.0
>Reporter: Grant Sohn
>Priority: Minor
>
> I see "resourceRequests" when running the RM Cluster Apps API however it is
> not mentioned in the current docs though it's visible in the example output.
> http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API
--
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] [Created] (YARN-7545) RM REST API cluster apps missing documentation for "resourceRequests"
Grant Sohn created YARN-7545: Summary: RM REST API cluster apps missing documentation for "resourceRequests" Key: YARN-7545 URL: https://issues.apache.org/jira/browse/YARN-7545 Project: Hadoop YARN Issue Type: Bug Components: documentation, resourcemanager, restapi Affects Versions: 3.0.0 Reporter: Grant Sohn Priority: Minor I see "resourceRequests" when running the RM Cluster Apps API however it is not mentioned in the current docs though it's visible in the example output. http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API -- 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] [Commented] (YARN-7528) Resource types that use units need to be defined at RM level and NM level or when using small units you will overflow max
[
https://issues.apache.org/jira/browse/YARN-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257725#comment-16257725
]
Grant Sohn commented on YARN-7528:
--
Resource Manager exception is:
{noformat}
java.lang.IllegalArgumentException: Converting 9223372036854775807 from '' to
'm' will result in an overflow of Long
at
org.apache.hadoop.yarn.util.UnitsConversionUtil.convert(UnitsConversionUtil.java:160)
at
org.apache.hadoop.yarn.util.resource.DominantResourceCalculator.normalize(DominantResourceCalculator.java:444)
at
org.apache.hadoop.yarn.util.resource.Resources.normalize(Resources.java:392)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.getNormalizedResource(SchedulerUtils.java:177)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.getNormalizedResource(FairScheduler.java:782)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.AbstractYarnScheduler.normalizeRequests(AbstractYarnScheduler.java:1137)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.allocate(FairScheduler.java:828)
at
org.apache.hadoop.yarn.server.resourcemanager.DefaultAMSProcessor.allocate(DefaultAMSProcessor.java:265)
at
org.apache.hadoop.yarn.server.resourcemanager.AMSProcessingChain.allocate(AMSProcessingChain.java:92)
at
org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService.allocate(ApplicationMasterService.java:388)
at
org.apache.hadoop.yarn.api.impl.pb.service.ApplicationMasterProtocolPBServiceImpl.allocate(ApplicationMasterProtocolPBServiceImpl.java:60)
at
org.apache.hadoop.yarn.proto.ApplicationMasterProtocol$ApplicationMasterProtocolService$2.callBlockingMethod(ApplicationMasterProtocol.java:99)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:869)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:815)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
{noformat}
> Resource types that use units need to be defined at RM level and NM level or
> when using small units you will overflow max
> -
>
> Key: YARN-7528
> URL: https://issues.apache.org/jira/browse/YARN-7528
> Project: Hadoop YARN
> Issue Type: Bug
> Components: documentation, resourcemanager
>Affects Versions: 3.0.0
>Reporter: Grant Sohn
>Assignee: Daniel Templeton
>
> When the unit is not defined in the RM, the LONG_MAX default will overflow in
> the conversion step.
--
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-7528) Resource types that use units need to be defined at RM level and NM level or when using small units you will overflow max_allocation calculation
[ https://issues.apache.org/jira/browse/YARN-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-7528: - Summary: Resource types that use units need to be defined at RM level and NM level or when using small units you will overflow max_allocation calculation (was: Resource types that use units need to be defined at RM level and NM level or when using small units you will overflow max) > Resource types that use units need to be defined at RM level and NM level or > when using small units you will overflow max_allocation calculation > > > Key: YARN-7528 > URL: https://issues.apache.org/jira/browse/YARN-7528 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation, resourcemanager >Affects Versions: 3.0.0 >Reporter: Grant Sohn >Assignee: Daniel Templeton > > When the unit is not defined in the RM, the LONG_MAX default will overflow in > the conversion step. -- 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-7528) Resource types that use units need to be defined at RM level and NM level or when using small units you will overflow max
[ https://issues.apache.org/jira/browse/YARN-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-7528: - Summary: Resource types that use units need to be defined at RM level and NM level or when using small units you will overflow max (was: Need to document that resource types that use units need to be defined at RM level and NM level) > Resource types that use units need to be defined at RM level and NM level or > when using small units you will overflow max > - > > Key: YARN-7528 > URL: https://issues.apache.org/jira/browse/YARN-7528 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation, resourcemanager >Affects Versions: 3.0.0 >Reporter: Grant Sohn >Assignee: Daniel Templeton > > When the unit is not defined in the RM, the LONG_MAX default will overflow in > the conversion step. -- 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-7528) Need to document that resource types that use units need to be defined at RM level and NM level
[ https://issues.apache.org/jira/browse/YARN-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-7528: - Component/s: resourcemanager > Need to document that resource types that use units need to be defined at RM > level and NM level > --- > > Key: YARN-7528 > URL: https://issues.apache.org/jira/browse/YARN-7528 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation, resourcemanager >Affects Versions: 3.0.0 >Reporter: Grant Sohn >Assignee: Daniel Templeton > > When the unit is not defined in the RM, the LONG_MAX default will overflow in > the conversion step. -- 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] [Commented] (YARN-7528) Need to document that resource types that use units need to be defined at RM level and NM level
[ https://issues.apache.org/jira/browse/YARN-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257713#comment-16257713 ] Grant Sohn commented on YARN-7528: -- This has the unpleasant side-effect of causing the job to hang. > Need to document that resource types that use units need to be defined at RM > level and NM level > --- > > Key: YARN-7528 > URL: https://issues.apache.org/jira/browse/YARN-7528 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation >Affects Versions: 3.0.0 >Reporter: Grant Sohn >Assignee: Daniel Templeton > > When the unit is not defined in the RM, the LONG_MAX default will overflow in > the conversion step. -- 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] [Created] (YARN-7528) Need to document that resource types that use units need to be defined at RM level and NM level
Grant Sohn created YARN-7528: Summary: Need to document that resource types that use units need to be defined at RM level and NM level Key: YARN-7528 URL: https://issues.apache.org/jira/browse/YARN-7528 Project: Hadoop YARN Issue Type: Bug Components: documentation Affects Versions: 3.0.0 Reporter: Grant Sohn Assignee: Daniel Templeton When the unit is not defined in the RM, the LONG_MAX default will overflow in the conversion step. -- 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] [Commented] (YARN-5591) Update web UIs to reflect multiple resource types
[ https://issues.apache.org/jira/browse/YARN-5591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242922#comment-16242922 ] Grant Sohn commented on YARN-5591: -- The Applications page and the Scheduler page should include resource types information. The Application page: Under "Scheduler Metrics" the "Maximum Allocation" should show resource types and their max allocations. The Scheduler page: Under "Application Queues": All the resources per queue should reflect any resource types used / available. > Update web UIs to reflect multiple resource types > - > > Key: YARN-5591 > URL: https://issues.apache.org/jira/browse/YARN-5591 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager >Reporter: Varun Vasudev >Assignee: Varun Vasudev > -- 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] [Created] (YARN-7451) Resources Types should be visible in the Cluster Apps API "resourceRequests" section
Grant Sohn created YARN-7451: Summary: Resources Types should be visible in the Cluster Apps API "resourceRequests" section Key: YARN-7451 URL: https://issues.apache.org/jira/browse/YARN-7451 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager, restapi Affects Versions: 3.0.0 Reporter: Grant Sohn When running jobs that request resource types the RM Cluster Apps API should include this in the "resourceRequests" object. -- 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] [Commented] (YARN-6912) Cluster Metrics API should report resource types information
[ https://issues.apache.org/jira/browse/YARN-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241173#comment-16241173 ] Grant Sohn commented on YARN-6912: -- This might be unnecessary based on what was done for Node Labels which is a similar type of feature. > Cluster Metrics API should report resource types information > > > Key: YARN-6912 > URL: https://issues.apache.org/jira/browse/YARN-6912 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Affects Versions: YARN-3926 >Reporter: Daniel Templeton > -- 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] [Commented] (YARN-3581) Deprecate -directlyAccessNodeLabelStore in RMAdminCLI
[ https://issues.apache.org/jira/browse/YARN-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197597#comment-16197597 ] Grant Sohn commented on YARN-3581: -- Is this going to be removed in Hadoop 3? It's been deprecated a long time. Thanks. > Deprecate -directlyAccessNodeLabelStore in RMAdminCLI > - > > Key: YARN-3581 > URL: https://issues.apache.org/jira/browse/YARN-3581 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, client, resourcemanager >Reporter: Wangda Tan >Assignee: Naganarasimha G R > Fix For: 2.8.0, 3.0.0-alpha1 > > Attachments: YARN-3581.20150525-1.patch, YARN-3581.20150528-1.patch > > > In 2.6.0, we added an option called "-directlyAccessNodeLabelStore" to make > RM can start with label-configured queue settings. After YARN-2918, we don't > need this option any more, admin can configure queue setting, start RM and > configure node label via RMAdminCLI without any error. > In addition, this option is very restrictive, first it needs to run on the > same node where RM is running if admin configured to store labels in local > disk. > Second, when admin run the option when RM is running, multiple process write > to a same file can happen, this could make node label store becomes invalid. -- 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] [Created] (YARN-7200) SLS generates a realtimetrack.json file but that file is missing the closing ']'
Grant Sohn created YARN-7200:
Summary: SLS generates a realtimetrack.json file but that file is
missing the closing ']'
Key: YARN-7200
URL: https://issues.apache.org/jira/browse/YARN-7200
Project: Hadoop YARN
Issue Type: Bug
Components: scheduler-load-simulator
Reporter: Grant Sohn
Priority: Minor
File
hadoop-tools/hadoop-sls/src/main/java/org/apache/hadoop/yarn/sls/scheduler/SchedulerMetrics.java
shows:
{noformat}
void tearDown() throws Exception {
if (metricsLogBW != null) {
metricsLogBW.write("]");
metricsLogBW.close();
}
{noformat}
So the exit logic is flawed.
--
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] [Commented] (YARN-7162) Remove XML excludes file format
[ https://issues.apache.org/jira/browse/YARN-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16165369#comment-16165369 ] Grant Sohn commented on YARN-7162: -- +1 (non-binding) > Remove XML excludes file format > --- > > Key: YARN-7162 > URL: https://issues.apache.org/jira/browse/YARN-7162 > Project: Hadoop YARN > Issue Type: Sub-task > Components: graceful >Affects Versions: 2.9.0, 3.0.0-beta1 >Reporter: Robert Kanter >Assignee: Robert Kanter >Priority: Blocker > Attachments: YARN-7162.001.patch, YARN-7162.branch-2.001.patch > > > YARN-5536 aims to replace the XML format for the excludes file with a JSON > format. However, it looks like we won't have time for that for Hadoop 3 Beta > 1. The concern is that if we release it as-is, we'll now have to support the > XML format as-is for all of Hadoop 3.x, which we're either planning on > removing, or rewriting using a pluggable framework. > [This comment in > YARN-5536|https://issues.apache.org/jira/browse/YARN-5536?focusedCommentId=16126194=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16126194] > proposed two quick solutions to prevent this compat issue. In this JIRA, > we're going to remove the XML format. If we later want to add it back in, > YARN-5536 can add it back, rewriting it to be in the pluggable framework. -- 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] [Commented] (YARN-7009) TestNMClient.testNMClientNoCleanupOnStop is flaky by design
[
https://issues.apache.org/jira/browse/YARN-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16165016#comment-16165016
]
Grant Sohn commented on YARN-7009:
--
+1 (non-binding).
> TestNMClient.testNMClientNoCleanupOnStop is flaky by design
> ---
>
> Key: YARN-7009
> URL: https://issues.apache.org/jira/browse/YARN-7009
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Miklos Szegedi
>Assignee: Miklos Szegedi
> Attachments: YARN-7009.000.patch, YARN-7009.001.patch,
> YARN-7009.002.patch
>
>
> The sleeps to wait for a transition to reinit and than back to running is not
> long enough, it can miss the reinit event.
> {code}
> java.lang.AssertionError: Exception is not expected:
> org.apache.hadoop.yarn.exceptions.YarnException: Cannot perform RE_INIT on
> [container_1502735389852_0001_01_01]. Current state is [REINITIALIZING,
> isReInitializing=true].
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.preReInitializeOrLocalizeCheck(ContainerManagerImpl.java:1772)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.reInitializeContainer(ContainerManagerImpl.java:1697)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.reInitializeContainer(ContainerManagerImpl.java:1668)
> at
> org.apache.hadoop.yarn.api.impl.pb.service.ContainerManagementProtocolPBServiceImpl.reInitializeContainer(ContainerManagementProtocolPBServiceImpl.java:214)
> at
> org.apache.hadoop.yarn.proto.ContainerManagementProtocol$ContainerManagementProtocolService$2.callBlockingMethod(ContainerManagementProtocol.java:237)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:869)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:815)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2675)
> at
> org.apache.hadoop.yarn.client.api.impl.TestNMClient.testReInitializeContainer(TestNMClient.java:567)
> at
> org.apache.hadoop.yarn.client.api.impl.TestNMClient.testContainerManagement(TestNMClient.java:405)
> at
> org.apache.hadoop.yarn.client.api.impl.TestNMClient.testNMClientNoCleanupOnStop(TestNMClient.java:214)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> Caused by: org.apache.hadoop.yarn.exceptions.YarnException: Cannot perform
> RE_INIT on [container_1502735389852_0001_01_01]. Current state is
> [REINITIALIZING, isReInitializing=true].
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.preReInitializeOrLocalizeCheck(ContainerManagerImpl.java:1772)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.reInitializeContainer(ContainerManagerImpl.java:1697)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.reInitializeContainer(ContainerManagerImpl.java:1668)
> at
> org.apache.hadoop.yarn.api.impl.pb.service.ContainerManagementProtocolPBServiceImpl.reInitializeContainer(ContainerManagementProtocolPBServiceImpl.java:214)
> at
> org.apache.hadoop.yarn.proto.ContainerManagementProtocol$ContainerManagementProtocolService$2.callBlockingMethod(ContainerManagementProtocol.java:237)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:869)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:815)
> at
[jira] [Commented] (YARN-7146) Many RM unit tests failing with FairScheduler
[
https://issues.apache.org/jira/browse/YARN-7146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16163660#comment-16163660
]
Grant Sohn commented on YARN-7146:
--
+1 (non-binding) LGTM.
> Many RM unit tests failing with FairScheduler
> -
>
> Key: YARN-7146
> URL: https://issues.apache.org/jira/browse/YARN-7146
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Affects Versions: 3.0.0-beta1
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: YARN-7146.001.patch, YARN-7146.002.patch,
> YARN-7146.003.patch, YARN-7146.004.patch
>
>
> Many of the RM unit tests are failing when using the FairScheduler.
> Here is a list of affected test classes:
> {noformat}
> TestYarnClient
> TestApplicationCleanup
> TestApplicationMasterLauncher
> TestDecommissioningNodesWatcher
> TestKillApplicationWithRMHA
> TestNodeBlacklistingOnAMFailures
> TestRM
> TestRMAdminService
> TestRMRestart
> TestResourceTrackerService
> TestWorkPreservingRMRestart
> TestAMRMRPCNodeUpdates
> TestAMRMRPCResponseId
> TestAMRestart
> TestApplicationLifetimeMonitor
> TestNodesListManager
> TestRMContainerImpl
> TestAbstractYarnScheduler
> TestSchedulerUtils
> TestFairOrderingPolicy
> TestAMRMTokens
> TestDelegationTokenRenewer
> {noformat}
> Most of the test methods in these classes are failing, though some do succeed.
> There's two main categories of issues:
> # The test submits an application to the {{MockRM}} and waits for it to enter
> a specific state, which it never does, and the test times out. We need to
> call {{update()}} on the scheduler.
> # The test throws a {{ClassCastException}} on {{FSQueueMetrics}} to
> {{CSQueueMetrics}}. This is because {{QueueMetrics}} metrics are static, and
> a previous test using FairScheduler initialized it, and the current test is
> using CapacityScheduler. We need to reset the metrics.
--
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] [Commented] (YARN-6546) SLS is slow while loading 10k queues
[
https://issues.apache.org/jira/browse/YARN-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16163327#comment-16163327
]
Grant Sohn commented on YARN-6546:
--
+1 (non-binding). Thanks for getting this addressed.
> SLS is slow while loading 10k queues
>
>
> Key: YARN-6546
> URL: https://issues.apache.org/jira/browse/YARN-6546
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: scheduler-load-simulator
>Affects Versions: 3.0.0-alpha2
>Reporter: Yufei Gu
>Assignee: Yufei Gu
> Attachments: Desktop.png, YARN-6546.001.patch
>
>
> It takes a long time (more than 10 minutes) to load 10k queues in SLS. The
> problem should be in {{com.codahale.metrics.CsvReporter}} based on the result
> from profiler. SLS creates 14 .csv files for each leaf queue, and update them
> constantly during execution. It is not necessary to log information for
> inactive queues.
--
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] [Commented] (YARN-6894) RM Apps API returns only active apps when query parameter queue used
[ https://issues.apache.org/jira/browse/YARN-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144365#comment-16144365 ] Grant Sohn commented on YARN-6894: -- +1 (non-binding) > RM Apps API returns only active apps when query parameter queue used > > > Key: YARN-6894 > URL: https://issues.apache.org/jira/browse/YARN-6894 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, restapi >Reporter: Grant Sohn >Assignee: Gergely Novák >Priority: Minor > Attachments: YARN-6894.001.patch, YARN-6894.002.patch > > > If you run RM's Cluster Applications API with no query parameters, you get a > list of apps. > If you run RM's Cluster Applications API with any query parameters other than > "queue" you get the list of apps with the parameter filters being applied. > However, when you use the "queue" query parameter, you only see the > applications that are active in the cluster (NEW, NEW_SAVING, SUBMITTED, > ACCEPTED, RUNNING). This behavior is inconsistent with the API. If there is > a sound reason behind this, it should be documented and it seems like there > might be as the mapred queue CLI behaves similarly. > http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API -- 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] [Commented] (YARN-6894) RM Apps API returns only active apps when query parameter queue used
[ https://issues.apache.org/jira/browse/YARN-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141825#comment-16141825 ] Grant Sohn commented on YARN-6894: -- Yeah, that is a better approach. I assume you're referring to the paragraph under "Query Parameters Supported". > RM Apps API returns only active apps when query parameter queue used > > > Key: YARN-6894 > URL: https://issues.apache.org/jira/browse/YARN-6894 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, restapi >Reporter: Grant Sohn >Assignee: Gergely Novák >Priority: Minor > Attachments: YARN-6894.001.patch > > > If you run RM's Cluster Applications API with no query parameters, you get a > list of apps. > If you run RM's Cluster Applications API with any query parameters other than > "queue" you get the list of apps with the parameter filters being applied. > However, when you use the "queue" query parameter, you only see the > applications that are active in the cluster (NEW, NEW_SAVING, SUBMITTED, > ACCEPTED, RUNNING). This behavior is inconsistent with the API. If there is > a sound reason behind this, it should be documented and it seems like there > might be as the mapred queue CLI behaves similarly. > http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API -- 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-6088) RM UI has to redirect to AHS for completed applications logs
[ https://issues.apache.org/jira/browse/YARN-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6088: - Issue Type: Task (was: New Feature) > RM UI has to redirect to AHS for completed applications logs > > > Key: YARN-6088 > URL: https://issues.apache.org/jira/browse/YARN-6088 > Project: Hadoop YARN > Issue Type: Task > Components: webapp >Affects Versions: 2.7.3 >Reporter: Sunil G > > Currently AMContainer logs link in RMAppBlock is hardcoded containers' host > node. If that node unavailable, we will not have enough information. -- 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] [Commented] (YARN-6088) RM UI has to redirect to AHS for completed applications logs
[ https://issues.apache.org/jira/browse/YARN-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129221#comment-16129221 ] Grant Sohn commented on YARN-6088: -- FYI - just trying a few things on atlassian to try to close the duplicates. > RM UI has to redirect to AHS for completed applications logs > > > Key: YARN-6088 > URL: https://issues.apache.org/jira/browse/YARN-6088 > Project: Hadoop YARN > Issue Type: New Feature > Components: webapp >Affects Versions: 2.7.3 >Reporter: Sunil G > > Currently AMContainer logs link in RMAppBlock is hardcoded containers' host > node. If that node unavailable, we will not have enough information. -- 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-6088) RM UI has to redirect to AHS for completed applications logs
[ https://issues.apache.org/jira/browse/YARN-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6088: - Issue Type: New Feature (was: Task) > RM UI has to redirect to AHS for completed applications logs > > > Key: YARN-6088 > URL: https://issues.apache.org/jira/browse/YARN-6088 > Project: Hadoop YARN > Issue Type: New Feature > Components: webapp >Affects Versions: 2.7.3 >Reporter: Sunil G > > Currently AMContainer logs link in RMAppBlock is hardcoded containers' host > node. If that node unavailable, we will not have enough information. -- 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-6088) RM UI has to redirect to AHS for completed applications logs
[ https://issues.apache.org/jira/browse/YARN-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6088: - Issue Type: Task (was: Bug) > RM UI has to redirect to AHS for completed applications logs > > > Key: YARN-6088 > URL: https://issues.apache.org/jira/browse/YARN-6088 > Project: Hadoop YARN > Issue Type: Task > Components: webapp >Affects Versions: 2.7.3 >Reporter: Sunil G > > Currently AMContainer logs link in RMAppBlock is hardcoded containers' host > node. If that node unavailable, we will not have enough information. -- 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-6088) RM UI has to redirect to AHS for completed applications logs
[ https://issues.apache.org/jira/browse/YARN-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6088: - Issue Type: Task (was: Bug) > RM UI has to redirect to AHS for completed applications logs > > > Key: YARN-6088 > URL: https://issues.apache.org/jira/browse/YARN-6088 > Project: Hadoop YARN > Issue Type: Task > Components: webapp >Affects Versions: 2.7.3 >Reporter: Sunil G > > Currently AMContainer logs link in RMAppBlock is hardcoded containers' host > node. If that node unavailable, we will not have enough information. -- 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-6088) RM UI has to redirect to AHS for completed applications logs
[ https://issues.apache.org/jira/browse/YARN-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6088: - Issue Type: Bug (was: Task) > RM UI has to redirect to AHS for completed applications logs > > > Key: YARN-6088 > URL: https://issues.apache.org/jira/browse/YARN-6088 > Project: Hadoop YARN > Issue Type: Bug > Components: webapp >Affects Versions: 2.7.3 >Reporter: Sunil G > > Currently AMContainer logs link in RMAppBlock is hardcoded containers' host > node. If that node unavailable, we will not have enough information. -- 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] [Comment Edited] (YARN-6894) RM Apps API returns only active apps when query parameter queue used
[
https://issues.apache.org/jira/browse/YARN-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116992#comment-16116992
]
Grant Sohn edited comment on YARN-6894 at 8/7/17 6:27 PM:
--
I think this is too subtle. I would say:
{noformat}
queue - queue name, **Note** specifying the queue parameter will implicitly
filter on only the **unfinished** applications that are currently in this queue
{noformat}
Since it's not standard, it really needs to be called out more clearly. What
do you think?
was (Author: gsohn):
I think this is too subtle. I would say:
{noformat}
queue - queue name, **Note** specifying the queue parameter will implicitly
filter on only the **unfinished** applications that are currently in this queue
{noformat}
Since it's not standard, it really needs to be called out more clearly.
However, I on
> RM Apps API returns only active apps when query parameter queue used
>
>
> Key: YARN-6894
> URL: https://issues.apache.org/jira/browse/YARN-6894
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, restapi
>Reporter: Grant Sohn
>Assignee: Gergely Novák
>Priority: Minor
> Attachments: YARN-6894.001.patch
>
>
> If you run RM's Cluster Applications API with no query parameters, you get a
> list of apps.
> If you run RM's Cluster Applications API with any query parameters other than
> "queue" you get the list of apps with the parameter filters being applied.
> However, when you use the "queue" query parameter, you only see the
> applications that are active in the cluster (NEW, NEW_SAVING, SUBMITTED,
> ACCEPTED, RUNNING). This behavior is inconsistent with the API. If there is
> a sound reason behind this, it should be documented and it seems like there
> might be as the mapred queue CLI behaves similarly.
> http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API
--
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] [Commented] (YARN-6894) RM Apps API returns only active apps when query parameter queue used
[
https://issues.apache.org/jira/browse/YARN-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116992#comment-16116992
]
Grant Sohn commented on YARN-6894:
--
I think this is too subtle. I would say:
{noformat}
queue - queue name, **Note** specifying the queue parameter will implicitly
filter on only the **unfinished** applications that are currently in this queue
{noformat}
Since it's not standard, it really needs to be called out more clearly.
However, I on
> RM Apps API returns only active apps when query parameter queue used
>
>
> Key: YARN-6894
> URL: https://issues.apache.org/jira/browse/YARN-6894
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, restapi
>Reporter: Grant Sohn
>Assignee: Gergely Novák
>Priority: Minor
> Attachments: YARN-6894.001.patch
>
>
> If you run RM's Cluster Applications API with no query parameters, you get a
> list of apps.
> If you run RM's Cluster Applications API with any query parameters other than
> "queue" you get the list of apps with the parameter filters being applied.
> However, when you use the "queue" query parameter, you only see the
> applications that are active in the cluster (NEW, NEW_SAVING, SUBMITTED,
> ACCEPTED, RUNNING). This behavior is inconsistent with the API. If there is
> a sound reason behind this, it should be documented and it seems like there
> might be as the mapred queue CLI behaves similarly.
> http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API
--
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] [Commented] (YARN-6894) RM Apps API returns only active apps when query parameter queue used
[ https://issues.apache.org/jira/browse/YARN-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113302#comment-16113302 ] Grant Sohn commented on YARN-6894: -- I agree. After reading YARN-807, we should clearly document this behavior as different to the rest of the how the API works. > RM Apps API returns only active apps when query parameter queue used > > > Key: YARN-6894 > URL: https://issues.apache.org/jira/browse/YARN-6894 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, restapi >Reporter: Grant Sohn >Priority: Minor > > If you run RM's Cluster Applications API with no query parameters, you get a > list of apps. > If you run RM's Cluster Applications API with any query parameters other than > "queue" you get the list of apps with the parameter filters being applied. > However, when you use the "queue" query parameter, you only see the > applications that are active in the cluster (NEW, NEW_SAVING, SUBMITTED, > ACCEPTED, RUNNING). This behavior is inconsistent with the API. If there is > a sound reason behind this, it should be documented and it seems like there > might be as the mapred queue CLI behaves similarly. > http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API -- 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] [Commented] (YARN-6894) RM Apps API returns only active apps when query parameter queue used
[ https://issues.apache.org/jira/browse/YARN-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111342#comment-16111342 ] Grant Sohn commented on YARN-6894: -- I feel like 2 is the right solution because you can also pass `states` as a parameter and include NEW, NEW_SAVING, SUBMITTED, ACCEPTED, and RUNNING. 1 is the easiest to do. Don't see any value with doing 3. > RM Apps API returns only active apps when query parameter queue used > > > Key: YARN-6894 > URL: https://issues.apache.org/jira/browse/YARN-6894 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, restapi >Reporter: Grant Sohn >Priority: Minor > > If you run RM's Cluster Applications API with no query parameters, you get a > list of apps. > If you run RM's Cluster Applications API with any query parameters other than > "queue" you get the list of apps with the parameter filters being applied. > However, when you use the "queue" query parameter, you only see the > applications that are active in the cluster (NEW, NEW_SAVING, SUBMITTED, > ACCEPTED, RUNNING). This behavior is inconsistent with the API. If there is > a sound reason behind this, it should be documented and it seems like there > might be as the mapred queue CLI behaves similarly. > http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API -- 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] [Created] (YARN-6894) RM Apps API returns only active apps when query parameter queue used
Grant Sohn created YARN-6894: Summary: RM Apps API returns only active apps when query parameter queue used Key: YARN-6894 URL: https://issues.apache.org/jira/browse/YARN-6894 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager, restapi Reporter: Grant Sohn Priority: Minor If you run RM's Cluster Applications API with no query parameters, you get a list of apps. If you run RM's Cluster Applications API with any query parameters other than "queue" you get the list of apps with the parameter filters being applied. However, when you use the "queue" query parameter, you only see the applications that are active in the cluster (NEW, NEW_SAVING, SUBMITTED, ACCEPTED, RUNNING). This behavior is inconsistent with the API. If there is a sound reason behind this, it should be documented and it seems like there might be as the mapred queue CLI behaves similarly. http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API -- 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] [Commented] (YARN-6718) NodeManager logging has "Received" mispelled as "Recieved"
[ https://issues.apache.org/jira/browse/YARN-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054801#comment-16054801 ] Grant Sohn commented on YARN-6718: -- These spelling mistakes were fixed by HDFS-11574. > NodeManager logging has "Received" mispelled as "Recieved" > -- > > Key: YARN-6718 > URL: https://issues.apache.org/jira/browse/YARN-6718 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-6718.1.patch, YARN-6718.2.patch > > > Saw "Recieved SHUTDOWN signal from Resourcemanager" in the NM logs. -- 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] [Commented] (YARN-6718) NodeManager logging has "Received" mispelled as "Recieved"
[ https://issues.apache.org/jira/browse/YARN-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16053250#comment-16053250 ] Grant Sohn commented on YARN-6718: -- Looks like trunk already has the fix. I could probably just fix Resourcemanager to make consistent with the rest of the logging. > NodeManager logging has "Received" mispelled as "Recieved" > -- > > Key: YARN-6718 > URL: https://issues.apache.org/jira/browse/YARN-6718 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-6718.1.patch, YARN-6718.2.patch > > > Saw "Recieved SHUTDOWN signal from Resourcemanager" in the NM logs. -- 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-6718) NodeManager logging has "Received" mispelled as "Recieved"
[ https://issues.apache.org/jira/browse/YARN-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6718: - Attachment: YARN-6718.2.patch Also fixing "Resourcemanager" -> "ResourceManager" > NodeManager logging has "Received" mispelled as "Recieved" > -- > > Key: YARN-6718 > URL: https://issues.apache.org/jira/browse/YARN-6718 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-6718.1.patch, YARN-6718.2.patch > > > Saw "Recieved SHUTDOWN signal from Resourcemanager" in the NM logs. -- 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-6718) NodeManager logging has "Received" mispelled as "Recieved"
[ https://issues.apache.org/jira/browse/YARN-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6718: - Attachment: YARN-6718.1.patch Spelling fixes. > NodeManager logging has "Received" mispelled as "Recieved" > -- > > Key: YARN-6718 > URL: https://issues.apache.org/jira/browse/YARN-6718 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-6718.1.patch > > > Saw "Recieved SHUTDOWN signal from Resourcemanager" in the NM logs. -- 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-6718) NodeManager logging has "Received" mispelled as "Recieved"
[ https://issues.apache.org/jira/browse/YARN-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6718: - Summary: NodeManager logging has "Received" mispelled as "Recieved" (was: NodeManager logging has received mispelled) > NodeManager logging has "Received" mispelled as "Recieved" > -- > > Key: YARN-6718 > URL: https://issues.apache.org/jira/browse/YARN-6718 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > > Saw "Recieved SHUTDOWN signal from Resourcemanager" in the NM logs. -- 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] [Created] (YARN-6718) NodeManager logging has received mispelled
Grant Sohn created YARN-6718: Summary: NodeManager logging has received mispelled Key: YARN-6718 URL: https://issues.apache.org/jira/browse/YARN-6718 Project: Hadoop YARN Issue Type: Bug Components: nodemanager Reporter: Grant Sohn Assignee: Grant Sohn Priority: Trivial Saw "Recieved SHUTDOWN signal from Resourcemanager" in the NM logs. -- 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] [Created] (YARN-6700) Local directory health checks should not only find problems at the local dir level but also at the usercache and filecache level
Grant Sohn created YARN-6700: Summary: Local directory health checks should not only find problems at the local dir level but also at the usercache and filecache level Key: YARN-6700 URL: https://issues.apache.org/jira/browse/YARN-6700 Project: Hadoop YARN Issue Type: Improvement Components: nodemanager Reporter: Grant Sohn Priority: Minor Chmod 400 the usercache directory. The node manager doesn't notice that the usercache is no longer usable. Since the usercache and filecache are part of the local dir, we should extend the checks on these too. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6540) Resource Manager is spelled "Resource Manger" in ResourceManagerRestart.md and ResourceManagerHA.md
[ https://issues.apache.org/jira/browse/YARN-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16018711#comment-16018711 ] Grant Sohn commented on YARN-6540: -- [~yufeigu], thanks for committing this. > Resource Manager is spelled "Resource Manger" in ResourceManagerRestart.md > and ResourceManagerHA.md > --- > > Key: YARN-6540 > URL: https://issues.apache.org/jira/browse/YARN-6540 > Project: Hadoop YARN > Issue Type: Bug > Components: site >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Fix For: 3.0.0-alpha3 > > Attachments: YARN-6540.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6554) ResourceManagerRest.md should document and "{{", "}}" meanings
Grant Sohn created YARN-6554:
Summary: ResourceManagerRest.md should document and "{{",
"}}" meanings
Key: YARN-6554
URL: https://issues.apache.org/jira/browse/YARN-6554
Project: Hadoop YARN
Issue Type: Bug
Components: site
Reporter: Grant Sohn
Priority: Trivial
The docs should mention the meaning of , "{{" and "}}". These are
explained fully in the code.
{noformat}
063 /**
064 * This constant is used to construct class path and it will be
replaced with
065 * real class path separator(':' for Linux and ';' for Windows) by
066 * NodeManager on container launch. User has to use this constant to
construct
067 * class path if user wants cross-platform practice i.e. submit an
application
068 * from a Windows client to a Linux/Unix server or vice versa.
069 */
070 @Public
071 @Unstable
072 public static final String CLASS_PATH_SEPARATOR= "";
073
074 /**
075 * The following two constants are used to expand parameter and it
will be
076 * replaced with real parameter expansion marker ('%' for Windows and
'$' for
077 * Linux) by NodeManager on container launch. For example: {{VAR}}
will be
078 * replaced as $VAR on Linux, and %VAR% on Windows. User has to use
this
079 * constant to construct class path if user wants cross-platform
practice i.e.
080 * submit an application from a Windows client to a Linux/Unix server
or vice
081 * versa.
082 */
083 @Public
084 @Unstable
085 public static final String PARAMETER_EXPANSION_LEFT="{{";
086
087 /**
088 * User has to use this constant to construct class path if user wants
089 * cross-platform practice i.e. submit an application from a Windows
client to
090 * a Linux/Unix server or vice versa.
091 */
092 @Public
093 @Unstable
094 public static final String PARAMETER_EXPANSION_RIGHT="}}";
095
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6540) Resource Manager is spelled "Resource Manger" in ResourceManagerRestart.md and ResourceManagerHA.md
[ https://issues.apache.org/jira/browse/YARN-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6540: - Attachment: YARN-6540.1.patch patch > Resource Manager is spelled "Resource Manger" in ResourceManagerRestart.md > and ResourceManagerHA.md > --- > > Key: YARN-6540 > URL: https://issues.apache.org/jira/browse/YARN-6540 > Project: Hadoop YARN > Issue Type: Bug > Components: site >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-6540.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6540) Resource Manager is spelled "Resource Manger" in ResourceManagerRestart.md and ResourceManagerHA.md
Grant Sohn created YARN-6540: Summary: Resource Manager is spelled "Resource Manger" in ResourceManagerRestart.md and ResourceManagerHA.md Key: YARN-6540 URL: https://issues.apache.org/jira/browse/YARN-6540 Project: Hadoop YARN Issue Type: Bug Components: site Reporter: Grant Sohn Assignee: Grant Sohn Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6162) Cluster Writeable APIs in RM Rest APIs page refers to APIs as alpha but they are already in use with Spark
[
https://issues.apache.org/jira/browse/YARN-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860177#comment-15860177
]
Grant Sohn commented on YARN-6162:
--
I'd say the APIs are stable enough that they shouldn't be labelled alpha.
Searching on this API reveals lots of links
from 2015 to now and some libraries/ports so it isn't really screaming bleeding
edge anymore.
> Cluster Writeable APIs in RM Rest APIs page refers to APIs as alpha but they
> are already in use with Spark
> --
>
> Key: YARN-6162
> URL: https://issues.apache.org/jira/browse/YARN-6162
> Project: Hadoop YARN
> Issue Type: Bug
> Components: documentation, site
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
>
> Excerpt with documentation that should be removed.
> {quote}
> Cluster Writeable APIs
> The setions below refer to APIs which allow to create and modify
> applications. -These APIs are currently in alpha and may change in the
> future.-
> Cluster New Application API
> With the New Application API, you can obtain an application-id which can then
> be used as part of the Cluster Submit Applications API to submit
> applications. The response also includes the maximum resource capabilities
> available on the cluster.
> -This feature is currently in the alpha stage and may change in the future.-
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-6162) Cluster Writeable APIs in RM Rest APIs page refers to APIs as alpha but they are already in use with Spark
[
https://issues.apache.org/jira/browse/YARN-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Sohn reassigned YARN-6162:
Assignee: Grant Sohn
> Cluster Writeable APIs in RM Rest APIs page refers to APIs as alpha but they
> are already in use with Spark
> --
>
> Key: YARN-6162
> URL: https://issues.apache.org/jira/browse/YARN-6162
> Project: Hadoop YARN
> Issue Type: Bug
> Components: documentation, site
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
>
> Excerpt with documentation that should be removed.
> {quote}
> Cluster Writeable APIs
> The setions below refer to APIs which allow to create and modify
> applications. -These APIs are currently in alpha and may change in the
> future.-
> Cluster New Application API
> With the New Application API, you can obtain an application-id which can then
> be used as part of the Cluster Submit Applications API to submit
> applications. The response also includes the maximum resource capabilities
> available on the cluster.
> -This feature is currently in the alpha stage and may change in the future.-
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6162) Cluster Writeable APIs in RM Rest APIs page refers to APIs as alpha but they are already in use with Spark
[
https://issues.apache.org/jira/browse/YARN-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15858358#comment-15858358
]
Grant Sohn commented on YARN-6162:
--
Here's a link showing usage in Spark.
https://community.hortonworks.com/articles/28070/starting-spark-jobs-directly-via-yarn-rest-api.html
> Cluster Writeable APIs in RM Rest APIs page refers to APIs as alpha but they
> are already in use with Spark
> --
>
> Key: YARN-6162
> URL: https://issues.apache.org/jira/browse/YARN-6162
> Project: Hadoop YARN
> Issue Type: Bug
> Components: documentation, site
>Reporter: Grant Sohn
>Priority: Trivial
>
> Excerpt with documentation that should be removed.
> {quote}
> Cluster Writeable APIs
> The setions below refer to APIs which allow to create and modify
> applications. -These APIs are currently in alpha and may change in the
> future.-
> Cluster New Application API
> With the New Application API, you can obtain an application-id which can then
> be used as part of the Cluster Submit Applications API to submit
> applications. The response also includes the maximum resource capabilities
> available on the cluster.
> -This feature is currently in the alpha stage and may change in the future.-
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6162) Cluster Writeable APIs in RM Rest APIs page refers to APIs as alpha but they are already in use with Spark
Grant Sohn created YARN-6162:
Summary: Cluster Writeable APIs in RM Rest APIs page refers to
APIs as alpha but they are already in use with Spark
Key: YARN-6162
URL: https://issues.apache.org/jira/browse/YARN-6162
Project: Hadoop YARN
Issue Type: Bug
Components: documentation, site
Reporter: Grant Sohn
Priority: Trivial
Excerpt with documentation that should be removed.
{quote}
Cluster Writeable APIs
The setions below refer to APIs which allow to create and modify applications.
-These APIs are currently in alpha and may change in the future.-
Cluster New Application API
With the New Application API, you can obtain an application-id which can then
be used as part of the Cluster Submit Applications API to submit applications.
The response also includes the maximum resource capabilities available on the
cluster.
-This feature is currently in the alpha stage and may change in the future.-
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6155) Table of contents for ResourceManagerRest.html could use listings for each Cluster Scheduler API
[ https://issues.apache.org/jira/browse/YARN-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6155: - Attachment: YARN-6155.1.patch > Table of contents for ResourceManagerRest.html could use listings for each > Cluster Scheduler API > > > Key: YARN-6155 > URL: https://issues.apache.org/jira/browse/YARN-6155 > Project: Hadoop YARN > Issue Type: Improvement > Components: site >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-6155.1.patch > > > Latest docs have one link for Cluster Scheduler API however, the API actually > has 3 parts for each supported Scheduler (Capacity, Fifo and Fair). > Add sub-headers for these types. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6155) Table of contents for ResourceManagerRest.html could use listings for each Cluster Scheduler API
Grant Sohn created YARN-6155: Summary: Table of contents for ResourceManagerRest.html could use listings for each Cluster Scheduler API Key: YARN-6155 URL: https://issues.apache.org/jira/browse/YARN-6155 Project: Hadoop YARN Issue Type: Improvement Components: site Reporter: Grant Sohn Assignee: Grant Sohn Priority: Trivial Latest docs have one link for Cluster Scheduler API however, the API actually has 3 parts for each supported Scheduler (Capacity, Fifo and Fair). Add sub-headers for these types. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6079) simple spelling errors in yarn test code
[
https://issues.apache.org/jira/browse/YARN-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816321#comment-15816321
]
Grant Sohn commented on YARN-6079:
--
+1 (non-binding).
> simple spelling errors in yarn test code
>
>
> Key: YARN-6079
> URL: https://issues.apache.org/jira/browse/YARN-6079
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Grant Sohn
>Assignee: vijay
>Priority: Trivial
> Attachments: YARN-6079.001.patch
>
>
> charactor -> character
> hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/nodelabels/TestCommonNodeLabelsManager.java:
> Assert.assertTrue("invalid label charactor should not add to repo",
> caught);
> expteced -> expected
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebApp.java:
> Assert.fail("Exception is not expteced.");
> Exepected -> Expected
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestLeafQueue.java:
> "Exepected AbsoluteUsedCapacity > 0.95, got: "
> expteced -> expected
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebApp.java:
> Assert.fail("Exception is not expteced.");
> macthing -> matching
> hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestAMRMClient.java:
> assertEquals("Expected no macthing requests.", matches.size(), 0);
> propogated -> propagated
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNodeHealthService.java:
> Assert.assertTrue("Node script time out message not propogated",
> protential -> potential
> hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/api/BasePBImplRecordsTest.java:
> LOG.info(String.format("Exclude protential property: %s\n",
> gsp.propertyName));
> recevied -> received
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/localizer/TestResourceLocalizationService.java:
> throw new Exception("Unexpected resource recevied.");
> shouldnt -> shouldn't
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebServiceAppsNodelabel.java:
> fail("resourceInfo object shouldnt be available for finished apps");
> Transistion -> Transition
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMHA.java:
> Assert.fail("Transistion to Active should have failed for
> refreshAll()");
> Unhelathy -> Unhealthy
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMNodeTransitions.java:
> Assert.assertEquals("Unhelathy Nodes", initialUnHealthy,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6079) simple spelling errors in yarn test code
[
https://issues.apache.org/jira/browse/YARN-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Sohn updated YARN-6079:
-
Assignee: (was: Grant Sohn)
> simple spelling errors in yarn test code
>
>
> Key: YARN-6079
> URL: https://issues.apache.org/jira/browse/YARN-6079
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Grant Sohn
>Priority: Trivial
>
> charactor -> character
> hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/nodelabels/TestCommonNodeLabelsManager.java:
> Assert.assertTrue("invalid label charactor should not add to repo",
> caught);
> expteced -> expected
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebApp.java:
> Assert.fail("Exception is not expteced.");
> Exepected -> Expected
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestLeafQueue.java:
> "Exepected AbsoluteUsedCapacity > 0.95, got: "
> expteced -> expected
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebApp.java:
> Assert.fail("Exception is not expteced.");
> macthing -> matching
> hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestAMRMClient.java:
> assertEquals("Expected no macthing requests.", matches.size(), 0);
> propogated -> propagated
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNodeHealthService.java:
> Assert.assertTrue("Node script time out message not propogated",
> protential -> potential
> hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/api/BasePBImplRecordsTest.java:
> LOG.info(String.format("Exclude protential property: %s\n",
> gsp.propertyName));
> recevied -> received
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/localizer/TestResourceLocalizationService.java:
> throw new Exception("Unexpected resource recevied.");
> shouldnt -> shouldn't
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebServiceAppsNodelabel.java:
> fail("resourceInfo object shouldnt be available for finished apps");
> Transistion -> Transition
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMHA.java:
> Assert.fail("Transistion to Active should have failed for
> refreshAll()");
> Unhelathy -> Unhealthy
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMNodeTransitions.java:
> Assert.assertEquals("Unhelathy Nodes", initialUnHealthy,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-6079) simple spelling errors in yarn test code
[
https://issues.apache.org/jira/browse/YARN-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Sohn reassigned YARN-6079:
Assignee: Grant Sohn
> simple spelling errors in yarn test code
>
>
> Key: YARN-6079
> URL: https://issues.apache.org/jira/browse/YARN-6079
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
>
> charactor -> character
> hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/nodelabels/TestCommonNodeLabelsManager.java:
> Assert.assertTrue("invalid label charactor should not add to repo",
> caught);
> expteced -> expected
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebApp.java:
> Assert.fail("Exception is not expteced.");
> Exepected -> Expected
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestLeafQueue.java:
> "Exepected AbsoluteUsedCapacity > 0.95, got: "
> expteced -> expected
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebApp.java:
> Assert.fail("Exception is not expteced.");
> macthing -> matching
> hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestAMRMClient.java:
> assertEquals("Expected no macthing requests.", matches.size(), 0);
> propogated -> propagated
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNodeHealthService.java:
> Assert.assertTrue("Node script time out message not propogated",
> protential -> potential
> hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/api/BasePBImplRecordsTest.java:
> LOG.info(String.format("Exclude protential property: %s\n",
> gsp.propertyName));
> recevied -> received
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/localizer/TestResourceLocalizationService.java:
> throw new Exception("Unexpected resource recevied.");
> shouldnt -> shouldn't
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebServiceAppsNodelabel.java:
> fail("resourceInfo object shouldnt be available for finished apps");
> Transistion -> Transition
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMHA.java:
> Assert.fail("Transistion to Active should have failed for
> refreshAll()");
> Unhelathy -> Unhealthy
> hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMNodeTransitions.java:
> Assert.assertEquals("Unhelathy Nodes", initialUnHealthy,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6079) simple spelling errors in yarn test code
Grant Sohn created YARN-6079:
Summary: simple spelling errors in yarn test code
Key: YARN-6079
URL: https://issues.apache.org/jira/browse/YARN-6079
Project: Hadoop YARN
Issue Type: Bug
Components: test
Reporter: Grant Sohn
Assignee: Grant Sohn
Priority: Trivial
charactor -> character
hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/nodelabels/TestCommonNodeLabelsManager.java:
Assert.assertTrue("invalid label charactor should not add to repo", caught);
expteced -> expected
hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebApp.java:
Assert.fail("Exception is not expteced.");
Exepected -> Expected
hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestLeafQueue.java:
"Exepected AbsoluteUsedCapacity > 0.95, got: "
expteced -> expected
hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebApp.java:
Assert.fail("Exception is not expteced.");
macthing -> matching
hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestAMRMClient.java:
assertEquals("Expected no macthing requests.", matches.size(), 0);
propogated -> propagated
hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNodeHealthService.java:
Assert.assertTrue("Node script time out message not propogated",
protential -> potential
hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/api/BasePBImplRecordsTest.java:
LOG.info(String.format("Exclude protential property: %s\n",
gsp.propertyName));
recevied -> received
hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/localizer/TestResourceLocalizationService.java:
throw new Exception("Unexpected resource recevied.");
shouldnt -> shouldn't
hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebServiceAppsNodelabel.java:
fail("resourceInfo object shouldnt be available for finished apps");
Transistion -> Transition
hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMHA.java:
Assert.fail("Transistion to Active should have failed for refreshAll()");
Unhelathy -> Unhealthy
hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMNodeTransitions.java:
Assert.assertEquals("Unhelathy Nodes", initialUnHealthy,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-5234) ResourceManager REST API missing descriptions for what's returned when using Fair Scheduler
[ https://issues.apache.org/jira/browse/YARN-5234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn resolved YARN-5234. -- Resolution: Fixed Fix Version/s: 3.0.0-alpha1 Looked at latest docs and this has been addressed. > ResourceManager REST API missing descriptions for what's returned when using > Fair Scheduler > --- > > Key: YARN-5234 > URL: https://issues.apache.org/jira/browse/YARN-5234 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation, fairscheduler, resourcemanager >Reporter: Grant Sohn >Priority: Minor > Fix For: 3.0.0-alpha1 > > > Cluster Scheduler API indicates support for Capacity and Fifo. What's > missing is what would be returned if using Fair scheduling. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6026) A couple of spelling errors in the docs
[ https://issues.apache.org/jira/browse/YARN-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6026: - Attachment: YARN-6026-branch-YARN-5355-branch-2.1.patch patch for branch YARN-5355-branch-2. > A couple of spelling errors in the docs > --- > > Key: YARN-6026 > URL: https://issues.apache.org/jira/browse/YARN-6026 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Labels: newbie > Attachments: YARN-6026-branch-YARN-5355-branch-2.1.patch, > YARN-6026.1.patch > > > maximum and retrieved > ResourceManagerRest.md:| memory | int | The maxiumim memory available for a > container | > TimelineServiceV2.md:Else address needs to be retreived from the AM allocate > response and need to be set in timeline client explicitly. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6026) A couple spelling errors in the docs
[ https://issues.apache.org/jira/browse/YARN-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-6026: - Attachment: YARN-6025.1.patch Fixes for spelling mistakes. > A couple spelling errors in the docs > > > Key: YARN-6026 > URL: https://issues.apache.org/jira/browse/YARN-6026 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-6025.1.patch > > > maximum and retrieved > ResourceManagerRest.md:| memory | int | The maxiumim memory available for a > container | > TimelineServiceV2.md:Else address needs to be retreived from the AM allocate > response and need to be set in timeline client explicitly. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6026) A couple spelling errors in the docs
Grant Sohn created YARN-6026: Summary: A couple spelling errors in the docs Key: YARN-6026 URL: https://issues.apache.org/jira/browse/YARN-6026 Project: Hadoop YARN Issue Type: Bug Components: documentation Reporter: Grant Sohn Assignee: Grant Sohn Priority: Trivial maximum and retrieved ResourceManagerRest.md:| memory | int | The maxiumim memory available for a container | TimelineServiceV2.md:Else address needs to be retreived from the AM allocate response and need to be set in timeline client explicitly. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5962) Spelling errors in logging and exceptions for resource manager code
[ https://issues.apache.org/jira/browse/YARN-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-5962: - Attachment: YARN-5962.3.patch Fixed style changes. > Spelling errors in logging and exceptions for resource manager code > --- > > Key: YARN-5962 > URL: https://issues.apache.org/jira/browse/YARN-5962 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 3.0.0-alpha1 >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-5962.1.patch, YARN-5962.2.patch, YARN-5962.3.patch > > > Found spelling errors in exceptions and logging. > Examples: > Invailid -> Invalid > refinition -> definition > non-exsisting -> non-existing -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5962) Spelling errors in logging and exceptions for resource manager code
[ https://issues.apache.org/jira/browse/YARN-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-5962: - Attachment: YARN-5962.2.patch Fixed tests that relied on the misspellings. > Spelling errors in logging and exceptions for resource manager code > --- > > Key: YARN-5962 > URL: https://issues.apache.org/jira/browse/YARN-5962 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 3.0.0-alpha1 >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-5962.1.patch, YARN-5962.2.patch > > > Found spelling errors in exceptions and logging. > Examples: > Invailid -> Invalid > refinition -> definition > non-exsisting -> non-existing -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5963) Spelling errors in logging and exceptions for node manager, client, web-proxy, common, and app history code
[ https://issues.apache.org/jira/browse/YARN-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15720839#comment-15720839 ] Grant Sohn commented on YARN-5963: -- The changes only fix spelling errors in strings. No new functionality was added. > Spelling errors in logging and exceptions for node manager, client, > web-proxy, common, and app history code > --- > > Key: YARN-5963 > URL: https://issues.apache.org/jira/browse/YARN-5963 > Project: Hadoop YARN > Issue Type: Bug > Components: client, nodemanager >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-5963.1.patch > > > A set of spelling errors in the exceptions and logging messages. > Examples: > accessable -> accessible > occured -> occurred > autorized -> authorized -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5963) Spelling errors in logging and exceptions for node manager, client, web-proxy, common, and app history code
[ https://issues.apache.org/jira/browse/YARN-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-5963: - Attachment: YARN-5963.1.patch Fixes for spelling errors. > Spelling errors in logging and exceptions for node manager, client, > web-proxy, common, and app history code > --- > > Key: YARN-5963 > URL: https://issues.apache.org/jira/browse/YARN-5963 > Project: Hadoop YARN > Issue Type: Bug > Components: client, nodemanager >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-5963.1.patch > > > A set of spelling errors in the exceptions and logging messages. > Examples: > accessable -> accessible > occured -> occurred > autorized -> authorized -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5963) Spelling errors in logging and exceptions for node manager, client, web-proxy, common, and app history code
Grant Sohn created YARN-5963: Summary: Spelling errors in logging and exceptions for node manager, client, web-proxy, common, and app history code Key: YARN-5963 URL: https://issues.apache.org/jira/browse/YARN-5963 Project: Hadoop YARN Issue Type: Bug Components: client, nodemanager Reporter: Grant Sohn Assignee: Grant Sohn Priority: Trivial A set of spelling errors in the exceptions and logging messages. Examples: accessable -> accessible occured -> occurred autorized -> authorized -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5962) Spelling errors in logging and exceptions for resource manager code
[ https://issues.apache.org/jira/browse/YARN-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Sohn updated YARN-5962: - Attachment: YARN-5962.1.patch Fixes for spelling errors. > Spelling errors in logging and exceptions for resource manager code > --- > > Key: YARN-5962 > URL: https://issues.apache.org/jira/browse/YARN-5962 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 3.0.0-alpha1 >Reporter: Grant Sohn >Assignee: Grant Sohn >Priority: Trivial > Attachments: YARN-5962.1.patch > > > Found spelling errors in exceptions and logging. > Examples: > Invailid -> Invalid > refinition -> definition > non-exsisting -> non-existing -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5962) Spelling errors in logging and exceptions for resource manager code
Grant Sohn created YARN-5962: Summary: Spelling errors in logging and exceptions for resource manager code Key: YARN-5962 URL: https://issues.apache.org/jira/browse/YARN-5962 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 3.0.0-alpha1 Reporter: Grant Sohn Assignee: Grant Sohn Priority: Trivial Found spelling errors in exceptions and logging. Examples: Invailid -> Invalid refinition -> definition non-exsisting -> non-existing -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5891) yarn rmadmin -help contains a misspelled ResourceManager
[
https://issues.apache.org/jira/browse/YARN-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Sohn updated YARN-5891:
-
Attachment: YARN-5891.1.patch
Fix attached.
> yarn rmadmin -help contains a misspelled ResourceManager
>
>
> Key: YARN-5891
> URL: https://issues.apache.org/jira/browse/YARN-5891
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
>Affects Versions: 2.6.0
>Reporter: Grant Sohn
>Priority: Trivial
> Attachments: YARN-5891.1.patch
>
>
> In the refreshServiceAcl section.
> {noformat}
> rmadmin is the command to execute YARN administrative commands.
> The full syntax is:
> yarn rmadmin [-refreshQueues] [-refreshNodes [-g [timeout in seconds]
> -client|server]] [-refreshSuperUserGroupsConfiguration]
> [-refreshUserToGroupsMappings] [-refreshAdminAcls] [-refreshServiceAcl]
> [-getGroup [username]] [-help [cmd]]
>-refreshQueues: Reload the queues' acls, states and scheduler specific
> properties.
> ResourceManager will reload the mapred-queues configuration
> file.
>-refreshNodes [-g [timeout in seconds] -client|server]: Refresh the hosts
> information at the ResourceManager. Here [-g [timeout in seconds]
> -client|server] is optional, if we specify the timeout then ResourceManager
> will wait for timeout before marking the NodeManager as decommissioned. The
> -client|server indicates if the timeout tracking should be handled by the
> client or the ResourceManager. The client-side tracking is blocking, while
> the server-side tracking is not. Omitting the timeout, or a timeout of -1,
> indicates an infinite timeout.
>-refreshSuperUserGroupsConfiguration: Refresh superuser proxy groups
> mappings
>-refreshUserToGroupsMappings: Refresh user-to-groups mappings
>-refreshAdminAcls: Refresh acls for administration of ResourceManager
>-refreshServiceAcl: Reload the service-level authorization policy file.
> ResoureceManager will reload the authorization policy file.
>-getGroups [username]: Get the groups which given user belongs to.
>-help [cmd]: Displays help for the given command or all commands if none
> is specified.
>-addToClusterNodeLabels [label1,label2,label3] (label splitted by ","):
> add to cluster node labels
>-removeFromClusterNodeLabels [label1,label2,label3] (label splitted by
> ","): remove from cluster node labels
>-replaceLabelsOnNode [node1:port,label1,label2 node2:port,label1,label2]:
> replace labels on nodes
>-directlyAccessNodeLabelStore: Directly access node label store, with this
> option, all node label related operations will not connect RM. Instead, they
> will access/modify stored node labels directly. By default, it is false
> (access via RM). AND PLEASE NOTE: if you configured
> yarn.node-labels.fs-store.root-dir to a local directory (instead of NFS or
> HDFS), this option will only work when the command run on the machine where
> RM is running.
> Generic options supported are
> -conf specify an application configuration file
> -D
[jira] [Created] (YARN-5891) yarn rmadmin -help contains a misspelled ResourceManager
Grant Sohn created YARN-5891:
Summary: yarn rmadmin -help contains a misspelled ResourceManager
Key: YARN-5891
URL: https://issues.apache.org/jira/browse/YARN-5891
Project: Hadoop YARN
Issue Type: Bug
Components: resourcemanager
Affects Versions: 2.6.0
Reporter: Grant Sohn
Priority: Trivial
In the refreshServiceAcl section.
{noformat}
rmadmin is the command to execute YARN administrative commands.
The full syntax is:
yarn rmadmin [-refreshQueues] [-refreshNodes [-g [timeout in seconds]
-client|server]] [-refreshSuperUserGroupsConfiguration]
[-refreshUserToGroupsMappings] [-refreshAdminAcls] [-refreshServiceAcl]
[-getGroup [username]] [-help [cmd]]
-refreshQueues: Reload the queues' acls, states and scheduler specific
properties.
ResourceManager will reload the mapred-queues configuration
file.
-refreshNodes [-g [timeout in seconds] -client|server]: Refresh the hosts
information at the ResourceManager. Here [-g [timeout in seconds]
-client|server] is optional, if we specify the timeout then ResourceManager
will wait for timeout before marking the NodeManager as decommissioned. The
-client|server indicates if the timeout tracking should be handled by the
client or the ResourceManager. The client-side tracking is blocking, while the
server-side tracking is not. Omitting the timeout, or a timeout of -1,
indicates an infinite timeout.
-refreshSuperUserGroupsConfiguration: Refresh superuser proxy groups mappings
-refreshUserToGroupsMappings: Refresh user-to-groups mappings
-refreshAdminAcls: Refresh acls for administration of ResourceManager
-refreshServiceAcl: Reload the service-level authorization policy file.
ResoureceManager will reload the authorization policy file.
-getGroups [username]: Get the groups which given user belongs to.
-help [cmd]: Displays help for the given command or all commands if none is
specified.
-addToClusterNodeLabels [label1,label2,label3] (label splitted by ","): add
to cluster node labels
-removeFromClusterNodeLabels [label1,label2,label3] (label splitted by ","):
remove from cluster node labels
-replaceLabelsOnNode [node1:port,label1,label2 node2:port,label1,label2]:
replace labels on nodes
-directlyAccessNodeLabelStore: Directly access node label store, with this
option, all node label related operations will not connect RM. Instead, they
will access/modify stored node labels directly. By default, it is false (access
via RM). AND PLEASE NOTE: if you configured yarn.node-labels.fs-store.root-dir
to a local directory (instead of NFS or HDFS), this option will only work when
the command run on the machine where RM is running.
Generic options supported are
-conf specify an application configuration file
-D
[jira] [Commented] (YARN-5820) yarn node CLI help should be clearer
[
https://issues.apache.org/jira/browse/YARN-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646654#comment-15646654
]
Grant Sohn commented on YARN-5820:
--
[~naganarasimha...@apache.org], by showing the hadoop command usage, I was only
trying to point out that usage lines are never split in the middle of some
option as was done with , even when the options and parameters gets
quite long like hadoop fs -setfacl. I'm fine with the YARN style of usage, I
was just trying to make the content clearer. Apologies for the confusion, I'll
try to be less ambiguous.
> yarn node CLI help should be clearer
>
>
> Key: YARN-5820
> URL: https://issues.apache.org/jira/browse/YARN-5820
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
>Affects Versions: 2.6.0
>Reporter: Grant Sohn
>Assignee: Ajith S
>Priority: Trivial
> Attachments: YARN-5820.01.patch, YARN-5820.02.patch,
> YARN-5820.03.patch, YARN-5820.04.patch
>
>
> Current message is:
> {noformat}
> usage: node
> -all Works with -list to list all nodes.
> -list List all running nodes. Supports optional use of
> -states to filter nodes based on node state, all -all
> to list all nodes.
> -statesWorks with -list to filter nodes based on input
> comma-separated list of node states.
> -statusPrints the status report of the node.
> {noformat}
> It should be either this:
> {noformat}
> usage: yarn node [-list [-states |-all] | -status ]
> -all Works with -list to list all nodes.
> -list List all running nodes. Supports optional use of
> -states to filter nodes based on node state, all -all
> to list all nodes.
> -statesWorks with -list to filter nodes based on input
> comma-separated list of node states.
> -statusPrints the status report of the node.
> {noformat}
> or that.
> {noformat}
> usage: yarn node -list [-states |-all]
>yarn node -status
> -all Works with -list to list all nodes.
> -list List all running nodes. Supports optional use of
> -states to filter nodes based on node state, all -all
> to list all nodes.
> -statesWorks with -list to filter nodes based on input
> comma-separated list of node states.
> -statusPrints the status report of the node.
> {noformat}
> The latter is the least ambiguous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5850) Document fair scheduler properties waitTimeBeforeKill and preemptionInterval
Grant Sohn created YARN-5850:
Summary: Document fair scheduler properties waitTimeBeforeKill and
preemptionInterval
Key: YARN-5850
URL: https://issues.apache.org/jira/browse/YARN-5850
Project: Hadoop YARN
Issue Type: Task
Components: documentation
Affects Versions: 2.6.0
Reporter: Grant Sohn
Priority: Minor
In FairSchedulerConfiguration.java there are 2 parameters which are not
described in hadoop-yarn/hadoop-yarn-site/FairScheduler.html
{noformat}
protected static final String PREEMPTION_INTERVAL = CONF_PREFIX +
"preemptionInterval";
protected static final int DEFAULT_PREEMPTION_INTERVAL = 5000;
protected static final String WAIT_TIME_BEFORE_KILL = CONF_PREFIX +
"waitTimeBeforeKill";
protected static final int DEFAULT_WAIT_TIME_BEFORE_KILL = 15000;
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5820) yarn node CLI help should be clearer
[
https://issues.apache.org/jira/browse/YARN-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645042#comment-15645042
]
Grant Sohn commented on YARN-5820:
--
The latest patch looks incorrect. The is on it's own line and
stylistically should look like option 2.
When you look at all the Hadoop ecosystem command helps, you never split a line
in this manner.
As an example, here is "hadoop fs":
{noformat}
Usage: hadoop fs [generic options]
[-appendToFile ... ]
[-cat [-ignoreCrc] ...]
[-checksum ...]
[-chgrp [-R] GROUP PATH...]
[-chmod [-R] PATH...]
[-chown [-R] [OWNER][:[GROUP]] PATH...]
[-copyFromLocal [-f] [-p] ... ]
[-copyToLocal [-p] [-ignoreCrc] [-crc] ... ]
[-count [-q] ...]
[-cp [-f] [-p] ... ]
[-createSnapshot []]
[-deleteSnapshot ]
[-df [-h] [ ...]]
[-du [-s] [-h] ...]
[-expunge]
[-get [-p] [-ignoreCrc] [-crc] ... ]
[-getfacl [-R] ]
[-getmerge [-nl] ]
[-help [cmd ...]]
[-ls [-d] [-h] [-R] [ ...]]
[-mkdir [-p] ...]
[-moveFromLocal ... ]
[-moveToLocal ]
[-mv ... ]
[-put [-f] [-p] ... ]
[-renameSnapshot ]
[-rm [-f] [-r|-R] [-skipTrash] ...]
[-rmdir [--ignore-fail-on-non-empty] ...]
[-setfacl [-R] [{-b|-k} {-m|-x } ]|[--set
]]
[-setrep [-R] [-w] ...]
[-stat [format] ...]
[-tail [-f] ]
[-test -[defsz] ]
[-text [-ignoreCrc] ...]
[-touchz ...]
[-usage [cmd ...]]
{noformat}
> yarn node CLI help should be clearer
>
>
> Key: YARN-5820
> URL: https://issues.apache.org/jira/browse/YARN-5820
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
>Affects Versions: 2.6.0
>Reporter: Grant Sohn
>Assignee: Ajith S
>Priority: Trivial
> Attachments: YARN-5820.01.patch, YARN-5820.02.patch,
> YARN-5820.03.patch, YARN-5820.04.patch
>
>
> Current message is:
> {noformat}
> usage: node
> -all Works with -list to list all nodes.
> -list List all running nodes. Supports optional use of
> -states to filter nodes based on node state, all -all
> to list all nodes.
> -statesWorks with -list to filter nodes based on input
> comma-separated list of node states.
> -statusPrints the status report of the node.
> {noformat}
> It should be either this:
> {noformat}
> usage: yarn node [-list [-states |-all] | -status ]
> -all Works with -list to list all nodes.
> -list List all running nodes. Supports optional use of
> -states to filter nodes based on node state, all -all
> to list all nodes.
> -statesWorks with -list to filter nodes based on input
> comma-separated list of node states.
> -statusPrints the status report of the node.
> {noformat}
> or that.
> {noformat}
> usage: yarn node -list [-states |-all]
>yarn node -status
> -all Works with -list to list all nodes.
> -list List all running nodes. Supports optional use of
> -states to filter nodes based on node state, all -all
> to list all nodes.
> -statesWorks with -list to filter nodes based on input
> comma-separated list of node states.
> -statusPrints the status report of the node.
> {noformat}
> The latter is the least ambiguous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5820) yarn node CLI help should be clearer
[
https://issues.apache.org/jira/browse/YARN-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15633743#comment-15633743
]
Grant Sohn commented on YARN-5820:
--
There is extra whitespace, otherwise it's ok.
{noformat}
node [-list [-states | -showDetails | -all] | -status ]
{noformat}
should be:
{noformat}
node [-list [-states |-showDetails|-all] |-status ]
{noformat}
> yarn node CLI help should be clearer
>
>
> Key: YARN-5820
> URL: https://issues.apache.org/jira/browse/YARN-5820
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
>Affects Versions: 2.6.0
>Reporter: Grant Sohn
>Assignee: Ajith S
>Priority: Trivial
> Attachments: YARN-5820.01.patch
>
>
> Current message is:
> {noformat}
> usage: node
> -all Works with -list to list all nodes.
> -list List all running nodes. Supports optional use of
> -states to filter nodes based on node state, all -all
> to list all nodes.
> -statesWorks with -list to filter nodes based on input
> comma-separated list of node states.
> -statusPrints the status report of the node.
> {noformat}
> It should be either this:
> {noformat}
> usage: yarn node [-list [-states |-all] | -status ]
> -all Works with -list to list all nodes.
> -list List all running nodes. Supports optional use of
> -states to filter nodes based on node state, all -all
> to list all nodes.
> -statesWorks with -list to filter nodes based on input
> comma-separated list of node states.
> -statusPrints the status report of the node.
> {noformat}
> or that.
> {noformat}
> usage: yarn node -list [-states |-all]
>yarn node -status
> -all Works with -list to list all nodes.
> -list List all running nodes. Supports optional use of
> -states to filter nodes based on node state, all -all
> to list all nodes.
> -statesWorks with -list to filter nodes based on input
> comma-separated list of node states.
> -statusPrints the status report of the node.
> {noformat}
> The latter is the least ambiguous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5820) yarn node CLI help should be clearer
Grant Sohn created YARN-5820:
Summary: yarn node CLI help should be clearer
Key: YARN-5820
URL: https://issues.apache.org/jira/browse/YARN-5820
Project: Hadoop YARN
Issue Type: Bug
Components: client
Affects Versions: 2.6.0
Reporter: Grant Sohn
Priority: Trivial
Current message is:
{noformat}
usage: node
-all Works with -list to list all nodes.
-list List all running nodes. Supports optional use of
-states to filter nodes based on node state, all -all
to list all nodes.
-statesWorks with -list to filter nodes based on input
comma-separated list of node states.
-statusPrints the status report of the node.
{noformat}
It should be either this:
{noformat}
usage: yarn node [-list [-states |-all] | -status ]
-all Works with -list to list all nodes.
-list List all running nodes. Supports optional use of
-states to filter nodes based on node state, all -all
to list all nodes.
-statesWorks with -list to filter nodes based on input
comma-separated list of node states.
-statusPrints the status report of the node.
{noformat}
or that.
{noformat}
usage: yarn node -list [-states |-all]
yarn node -status
-all Works with -list to list all nodes.
-list List all running nodes. Supports optional use of
-states to filter nodes based on node state, all -all
to list all nodes.
-statesWorks with -list to filter nodes based on input
comma-separated list of node states.
-statusPrints the status report of the node.
{noformat}
The latter is the least ambiguous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-4834) ProcfsBasedProcessTree doesn't track daemonized processes
[ https://issues.apache.org/jira/browse/YARN-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15613122#comment-15613122 ] Grant Sohn commented on YARN-4834: -- Regarding the 'kill -- ...': Ubuntu kill doesn't support "--" but recommends killall instead. > ProcfsBasedProcessTree doesn't track daemonized processes > - > > Key: YARN-4834 > URL: https://issues.apache.org/jira/browse/YARN-4834 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Affects Versions: 2.7.2, 3.0.0-alpha1 >Reporter: Nathan Roberts >Assignee: Nathan Roberts > Fix For: 2.8.0, 2.7.3, 3.0.0-alpha1 > > Attachments: YARN-4834.001.patch > > > Currently the algorithm uses ppid from /proc//stat which can be 1 if a > child process has daemonized itself. This causes potentially large processes > from not being monitored. > session id might be a better choice since that's what we use to signal the > container during teardown. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5757) RM Cluster Node API documentation is not up to date
[ https://issues.apache.org/jira/browse/YARN-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15593082#comment-15593082 ] Grant Sohn commented on YARN-5757: -- Can you add the version and components fields to the JIRA? Thanks. > RM Cluster Node API documentation is not up to date > --- > > Key: YARN-5757 > URL: https://issues.apache.org/jira/browse/YARN-5757 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Miklos Szegedi >Assignee: Miklos Szegedi >Priority: Trivial > Attachments: YARN-5757.000.patch > > > For an example please refer to this field that does not exist since YARN-686: > healthStatus string The health status of the node - Healthy or Unhealthy -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5267) RM REST API doc for app lists "Application Type" instead of "applicationType"
[
https://issues.apache.org/jira/browse/YARN-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Sohn updated YARN-5267:
-
Attachment: YARN-5267.001.patch
Fixes wrong name and 2 minor spelling bugs.
> RM REST API doc for app lists "Application Type" instead of "applicationType"
> --
>
> Key: YARN-5267
> URL: https://issues.apache.org/jira/browse/YARN-5267
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api, documentation
>Affects Versions: 2.6.4
>Reporter: Grant Sohn
>Priority: Trivial
> Labels: documentation
> Attachments: YARN-5267.001.patch
>
>
> From the docs:
> {noformat}
> Note that depending on security settings a user might not be able to see all
> the fields.
> Item Data Type Description
> idstring The application id
> user string The user who started the application
> name string The application name
> Application Type string The application type
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5267) RM REST API doc for app lists "Application Type" instead of "applicationType"
Grant Sohn created YARN-5267:
Summary: RM REST API doc for app lists "Application Type" instead
of "applicationType"
Key: YARN-5267
URL: https://issues.apache.org/jira/browse/YARN-5267
Project: Hadoop YARN
Issue Type: Bug
Components: api, documentation
Affects Versions: 2.6.4
Reporter: Grant Sohn
Priority: Trivial
>From the docs:
{noformat}
Note that depending on security settings a user might not be able to see all
the fields.
ItemData Type Description
id string The application id
userstring The user who started the application
namestring The application name
Application Typestring The application type
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5234) ResourceManager REST API missing descriptions for what's returned when using Fair Scheduler
Grant Sohn created YARN-5234: Summary: ResourceManager REST API missing descriptions for what's returned when using Fair Scheduler Key: YARN-5234 URL: https://issues.apache.org/jira/browse/YARN-5234 Project: Hadoop YARN Issue Type: Bug Components: documentation Reporter: Grant Sohn Priority: Minor Cluster Scheduler API indicates support for Capacity and Fifo. What's missing is what would be returned if using Fair scheduling. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5230) allowPreemptionFrom flag not mentioned in Hadoop: Fair Scheduler documents
Grant Sohn created YARN-5230: Summary: allowPreemptionFrom flag not mentioned in Hadoop: Fair Scheduler documents Key: YARN-5230 URL: https://issues.apache.org/jira/browse/YARN-5230 Project: Hadoop YARN Issue Type: Bug Components: documentation Affects Versions: 2.9.0 Reporter: Grant Sohn Priority: Minor Feature added in https://issues.apache.org/jira/browse/YARN-4462 is not documented in the Hadoop: Fair Scheduler. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
