[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236422#comment-15236422 ] Robert Kanter commented on YARN-4676: - Sorry for taking so long to review the updated patch. Thanks

[jira] [Commented] (YARN-4639) Remove dead code in TestDelegationTokenRenewer added in YARN-3055

[ https://issues.apache.org/jira/browse/YARN-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220587#comment-15220587 ] Robert Kanter commented on YARN-4639: - +1 > Remove dead code in TestDelegationTokenRenewer added in

[jira] [Updated] (YARN-4436) DistShell ApplicationMaster.ExecBatScripStringtPath is misspelled

[ https://issues.apache.org/jira/browse/YARN-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4436: Fix Version/s: 2.9.0 > DistShell ApplicationMaster.ExecBatScripStringtPath is misspelled >

[jira] [Commented] (YARN-4436) DistShell ApplicationMaster.ExecBatScripStringtPath is misspelled

[ https://issues.apache.org/jira/browse/YARN-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15217118#comment-15217118 ] Robert Kanter commented on YARN-4436: - +1 > DistShell ApplicationMaster.ExecBatScripStringtPath is

[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210625#comment-15210625 ] Robert Kanter commented on YARN-4676: - I'm still looking through the patch, especially the

[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207373#comment-15207373 ] Robert Kanter commented on YARN-4676: - Thanks for uploading a new patch [~danzhi]. I had actually been

[jira] [Commented] (YARN-4812) TestFairScheduler#testContinuousScheduling fails intermittently

[ https://issues.apache.org/jira/browse/YARN-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198530#comment-15198530 ] Robert Kanter commented on YARN-4812: - +1 > TestFairScheduler#testContinuousScheduling fails

[jira] [Commented] (YARN-4717) TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IllegalArgumentException from cleanup

[ https://issues.apache.org/jira/browse/YARN-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195629#comment-15195629 ] Robert Kanter commented on YARN-4717: - +1 LGTM easy fix :) >

[jira] [Commented] (YARN-4805) Don't go through all schedulers in ParameterizedTestBase

[ https://issues.apache.org/jira/browse/YARN-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15194274#comment-15194274 ] Robert Kanter commented on YARN-4805: - +1 > Don't go through all schedulers in ParameterizedTestBase >

[jira] [Commented] (YARN-4150) Failure in TestNMClient because nodereports were not available

[ https://issues.apache.org/jira/browse/YARN-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191429#comment-15191429 ] Robert Kanter commented on YARN-4150: - I'd say that the test failures were unrelated given the patch,

[jira] [Commented] (YARN-4579) Allow DefaultContainerExecutor container log directory permissions to be configurable

[ https://issues.apache.org/jira/browse/YARN-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168087#comment-15168087 ] Robert Kanter commented on YARN-4579: - +1 > Allow DefaultContainerExecutor container log directory

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15167598#comment-15167598 ] Robert Kanter commented on YARN-4701: - Kicked off Jenkins because it doesn't seem to have noticed this

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15165651#comment-15165651 ] Robert Kanter commented on YARN-4701: - LGTM +1 pending Jenkins > When task logs are not available,

[jira] [Commented] (YARN-4729) SchedulerApplicationAttempt#getTotalRequiredResources can throw an NPE

[ https://issues.apache.org/jira/browse/YARN-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15163879#comment-15163879 ] Robert Kanter commented on YARN-4729: - +1 LGTM > SchedulerApplicationAttempt#getTotalRequiredResources

[jira] [Resolved] (YARN-2736) Job.getHistoryUrl returns empty string

[ https://issues.apache.org/jira/browse/YARN-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter resolved YARN-2736. - Resolution: Fixed > Job.getHistoryUrl returns empty string >

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159479#comment-15159479 ] Robert Kanter commented on YARN-4701: - Approach looks good. Though can you add a unit test for this

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159446#comment-15159446 ] Robert Kanter commented on YARN-4697: - I guess I just missed that build and hadn't refreshed. I've

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159437#comment-15159437 ] Robert Kanter commented on YARN-4697: - LGTM. +1 pending Jenkins (which I just kicked off because it

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157914#comment-15157914 ] Robert Kanter commented on YARN-4697: - Looks good overall. A few minor things: - Add a unit test for

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157870#comment-15157870 ] Robert Kanter commented on YARN-4701: - LGTM. Not sure why Jenkins didn't run for this. I've manually

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155015#comment-15155015 ] Robert Kanter commented on YARN-4697: - Besides [~wilfreds]'s comments, I have some feedback on the unit

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153519#comment-15153519 ] Robert Kanter commented on YARN-4701: - A few comments: - When {{getApplicationLogURL()}} returns null,

[jira] [Commented] (YARN-4579) Allow container directory permissions to be configurable

[ https://issues.apache.org/jira/browse/YARN-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096710#comment-15096710 ] Robert Kanter commented on YARN-4579: - Can you update the unit test to also use a non-default value and

[jira] [Commented] (YARN-4579) Allow DefaultContainerExecutor container log directory permissions to be configurable

[ https://issues.apache.org/jira/browse/YARN-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097118#comment-15097118 ] Robert Kanter commented on YARN-4579: - One minor thing: - {{delCheck}} isn't actually used anywhere.

[jira] [Commented] (YARN-4579) Allow DefaultContainerExecutor container log directory permissions to be configurable

[ https://issues.apache.org/jira/browse/YARN-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097232#comment-15097232 ] Robert Kanter commented on YARN-4579: - Makes sense. One final thing: - Can you replace {{for (int i =

[jira] [Commented] (YARN-4579) Allow container directory permissions to be configurable

[ https://issues.apache.org/jira/browse/YARN-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15095500#comment-15095500 ] Robert Kanter commented on YARN-4579: - Given that the property name in the patch is

[jira] [Commented] (YARN-4379) TestWebApp failing in trunk

[ https://issues.apache.org/jira/browse/YARN-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058525#comment-15058525 ] Robert Kanter commented on YARN-4379: - Sorry about this. I'll post an updated patch to HADOOP-12854.

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15038649#comment-15038649 ] Robert Kanter commented on YARN-4408: - Thanks [~djp]! > NodeManager still reports negative running

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036345#comment-15036345 ] Robert Kanter commented on YARN-4408: - I haven't been able to reproduce this issue, and I agree that

[jira] [Updated] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4408: Attachment: YARN-4408.002.patch The 002 patch adds the debug message. > NodeManager still reports

[jira] [Updated] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4408: Attachment: YARN-4408.003.patch Sure. The 003 patch uses warn level. > NodeManager still reports

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036857#comment-15036857 ] Robert Kanter commented on YARN-4408: - Test failure looks unrelated. > NodeManager still reports

[jira] [Created] (YARN-4408) NodeManager still reports negative running containers

Robert Kanter created YARN-4408: --- Summary: NodeManager still reports negative running containers Key: YARN-4408 URL: https://issues.apache.org/jira/browse/YARN-4408 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4408: Attachment: YARN-4408.001.patch The patch adds the missing check. It also adds a unit test for this

[jira] [Commented] (YARN-4367) SLS webapp doesn't load

[ https://issues.apache.org/jira/browse/YARN-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1501#comment-1501 ] Robert Kanter commented on YARN-4367: - +1 LGTM > SLS webapp doesn't load > --- > >

[jira] [Commented] (YARN-4180) AMLauncher does not retry on failures when talking to NM

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903096#comment-14903096 ] Robert Kanter commented on YARN-4180: - +1 after doing those. > AMLauncher does not retry on failures

[jira] [Commented] (YARN-4180) AMLauncher does not retry on failures when talking to NM

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876583#comment-14876583 ] Robert Kanter commented on YARN-4180: - Looks good. Two minor things: - Can you look into the test

[jira] [Commented] (YARN-4145) Make RMHATestBase abstract so its not run when running all tests under that namespace

[ https://issues.apache.org/jira/browse/YARN-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14741310#comment-14741310 ] Robert Kanter commented on YARN-4145: - +1 LGTM > Make RMHATestBase abstract so its not run when

[jira] [Commented] (YARN-4115) Reduce loglevel of ContainerManagementProtocolProxy to Debug

[ https://issues.apache.org/jira/browse/YARN-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14741318#comment-14741318 ] Robert Kanter commented on YARN-4115: - +1 LGTM > Reduce loglevel of ContainerManagementProtocolProxy

[jira] [Commented] (YARN-4086) Allow Aggregated Log readers to handle HAR files

[ https://issues.apache.org/jira/browse/YARN-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14737895#comment-14737895 ] Robert Kanter commented on YARN-4086: - Test failure unrelated. > Allow Aggregated Log readers to

[jira] [Commented] (YARN-4086) Allow Aggregated Log readers to handle HAR files

[ https://issues.apache.org/jira/browse/YARN-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14737510#comment-14737510 ] Robert Kanter commented on YARN-4086: - What about the javadoc comment? > Allow Aggregated Log readers

[jira] [Updated] (YARN-4086) Allow Aggregated Log readers to handle HAR files

[ https://issues.apache.org/jira/browse/YARN-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4086: Attachment: YARN-4086.003.patch The 003 patch clarifies the javadoc comment for the new test and the

[jira] [Updated] (YARN-4086) Allow Aggregated Log readers to handle HAR files

[ https://issues.apache.org/jira/browse/YARN-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4086: Attachment: YARN-4086.002.patch The 002 patch makes that test less brittle. I also fixed the RAT

[jira] [Updated] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3528: Affects Version/s: (was: 3.0.0) 2.8.0 Target Version/s: 2.8.0 (was:

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720571#comment-14720571 ] Robert Kanter commented on YARN-3528: - It looks like this doesn't apply cleanly to

[jira] [Created] (YARN-4086) Allow Aggregated Log readers to handle HAR files

Robert Kanter created YARN-4086: --- Summary: Allow Aggregated Log readers to handle HAR files Key: YARN-4086 URL: https://issues.apache.org/jira/browse/YARN-4086 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715641#comment-14715641 ] Robert Kanter commented on YARN-3528: - +1 LGTM. Any other comments [~varun_saxena]?

[jira] [Updated] (YARN-4086) Allow Aggregated Log readers to handle HAR files

[ https://issues.apache.org/jira/browse/YARN-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4086: Attachment: YARN-4086.001.patch The YARN-4086.001.patch allows the yarn CLI and web UIs to read

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712271#comment-14712271 ] Robert Kanter commented on YARN-3528: - Oops, wrong person. [~brahmareddy] Tests with

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712269#comment-14712269 ] Robert Kanter commented on YARN-3528: - [~brahma], have you had a chance to look at the

[jira] [Commented] (YARN-3924) Submitting an application to standby ResourceManager should respond better than Connection Refused

[ https://issues.apache.org/jira/browse/YARN-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695639#comment-14695639 ] Robert Kanter commented on YARN-3924: - I think the original mention of JobTracker here

[jira] [Commented] (YARN-4031) Add JvmPauseMonitor to ApplicationHistoryServer and WebAppProxyServer

[ https://issues.apache.org/jira/browse/YARN-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694162#comment-14694162 ] Robert Kanter commented on YARN-4031: - +1 LGTM. I'll commit this soon. Add

[jira] [Commented] (YARN-4031) Add JvmPauseMonitor to ApplicationHistoryServer and WebAppProxyServer

[ https://issues.apache.org/jira/browse/YARN-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680416#comment-14680416 ] Robert Kanter commented on YARN-4031: - For the {{WebAppProxyServer}}, I think we should

[jira] [Commented] (YARN-4019) Add JvmPauseMonitor to ResourceManager and NodeManager

[ https://issues.apache.org/jira/browse/YARN-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660436#comment-14660436 ] Robert Kanter commented on YARN-4019: - Thanks for the review [~djp] Add

[jira] [Updated] (YARN-4019) Add JvmPauseMonitor to ResourceManager and NodeManager

[ https://issues.apache.org/jira/browse/YARN-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4019: Attachment: YARN-4019.003.patch Sure. The 003 patch moves the start lines. The test failure was

[jira] [Commented] (YARN-4019) Add JvmPauseMonitor to ResourceManager and NodeManager

[ https://issues.apache.org/jira/browse/YARN-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14654612#comment-14654612 ] Robert Kanter commented on YARN-4019: - Test failure also appears to be unrelated. Add

[jira] [Updated] (YARN-4019) Add JvmPauseMonitor to ResourceManager and NodeManager

[ https://issues.apache.org/jira/browse/YARN-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4019: Attachment: YARN-4019.002.patch The 002 patch fixes the NM checkstyle warning and the trailing

[jira] [Created] (YARN-4019) Add JvmPauseMonitor to ResourceManager and NodeManager

Robert Kanter created YARN-4019: --- Summary: Add JvmPauseMonitor to ResourceManager and NodeManager Key: YARN-4019 URL: https://issues.apache.org/jira/browse/YARN-4019 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-4019) Add JvmPauseMonitor to ResourceManager and NodeManager

[ https://issues.apache.org/jira/browse/YARN-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4019: Attachment: YARN-4019.001.patch Most of the code was already there; it was just not hooked up. The

[jira] [Commented] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

[ https://issues.apache.org/jira/browse/YARN-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646344#comment-14646344 ] Robert Kanter commented on YARN-3950: - Thanks! Add unique SHELL_ID environment

[jira] [Commented] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639555#comment-14639555 ] Robert Kanter commented on YARN-3900: - +1 Protobuf layout of yarn_security_token

[jira] [Updated] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3900: Fix Version/s: 2.8.0 Protobuf layout of yarn_security_token causes errors in other protos that

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14637700#comment-14637700 ] Robert Kanter commented on YARN-3528: - I think we need to do some JIRA refactoring

[jira] [Updated] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

[ https://issues.apache.org/jira/browse/YARN-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3950: Attachment: YARN-3950.002.patch Good point. The 002 patch renames it to YARN_SHELL_ID and fixes

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635531#comment-14635531 ] Robert Kanter commented on YARN-3528: - [~brahmareddy], are you still working on this?

[jira] [Created] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

Robert Kanter created YARN-3950: --- Summary: Add unique SHELL_ID environment variable to DistributedShell Key: YARN-3950 URL: https://issues.apache.org/jira/browse/YARN-3950 Project: Hadoop YARN

[jira] [Updated] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

[ https://issues.apache.org/jira/browse/YARN-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3950: Attachment: YARN-3950.001.patch Add unique SHELL_ID environment variable to DistributedShell

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14600358#comment-14600358 ] Robert Kanter commented on YARN-2942: - After some offline discussion, we've decided to

[jira] [Updated] (YARN-3842) NM restarts could lead to app failures

[ https://issues.apache.org/jira/browse/YARN-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3842: Attachment: YARN-3842.001.patch That makes sense. The patch is also a lot simpler; it just adds a

[jira] [Updated] (YARN-3842) NM restarts could lead to app failures

[ https://issues.apache.org/jira/browse/YARN-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3842: Attachment: YARN-3842.002.patch The new patch make the changes Karthik suggested. I also added a

[jira] [Commented] (YARN-3842) NM restarts could lead to app failures

[ https://issues.apache.org/jira/browse/YARN-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14596765#comment-14596765 ] Robert Kanter commented on YARN-3842: - I had sort of just split {{startContainers}}

[jira] [Commented] (YARN-3835) hadoop-yarn-server-resourcemanager test package bundles core-site.xml, yarn-site.xml

[ https://issues.apache.org/jira/browse/YARN-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14596327#comment-14596327 ] Robert Kanter commented on YARN-3835: - +1 hadoop-yarn-server-resourcemanager test

[jira] [Updated] (YARN-3835) hadoop-yarn-server-resourcemanager test package bundles core-site.xml, yarn-site.xml

[ https://issues.apache.org/jira/browse/YARN-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3835: Target Version/s: 2.8.0 hadoop-yarn-server-resourcemanager test package bundles core-site.xml,

[jira] [Assigned] (YARN-3811) NM restarts could lead to app failures

[ https://issues.apache.org/jira/browse/YARN-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter reassigned YARN-3811: --- Assignee: Robert Kanter (was: Karthik Kambatla) [~kasha] said I can take this over. NM

[jira] [Commented] (YARN-3812) TestRollingLevelDBTimelineStore fails in trunk due to HADOOP-11347

[ https://issues.apache.org/jira/browse/YARN-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14589121#comment-14589121 ] Robert Kanter commented on YARN-3812: - [~bibinchundatt], good find! That fixes the

[jira] [Commented] (YARN-3812) TestRollingLevelDBTimelineStore fails in trunk due to HADOOP-11347

[ https://issues.apache.org/jira/browse/YARN-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14589174#comment-14589174 ] Robert Kanter commented on YARN-3812: - +1 pending Jenkins

[jira] [Created] (YARN-3812) TestRollingLevelDBTimelineStore fails in trunk due to HADOOP-11347

Robert Kanter created YARN-3812: --- Summary: TestRollingLevelDBTimelineStore fails in trunk due to HADOOP-11347 Key: YARN-3812 URL: https://issues.apache.org/jira/browse/YARN-3812 Project: Hadoop YARN

[jira] [Assigned] (YARN-3812) TestRollingLevelDBTimelineStore fails in trunk due to HADOOP-11347

[ https://issues.apache.org/jira/browse/YARN-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter reassigned YARN-3812: --- Assignee: Robert Kanter TestRollingLevelDBTimelineStore fails in trunk due to HADOOP-11347

[jira] [Updated] (YARN-3812) TestRollingLevelDBTimelineStore fails in trunk due to HADOOP-11347

[ https://issues.apache.org/jira/browse/YARN-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3812: Component/s: (was: timelineserver) test TestRollingLevelDBTimelineStore fails

[jira] [Updated] (YARN-3812) TestRollingLevelDBTimelineStore fails in trunk due to HADOOP-11347

[ https://issues.apache.org/jira/browse/YARN-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3812: Assignee: (was: Robert Kanter) TestRollingLevelDBTimelineStore fails in trunk due to

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564091#comment-14564091 ] Robert Kanter commented on YARN-3528: - I don't think we can simply put 0 everywhere.

[jira] [Updated] (YARN-3218) Implement ConcatenatableAggregatedLogFormat Reader and Writer

[ https://issues.apache.org/jira/browse/YARN-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3218: Attachment: YARN-3218.002.patch The 002 patch adds the {{ConcatenatableAggregatedLogFormat}} Reader

[jira] [Commented] (YARN-3713) Remove duplicate function call storeContainerDiagnostics in ContainerDiagnosticsUpdateTransition

[ https://issues.apache.org/jira/browse/YARN-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564031#comment-14564031 ] Robert Kanter commented on YARN-3713: - +1 Remove duplicate function call

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14562083#comment-14562083 ] Robert Kanter commented on YARN-3528: - [~brahmareddy] are you still planning on working

[jira] [Updated] (YARN-3218) Implement ConcatenatableAggregatedLogFormat Reader and Writer

[ https://issues.apache.org/jira/browse/YARN-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3218: Description: We need to create a Reader and Writer for the ConcatenatableAggregatedLogFormat (was:

[jira] [Updated] (YARN-3218) Implement ConcatenatableAggregatedLogFormat Reader and Writer

[ https://issues.apache.org/jira/browse/YARN-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3218: Description: We need to create a Reader and Writer for the {{ConcatenatableAggregatedLogFormat}}

[jira] [Created] (YARN-3729) Modify the yarn CLI to be able to read the ConcatenatableAggregatedLogFormat

Robert Kanter created YARN-3729: --- Summary: Modify the yarn CLI to be able to read the ConcatenatableAggregatedLogFormat Key: YARN-3729 URL: https://issues.apache.org/jira/browse/YARN-3729 Project:

[jira] [Updated] (YARN-3219) Modify the NM to write logs using the ConcatenatableAggregatedLogFormat

[ https://issues.apache.org/jira/browse/YARN-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3219: Description: The NodeManager should use the {{ConcatenatableAggregatedLogFormat}} from YARN-3218

[jira] [Updated] (YARN-3220) Create a Service in the RM to concatenate aggregated logs

[ https://issues.apache.org/jira/browse/YARN-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3220: Description: Create an {{RMAggregatedLogsConcatenationService}} in the RM that will concatenate the

[jira] [Created] (YARN-3728) Add an rmadmin command to compact concatenated aggregated logs

Robert Kanter created YARN-3728: --- Summary: Add an rmadmin command to compact concatenated aggregated logs Key: YARN-3728 URL: https://issues.apache.org/jira/browse/YARN-3728 Project: Hadoop YARN

[jira] [Updated] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-2942: Attachment: ConcatableAggregatedLogsProposal_v8.pdf Uploaded v8 doc based on the latest discussions.

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14555382#comment-14555382 ] Robert Kanter commented on YARN-2942: - [~kasha], [~vinodkv], [~jlowe], and I had a

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14544109#comment-14544109 ] Robert Kanter commented on YARN-2942: - The log delays in aggregation should be fine if

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540288#comment-14540288 ] Robert Kanter commented on YARN-2942: - Thanks [~jlowe] for your feedback. It's good to

[jira] [Updated] (YARN-3473) Fix RM Web UI configuration for some properties

[ https://issues.apache.org/jira/browse/YARN-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3473: Labels: supportability (was: BB2015-05-RFC supportability) Fix RM Web UI configuration for some

[jira] [Updated] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3491: Labels: (was: BB2015-05-TBR) PublicLocalizer#addResource is too slow.

[jira] [Updated] (YARN-3580) [JDK 8] TestClientRMService.testGetLabelsToNodes fails

[ https://issues.apache.org/jira/browse/YARN-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3580: Attachment: YARN-3580.001.patch When setting node labels, port 0 is considered a wildcard port, and

[jira] [Created] (YARN-3580) [JDK 8] TestClientRMService.testGetLabelsToNodes fails

Robert Kanter created YARN-3580: --- Summary: [JDK 8] TestClientRMService.testGetLabelsToNodes fails Key: YARN-3580 URL: https://issues.apache.org/jira/browse/YARN-3580 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-2942: Attachment: CombinedAggregatedLogsProposal_v7.pdf I’ve uploaded a v7 doc which uses the new log

[jira] [Commented] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14529372#comment-14529372 ] Robert Kanter commented on YARN-3491: - LGTM +1. I'll hold off on committing just yet

<    2   3   4   5   6   7   8   9   10   >