[jira] [Commented] (YARN-4006) YARN ATS Alternate Kerberos HTTP Authentication Changes

[ https://issues.apache.org/jira/browse/YARN-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297651#comment-15297651 ] Varun Vasudev commented on YARN-4006: - bq. We've confirmed that the RM REST API suffers from the exact

[jira] [Commented] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297636#comment-15297636 ] Hadoop QA commented on YARN-5132: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5111) YARN container system metrics are not aggregated to application

[ https://issues.apache.org/jira/browse/YARN-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297591#comment-15297591 ] Naganarasimha G R commented on YARN-5111: - Sorry for the delayed response... will have a look at it

[jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297551#comment-15297551 ] Arun Suresh commented on YARN-5087: --- bq. ..what happens when a user asks for both increase and decrease

[jira] [Commented] (YARN-3362) Add node label usage in RM CapacityScheduler web UI

[ https://issues.apache.org/jira/browse/YARN-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297535#comment-15297535 ] Naganarasimha G R commented on YARN-3362: - will close this jira once YARN-4751 is committed and

[jira] [Commented] (YARN-4751) In 2.7, Labeled queue usage not shown properly in capacity scheduler UI

[ https://issues.apache.org/jira/browse/YARN-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297534#comment-15297534 ] Naganarasimha G R commented on YARN-4751: - Hi [~eepayne], Latest patch LGTM and the findbugs and

[jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297514#comment-15297514 ] Sangjin Lee commented on YARN-5018: --- Looks good. I'll commit it when jenkins returns clean. > Online

[jira] [Comment Edited] (YARN-4887) AM-RM protocol changes for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297499#comment-15297499 ] Subru Krishnan edited comment on YARN-4887 at 5/24/16 1:45 AM: --- [~cnauroth],

[jira] [Commented] (YARN-4887) AM-RM protocol changes for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297499#comment-15297499 ] Subru Krishnan commented on YARN-4887: -- [~cnauroth], turns out that inheritance is turned off and so I

[jira] [Commented] (YARN-5071) address HBase compatibility issues with trunk

[ https://issues.apache.org/jira/browse/YARN-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297501#comment-15297501 ] Sangjin Lee commented on YARN-5071: --- I tried rebasing our branch with the current trunk, and I was able

[jira] [Comment Edited] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297492#comment-15297492 ] Subru Krishnan edited comment on YARN-5132 at 5/24/16 1:35 AM: --- Adding an

[jira] [Updated] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-5132: - Attachment: YARN-5132-v1.patch Adding an exclusion for protobuf-generated sources from YARN build

[jira] [Created] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build

Subru Krishnan created YARN-5132: Summary: Exclude generated protobuf sources from YARN Javadoc build Key: YARN-5132 URL: https://issues.apache.org/jira/browse/YARN-5132 Project: Hadoop YARN

[jira] [Updated] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-5018: Attachment: YARN-5018-YARN-2928.005.patch New patch to address [~sjlee0]'s comments. > Online aggregation logic

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297461#comment-15297461 ] Hadoop QA commented on YARN-4212: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297451#comment-15297451 ] Sangjin Lee commented on YARN-5018: --- I think it is fine to have this flag in the generic

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297450#comment-15297450 ] Hadoop QA commented on YARN-5124: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297449#comment-15297449 ] Li Lu commented on YARN-5018: - Thanks [~sjlee0]! That looks fine. I can hide the logic of collector.postPut

[jira] [Commented] (YARN-5097) NPE in Separator.joinEncoded()

[ https://issues.apache.org/jira/browse/YARN-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297447#comment-15297447 ] Hadoop QA commented on YARN-5097: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-4007) Add support for different network setups when launching the docker container

[ https://issues.apache.org/jira/browse/YARN-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297443#comment-15297443 ] Zhongyue Luo commented on YARN-4007: [~sidharta-s] Thanks for the heads up. We'd definitely try it out.

[jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297442#comment-15297442 ] Sangjin Lee commented on YARN-5018: --- The point is taken. Can we do this at least then? We can implement

[jira] [Commented] (YARN-3971) Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on nodelabel recovery

[ https://issues.apache.org/jira/browse/YARN-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297420#comment-15297420 ] Hudson commented on YARN-3971: -- SUCCESS: Integrated in Hadoop-trunk-Commit #9846 (See

[jira] [Updated] (YARN-3971) Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on nodelabel recovery

[ https://issues.apache.org/jira/browse/YARN-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3971: Fix Version/s: 2.8.0 > Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on

[jira] [Comment Edited] (YARN-3971) Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on nodelabel recovery

[ https://issues.apache.org/jira/browse/YARN-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297414#comment-15297414 ] Naganarasimha G R edited comment on YARN-3971 at 5/24/16 12:25 AM: ---

[jira] [Commented] (YARN-3971) Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on nodelabel recovery

[ https://issues.apache.org/jira/browse/YARN-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297414#comment-15297414 ] Naganarasimha G R commented on YARN-3971: - Committed the patch to trunk, Branch-2 & Branch-2.8.

[jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297397#comment-15297397 ] Li Lu commented on YARN-5018: - The current situation is a little bit nasty... In the original version we

[jira] [Commented] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297396#comment-15297396 ] Hadoop QA commented on YARN-4844: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5131) Distributed shell AM fails when extra container arrives during finishing

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297379#comment-15297379 ] Wangda Tan commented on YARN-5131: -- [~vvasudev], could you help to review this patch? Thanks, >

[jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297367#comment-15297367 ] Wangda Tan commented on YARN-5087: -- [~asuresh], bq. If we restrict an update to be only one type of change

[jira] [Updated] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4844: - Attachment: YARN-4844.12.patch Uploaded ver.12 update getVirtualCores as well. > Add

[jira] [Updated] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4212: --- Attachment: YARN-4212.002.patch > FairScheduler: Parent queues is not allowed to be 'Fair' policy if its >

[jira] [Updated] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4212: --- Attachment: YARN-4212.001.patch > FairScheduler: Parent queues is not allowed to be 'Fair' policy if its >

[jira] [Updated] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4212: --- Attachment: (was: YARN-4212.001.patch) > FairScheduler: Parent queues is not allowed to be 'Fair' policy

[jira] [Updated] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4212: --- Summary: FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[jira] [Updated] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4212: --- Summary: FairScheduler: Parent queues is not allowed to be 'Fair' policy its children have the "drf" policy

[jira] [Commented] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297344#comment-15297344 ] Ray Chiang commented on YARN-5047: -- RE: checkstyle Same issue with protected member variable. RE:

[jira] [Updated] (YARN-4212) FairScheduler: Parent queues is not allowed 'Fair' policy its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4212: --- Summary: FairScheduler: Parent queues is not allowed 'Fair' policy its children have the "drf" policy (was:

[jira] [Commented] (YARN-4006) YARN ATS Alternate Kerberos HTTP Authentication Changes

[ https://issues.apache.org/jira/browse/YARN-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297342#comment-15297342 ] Larry McCay commented on YARN-4006: --- Like I said, we need to extract the implementation of the

[jira] [Comment Edited] (YARN-5097) NPE in Separator.joinEncoded()

[ https://issues.apache.org/jira/browse/YARN-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297326#comment-15297326 ] Sangjin Lee edited comment on YARN-5097 at 5/23/16 11:26 PM: - Thanks

[jira] [Commented] (YARN-5097) NPE in Separator.joinEncoded()

[ https://issues.apache.org/jira/browse/YARN-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297326#comment-15297326 ] Sangjin Lee commented on YARN-5097: --- Thanks [~vrushalic]. I understand Joep also was suggesting a logging

[jira] [Commented] (YARN-5131) Distributed shell AM fails when extra container arrives during finishing

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297323#comment-15297323 ] Hadoop QA commented on YARN-5131: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-5097) NPE in Separator.joinEncoded()

[ https://issues.apache.org/jira/browse/YARN-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5097: - Attachment: YARN-5097-YARN-2928.03.patch Attaching v3 as per Joep's suggestions. > NPE in

[jira] [Commented] (YARN-5105) entire time series is returned for YARN container system metrics (CPU and memory)

[ https://issues.apache.org/jira/browse/YARN-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297316#comment-15297316 ] Sangjin Lee commented on YARN-5105: --- {quote} One more thing we need to think about is behavior of fields

[jira] [Commented] (YARN-5089) Improve "yarn log" command-line "logFiles" option to support regex

[ https://issues.apache.org/jira/browse/YARN-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297315#comment-15297315 ] Hadoop QA commented on YARN-5089: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297314#comment-15297314 ] Arun Suresh commented on YARN-5087: --- Thanks for weighing in [~leftnoteasy], If we restrict an update to

[jira] [Commented] (YARN-5094) some YARN container events have timestamp of -1 in REST output

[ https://issues.apache.org/jira/browse/YARN-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297290#comment-15297290 ] Sangjin Lee commented on YARN-5094: --- Yes, I'm also slightly leaning towards populating the timestamp

[jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297291#comment-15297291 ] Wangda Tan commented on YARN-5087: -- Beyond above comment, it's better not to touch existing

[jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297287#comment-15297287 ] Wangda Tan commented on YARN-5087: -- Hi [~asuresh], I think there's a downside of merging all

[jira] [Commented] (YARN-5097) NPE in Separator.joinEncoded()

[ https://issues.apache.org/jira/browse/YARN-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297277#comment-15297277 ] Sangjin Lee commented on YARN-5097: --- Thanks [~vrushalic] for your patch! To clarify, fixing YARN-5018

[jira] [Commented] (YARN-5093) created time shows 0 in most REST output

[ https://issues.apache.org/jira/browse/YARN-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297274#comment-15297274 ] Sangjin Lee commented on YARN-5093: --- Thanks [~varun_saxena]! I suspect most of the unit test changes are

[jira] [Commented] (YARN-5097) NPE in Separator.joinEncoded()

[ https://issues.apache.org/jira/browse/YARN-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297269#comment-15297269 ] Joep Rottinghuis commented on YARN-5097: Overall looks good. Why don't you lift 136 if ((flowName

[jira] [Updated] (YARN-5131) Distributed shell AM fails when extra container arrives during finishing

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5131: - Description: Because of YARN-1902, extra container could be allocated to AM which causes AM failure.

[jira] [Updated] (YARN-5131) Distributed shell AM fails when extra container arrives during finishing

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5131: - Attachment: YARN-5131.1.patch > Distributed shell AM fails when extra container arrives during finishing >

[jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297252#comment-15297252 ] Arun Suresh commented on YARN-5087: --- [~kasha], what I meant was.. Given that the allocate response

[jira] [Updated] (YARN-5131) Distributed shell AM fails when extra container arrives during finishing

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5131: - Description: Because of YARN-1902, extra container could be allocated to AM which causes AM failure.

[jira] [Updated] (YARN-5131) Distributed shell AM fails when extra container arrives during finishing

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5131: - Summary: Distributed shell AM fails when extra container arrives during finishing (was: Distributed shell

[jira] [Commented] (YARN-5131) Distributed shell AM fails because of InterruptedException

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297244#comment-15297244 ] Wangda Tan commented on YARN-5131: -- [~hitesh], yes you're correct, InterruptedException will not cause AM

[jira] [Commented] (YARN-5095) flow activities and flow runs are populated with wrong timestamp when RM restarts w/ recovery enabled

[ https://issues.apache.org/jira/browse/YARN-5095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297234#comment-15297234 ] Sangjin Lee commented on YARN-5095: --- Thanks for the patch [~varun_saxena]! Would it be easier to add an

[jira] [Commented] (YARN-4006) YARN ATS Alternate Kerberos HTTP Authentication Changes

[ https://issues.apache.org/jira/browse/YARN-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297228#comment-15297228 ] Allen Wittenauer commented on YARN-4006: We've confirmed that the RM REST API suffers from the

[jira] [Commented] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297216#comment-15297216 ] Hadoop QA commented on YARN-5047: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5124: -- Attachment: YARN-5124.003.patch [~curino], bq. I think the cleaner semantic should be: 1. I can ask for

[jira] [Commented] (YARN-4979) FSAppAttempt demand calculation considers demands at multiple locality levels different

[ https://issues.apache.org/jira/browse/YARN-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297200#comment-15297200 ] zhihai xu commented on YARN-4979: - thanks [~kasha] for reviewing and committing the patch! > FSAppAttempt

[jira] [Comment Edited] (YARN-5131) Distributed shell AM fails because of InterruptedException

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297174#comment-15297174 ] Hitesh Shah edited comment on YARN-5131 at 5/23/16 10:04 PM: - The error in the

[jira] [Commented] (YARN-4979) FSAppAttempt demand calculation considers demands at multiple locality levels different

[ https://issues.apache.org/jira/browse/YARN-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297178#comment-15297178 ] Hudson commented on YARN-4979: -- SUCCESS: Integrated in Hadoop-trunk-Commit #9844 (See

[jira] [Commented] (YARN-5131) Distributed shell AM fails because of InterruptedException

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297174#comment-15297174 ] Hitesh Shah commented on YARN-5131: --- The error in the description is not really an error. The thread was

[jira] [Updated] (YARN-5131) Distributed shell AM fails because of InterruptedException

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5131: - Priority: Major (was: Critical) > Distributed shell AM fails because of InterruptedException >

[jira] [Updated] (YARN-5131) Distributed shell AM fails because of InterruptedException

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5131: - Target Version/s: 2.9.0 > Distributed shell AM fails because of InterruptedException >

[jira] [Updated] (YARN-5131) Distributed shell AM fails because of InterruptedException

[ https://issues.apache.org/jira/browse/YARN-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5131: - Summary: Distributed shell AM fails because of InterruptedException (was: Distributed shell AM fails Java

[jira] [Created] (YARN-5131) Distributed shell AM fails Java Null Point Exception

Sumana Sathish created YARN-5131: Summary: Distributed shell AM fails Java Null Point Exception Key: YARN-5131 URL: https://issues.apache.org/jira/browse/YARN-5131 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297139#comment-15297139 ] Sangjin Lee commented on YARN-5018: --- [~gtCarrera9], thanks for the patch! I think defining a state after

[jira] [Commented] (YARN-2877) Extend YARN to support distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297133#comment-15297133 ] Arun Suresh commented on YARN-2877: --- Ah.. makes sense.. thanks for the clarification [~djp] > Extend

[jira] [Updated] (YARN-4979) FSAppAttempt demand calculation considers demands at multiple locality levels different

[ https://issues.apache.org/jira/browse/YARN-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4979: --- Summary: FSAppAttempt demand calculation considers demands at multiple locality levels

[jira] [Commented] (YARN-4979) FSAppAttempt adds duplicate ResourceRequest to demand in updateDemand.

[ https://issues.apache.org/jira/browse/YARN-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297118#comment-15297118 ] Karthik Kambatla commented on YARN-4979: +1, checking this in. > FSAppAttempt adds duplicate

[jira] [Updated] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-5047: - Attachment: YARN-5047.003.patch - Implement earlier feedback - Removes optimization to assignMultiple

[jira] [Commented] (YARN-4979) FSAppAttempt adds duplicate ResourceRequest to demand in updateDemand.

[ https://issues.apache.org/jira/browse/YARN-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297107#comment-15297107 ] Karthik Kambatla commented on YARN-4979: More importantly, the demand could be wrong and affect the

[jira] [Created] (YARN-5130) Mark ContainerStatus and NodeReport as evolving

Steve Loughran created YARN-5130: Summary: Mark ContainerStatus and NodeReport as evolving Key: YARN-5130 URL: https://issues.apache.org/jira/browse/YARN-5130 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-5109) timestamps are stored unencoded causing parse errors

[ https://issues.apache.org/jira/browse/YARN-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297099#comment-15297099 ] Sangjin Lee commented on YARN-5109: --- Thanks [~varun_saxena] for the patch! I think it's almost there. I

[jira] [Updated] (YARN-5089) Improve "yarn log" command-line "logFiles" option to support regex

[ https://issues.apache.org/jira/browse/YARN-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-5089: Attachment: YARN-5089.5.patch > Improve "yarn log" command-line "logFiles" option to support regex >

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues with 'Fair' policy should compute shares of all resources for its children during a recompute

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297096#comment-15297096 ] Yufei Gu commented on YARN-4212: The way to calculate the vcore in fair policy might not be a good idea.

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297089#comment-15297089 ] Carlo Curino commented on YARN-5124: Based on our off-line conversation, the current patch would

[jira] [Updated] (YARN-5127) Expose ExecutionType in Container api record

[ https://issues.apache.org/jira/browse/YARN-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5127: -- Assignee: Hitesh Sharma (was: Arun Suresh) > Expose ExecutionType in Container api record >

[jira] [Commented] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297041#comment-15297041 ] Ray Chiang commented on YARN-5047: -- Filed follow up JIRAs YARN-5128 and YARN-5129. > Refactor nodeUpdate

[jira] [Commented] (YARN-5127) Expose ExecutionType in Container api record

[ https://issues.apache.org/jira/browse/YARN-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297043#comment-15297043 ] Arun Suresh commented on YARN-5127: --- [~hrsharma], do you want to take this up ? > Expose ExecutionType

[jira] [Updated] (YARN-5128) Investigate potential race condition in the scheduler nodeUpdate() method

[ https://issues.apache.org/jira/browse/YARN-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-5128: - Summary: Investigate potential race condition in the scheduler nodeUpdate() method (was: Investigate

[jira] [Commented] (YARN-4006) YARN ATS Alternate Kerberos HTTP Authentication Changes

[ https://issues.apache.org/jira/browse/YARN-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297032#comment-15297032 ] Allen Wittenauer commented on YARN-4006: bq. I would say that whether certain deployments decide to

[jira] [Created] (YARN-5129) Update FairScheduler to use SchedulerHealth

Ray Chiang created YARN-5129: Summary: Update FairScheduler to use SchedulerHealth Key: YARN-5129 URL: https://issues.apache.org/jira/browse/YARN-5129 Project: Hadoop YARN Issue Type: Task

[jira] [Commented] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297002#comment-15297002 ] Ray Chiang commented on YARN-5047: -- Thanks for the feedback guys. I agree with doing #1, but it looks

[jira] [Commented] (YARN-4007) Add support for different network setups when launching the docker container

[ https://issues.apache.org/jira/browse/YARN-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296994#comment-15296994 ] Sidharta Seethana commented on YARN-4007: - Hi [~zyluo], I have work in progress patch - I should be

[jira] [Created] (YARN-5128) Investigate potential race condition in the scheuduler nodeUpdate() method

Ray Chiang created YARN-5128: Summary: Investigate potential race condition in the scheuduler nodeUpdate() method Key: YARN-5128 URL: https://issues.apache.org/jira/browse/YARN-5128 Project: Hadoop YARN

[jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296955#comment-15296955 ] Karthik Kambatla commented on YARN-5087: A single {{UpdateContainerRequest}} seems reasonable to

[jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296942#comment-15296942 ] Arun Suresh commented on YARN-5087: --- Ping [~kasha] too... thoughts ? > Expose API to allow AM to request

[jira] [Comment Edited] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15295133#comment-15295133 ] Arun Suresh edited comment on YARN-5087 at 5/23/16 7:35 PM: [~vinodkv],

[jira] [Comment Edited] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15295133#comment-15295133 ] Arun Suresh edited comment on YARN-5087 at 5/23/16 7:34 PM: [~vinodkv],

[jira] [Comment Edited] (YARN-4887) AM-RM protocol changes for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296931#comment-15296931 ] Subru Krishnan edited comment on YARN-4887 at 5/23/16 7:32 PM: --- Thanks

[jira] [Commented] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296933#comment-15296933 ] Hadoop QA commented on YARN-4766: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-4887) AM-RM protocol changes for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296931#comment-15296931 ] Subru Krishnan commented on YARN-4887: -- Thanks [~cnauroth] for your prompt response. I should have

[jira] [Commented] (YARN-4459) container-executor might kill process wrongly

[ https://issues.apache.org/jira/browse/YARN-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296930#comment-15296930 ] Hadoop QA commented on YARN-4459: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-4459) container-executor might kill process wrongly

[ https://issues.apache.org/jira/browse/YARN-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-4459: - Attachment: YARN-4459.03.patch Updated the patch to fix the unit test failure. Now that we're only

[jira] [Commented] (YARN-5105) entire time series is returned for YARN container system metrics (CPU and memory)

[ https://issues.apache.org/jira/browse/YARN-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296884#comment-15296884 ] Hadoop QA commented on YARN-5105: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296858#comment-15296858 ] Hadoop QA commented on YARN-5124: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

  1   2   >