[jira] [Commented] (YARN-4628) TopCli to support Application priority

[ https://issues.apache.org/jira/browse/YARN-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140425#comment-15140425 ] Varun Vasudev commented on YARN-4628: - Good point [~sunilg]. Bibin, can you please chan

[jira] [Commented] (YARN-4628) TopCli to support Application priority

[ https://issues.apache.org/jira/browse/YARN-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140285#comment-15140285 ] Varun Vasudev commented on YARN-4628: - Thanks for the patch [~bibinchundatt]. Couple of

[jira] [Commented] (YARN-4232) TopCLI console support for HA mode

[ https://issues.apache.org/jira/browse/YARN-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136707#comment-15136707 ] Varun Vasudev commented on YARN-4232: - [~bibinchundatt] - what version of hadoop are yo

[jira] [Commented] (YARN-4628) TopCli to support Application priority

[ https://issues.apache.org/jira/browse/YARN-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136703#comment-15136703 ] Varun Vasudev commented on YARN-4628: - Thanks for the patch [~bibinchundatt]. Some mino

[jira] [Comment Edited] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134366#comment-15134366 ] Varun Vasudev edited comment on YARN-3998 at 2/5/16 3:59 PM: - T

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134366#comment-15134366 ] Varun Vasudev commented on YARN-3998: - Thanks for your comments Vinod. Overall, I mostl

[jira] [Commented] (YARN-4635) Add global blacklist tracking for AM container failure.

[ https://issues.apache.org/jira/browse/YARN-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132004#comment-15132004 ] Varun Vasudev commented on YARN-4635: - [~sunilg] - does that mean this won't get commit

[jira] [Commented] (YARN-4635) Add global blacklist tracking for AM container failure.

[ https://issues.apache.org/jira/browse/YARN-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131938#comment-15131938 ] Varun Vasudev commented on YARN-4635: - I agree with [~jianhe] - 1) KILLED_EXCEEDED_PM

[jira] [Updated] (YARN-4307) Display blacklisted nodes for AM container in the RM web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4307: Summary: Display blacklisted nodes for AM container in the RM web UI (was: Blacklisted nodes for AM

[jira] [Commented] (YARN-4665) Asynch submit can lose application submissions

[ https://issues.apache.org/jira/browse/YARN-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130847#comment-15130847 ] Varun Vasudev commented on YARN-4665: - {quote} IIUC here the concern is, as the app sub

[jira] [Commented] (YARN-4665) Asynch submit can lose application submissions

[ https://issues.apache.org/jira/browse/YARN-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130701#comment-15130701 ] Varun Vasudev commented on YARN-4665: - Jason's understanding on the REST API is correct

[jira] [Commented] (YARN-4307) Blacklisted nodes for AM container is not getting displayed in the Web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130247#comment-15130247 ] Varun Vasudev commented on YARN-4307: - +1 for the latest patch. I'll commit this tomorr

[jira] [Commented] (YARN-4625) Make ApplicationSubmissionContext and ApplicationSubmissionContextInfo more consistent

[ https://issues.apache.org/jira/browse/YARN-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128350#comment-15128350 ] Varun Vasudev commented on YARN-4625: - +1 for the latest patch. I'll commit this tomorr

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127937#comment-15127937 ] Varun Vasudev commented on YARN-3998: - {quote} getLocalPathForWrite is used for allocat

[jira] [Commented] (YARN-4307) Blacklisted nodes for AM container is not getting displayed in the Web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127857#comment-15127857 ] Varun Vasudev commented on YARN-4307: - Thanks for the update Naga. Patch is almost ther

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127734#comment-15127734 ] Varun Vasudev commented on YARN-3998: - A couple of additional thoughts - I would like t

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127732#comment-15127732 ] Varun Vasudev commented on YARN-3998: - My apologies for the slow response [~hex108]. Th

[jira] [Commented] (YARN-4649) Add additional logging to some NM state store operations

[ https://issues.apache.org/jira/browse/YARN-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125256#comment-15125256 ] Varun Vasudev commented on YARN-4649: - The single log line thing was to make grep and l

[jira] [Commented] (YARN-4649) Add additional logging to some NM state store operations

[ https://issues.apache.org/jira/browse/YARN-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123332#comment-15123332 ] Varun Vasudev commented on YARN-4649: - Thanks for the patch [~sidharta-s]. Some feedack

[jira] [Updated] (YARN-4172) Extend DominantResourceCalculator to account for all resources

[ https://issues.apache.org/jira/browse/YARN-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4172: Attachment: YARN-4172-YARN-3926.003.patch Uploaded a new patch which fixes javadoc error. > Extend D

[jira] [Commented] (YARN-4625) Make ApplicationSubmissionContext and ApplicationSubmissionContextInfo more consistent

[ https://issues.apache.org/jira/browse/YARN-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118948#comment-15118948 ] Varun Vasudev commented on YARN-4625: - Thanks for the patch [~xgong]. Some comments 1)

[jira] [Commented] (YARN-4307) Blacklisted nodes for AM container is not getting displayed in the Web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115210#comment-15115210 ] Varun Vasudev commented on YARN-4307: - My apologies for the delay Naga. Patch looks mos

[jira] [Commented] (YARN-4555) TestDefaultContainerExecutor#testContainerLaunchError fails on non-englihsh locale environment

[ https://issues.apache.org/jira/browse/YARN-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114830#comment-15114830 ] Varun Vasudev commented on YARN-4555: - Patch should work with docker as well, no issue

[jira] [Commented] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112422#comment-15112422 ] Varun Vasudev commented on YARN-3542: - The increase in javac warnings is due to the dep

[jira] [Updated] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3542: Attachment: YARN-3542.008.patch Uploaded a new version of the patch which also deprecates the Defaul

[jira] [Commented] (YARN-4578) Directories that are mounted in docker containers need to be more restrictive/container-specific

[ https://issues.apache.org/jira/browse/YARN-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112123#comment-15112123 ] Varun Vasudev commented on YARN-4578: - The test failure is unrelated. Committing this t

[jira] [Commented] (YARN-4578) Directories that are mounted in docker containers need to be more restrictive/container-specific

[ https://issues.apache.org/jira/browse/YARN-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110976#comment-15110976 ] Varun Vasudev commented on YARN-4578: - Latest patch applies cleanly. +1 pending jenkins

[jira] [Commented] (YARN-4578) Directories that are mounted in docker containers need to be more restrictive/container-specific

[ https://issues.apache.org/jira/browse/YARN-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110918#comment-15110918 ] Varun Vasudev commented on YARN-4578: - The patch doesn't apply cleanly on trunk, there'

[jira] [Commented] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098214#comment-15098214 ] Varun Vasudev commented on YARN-3542: - {quote} This effectively means the old code

[jira] [Commented] (YARN-4553) Add cgroups support for docker containers

[ https://issues.apache.org/jira/browse/YARN-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094213#comment-15094213 ] Varun Vasudev commented on YARN-4553: - +1 - I'll commit this tomorrow if no one objects

[jira] [Commented] (YARN-4307) Blacklisted nodes for AM container is not getting displayed in the Web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093414#comment-15093414 ] Varun Vasudev commented on YARN-4307: - Thanks for the patch [~Naganarasimha Garla]. Som

[jira] [Comment Edited] (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&focusedCommentId=15091628#comment-15091628 ] Varun Vasudev edited comment on YARN-4459 at 1/11/16 9:04 AM: --

[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&focusedCommentId=15091628#comment-15091628 ] Varun Vasudev commented on YARN-4459: - [~hex108] - assume that the process with the rec

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15087392#comment-15087392 ] Varun Vasudev commented on YARN-3998: - Thanks for the patch [~hex108]! In your impleme

[jira] [Updated] (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:all-tabpanel ] Varun Vasudev updated YARN-4007: Assignee: Sidharta Seethana (was: Varun Vasudev) > Add support for different network setups when lau

[jira] [Commented] (YARN-4232) TopCLI console shows exceptions for help command

[ https://issues.apache.org/jira/browse/YARN-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074891#comment-15074891 ] Varun Vasudev commented on YARN-4232: - Adding support for HA is probably the right thin

[jira] [Updated] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3542: Attachment: YARN-3542.007.patch Uploaded a new patch that'll apply on trunk. Just a note on the confi

[jira] [Commented] (YARN-4172) Extend DominantResourceCalculator to account for all resources

[ https://issues.apache.org/jira/browse/YARN-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067867#comment-15067867 ] Varun Vasudev commented on YARN-4172: - Looks like we need to rebase the YARN-3926 branc

[jira] [Updated] (YARN-4172) Extend DominantResourceCalculator to account for all resources

[ https://issues.apache.org/jira/browse/YARN-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4172: Attachment: YARN-4172-YARN-3926.002.patch bq. 1) Who will update DRC.resourceNames, I found currently

[jira] [Commented] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067584#comment-15067584 ] Varun Vasudev commented on YARN-1856: - [~kasha] - we haven't provided a flag for using

[jira] [Commented] (YARN-2934) Improve handling of container's stderr

[ https://issues.apache.org/jira/browse/YARN-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061915#comment-15061915 ] Varun Vasudev commented on YARN-2934: - I'm not too fussed either way. Globs are probabl

[jira] [Updated] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3542: Attachment: YARN-3542.006.patch bq. Adding a @Deprecated to TestCgroupsLCEResourcesHandler would remo

[jira] [Commented] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058403#comment-15058403 ] Varun Vasudev commented on YARN-3542: - The javac warning increase is due to the depreca

[jira] [Updated] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3542: Attachment: YARN-3542.005.patch Uploaded a patch to fix a failing test. > Re-factor support for CPU

[jira] [Updated] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3542: Attachment: YARN-3542.004.patch Uploaded a new patch to address [~sidharta-s]'s comments. bq. unused

[jira] [Commented] (YARN-4441) Kill application request from the webservice(ui) is showing success even for the finished applications

[ https://issues.apache.org/jira/browse/YARN-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055747#comment-15055747 ] Varun Vasudev commented on YARN-4441: - That's a performance optimization for the RPC cl

[jira] [Comment Edited] (YARN-4451) Some improvements required in Dump scheduler logs

[ https://issues.apache.org/jira/browse/YARN-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055722#comment-15055722 ] Varun Vasudev edited comment on YARN-4451 at 12/14/15 9:58 AM: --

[jira] [Commented] (YARN-4451) Some improvements required in Dump scheduler logs

[ https://issues.apache.org/jira/browse/YARN-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055722#comment-15055722 ] Varun Vasudev commented on YARN-4451: - bq .Well i guessed that would be the reason but

[jira] [Commented] (YARN-4441) Kill application request from the webservice(ui) is showing success even for the finished applications

[ https://issues.apache.org/jira/browse/YARN-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055686#comment-15055686 ] Varun Vasudev commented on YARN-4441: - Why? The reason the webservice implementation ca

[jira] [Commented] (YARN-4451) Some improvements required in Dump scheduler logs

[ https://issues.apache.org/jira/browse/YARN-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055676#comment-15055676 ] Varun Vasudev commented on YARN-4451: - Agree with points (1) and (2) and (5). Disagree

[jira] [Commented] (YARN-4441) Kill application request from the webservice(ui) is showing success even for the finished applications

[ https://issues.apache.org/jira/browse/YARN-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055636#comment-15055636 ] Varun Vasudev commented on YARN-4441: - [~mohdshahidkhan] - Why shouldn't the logic you'

[jira] [Commented] (YARN-4442) create new application operation from the Rest API should be logged in the audit log

[ https://issues.apache.org/jira/browse/YARN-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051136#comment-15051136 ] Varun Vasudev commented on YARN-4442: - Any reason why it should be logged in the REST A

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051024#comment-15051024 ] Varun Vasudev commented on YARN-3998: - [~hex108] - do you wish to work on this? Do you

[jira] [Reopened] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reopened YARN-3998: - Re-opening - I think this is a useful feature for YARN to support. > Add retry-times to let NM re-laun

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.010.patch bq. Do you think is it better to rename yarn.nodemanager.log-contain

[jira] [Commented] (YARN-2934) Improve handling of container's stderr

[ https://issues.apache.org/jira/browse/YARN-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050495#comment-15050495 ] Varun Vasudev commented on YARN-2934: - [~Naganarasimha] - one minor comment - can we ma

[jira] [Updated] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1856: Attachment: YARN-1856.004.patch {quote} Should add all the configs to yarn-default.xml, saying th

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049050#comment-15049050 ] Varun Vasudev commented on YARN-3998: - I'm thinking of re-opening this issue because we

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.009.patch Thanks for the reviews [~ivanmi] and [~leftnoteasy]. bq. I think it

[jira] [Commented] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046559#comment-15046559 ] Varun Vasudev commented on YARN-1856: - The license warnings aren't from the patch. They

[jira] [Updated] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1856: Attachment: YARN-1856.003.patch bq. The constants should have ‘MEMORY’ in their names. For example,

[jira] [Updated] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1856: Attachment: YARN-1856.002.patch bq. Could you move these constants to CGroupsHandler ? There are alre

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.008.patch Uploaded a new patch to address comments by [~leftnoteasy]. bq. Coul

[jira] [Updated] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3542: Attachment: YARN-3542.003.patch bq.Move the implementation from CgroupsLCEResourcesHandler into t

[jira] [Commented] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044361#comment-15044361 ] Varun Vasudev commented on YARN-3542: - All the existing configurations will continue to

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.007.patch Uploaded a new patch with clarifications on following symlinks in the

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.006.patch Uploaded a new patch to address [~sidharta-s]'s comments. [~leftnote

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037418#comment-15037418 ] Varun Vasudev commented on YARN-4309: - bq. do we need to worry about -L following links

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.005.patch Uploaded a new version of the patch with Windows support. > Add debu

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.004.patch Thanks for the review [~sidharta-s]. bq. Could you clarify why the d

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.003.patch Uploaded a new patch that adds a section on broken symlinks to the di

[jira] [Updated] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1856: Attachment: YARN-1856.001.patch Uploaded a patch that adds support for cgroups based memory monitorin

[jira] [Updated] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3542: Attachment: YARN-3542.002.patch Uploaded a new patch to address test failures and checkstyle issues.

[jira] [Commented] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031351#comment-15031351 ] Varun Vasudev commented on YARN-1856: - Moved it out of 2.6.3 and 2.7.3. > cgroups base

[jira] [Updated] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1856: Target Version/s: 2.7.3 (was: 2.6.3, 2.7.3) > cgroups based memory monitoring for containers > -

[jira] [Updated] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1856: Target Version/s: (was: 2.7.3) > cgroups based memory monitoring for containers > -

[jira] [Updated] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3542: Attachment: YARN-3542.001.patch Attached an initial version of the patch. > Re-factor support for CP

[jira] [Commented] (YARN-4361) Total resource count mistake:NodeRemovedSchedulerEvent in ReconnectNodeTransition will reduce the newNode.getTotalCapability() in Multi-thread model

[ https://issues.apache.org/jira/browse/YARN-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029676#comment-15029676 ] Varun Vasudev commented on YARN-4361: - [~wjlei] - is this a duplicate of YARN-4344? >

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.002.patch bq .Linux or Unix? Sorry, not Linux - this patch is for Unix only. U

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.001.patch Uploaded an initial version of the patch. It's a little difficult to

[jira] [Updated] (YARN-4344) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations

[ https://issues.apache.org/jira/browse/YARN-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4344: Attachment: YARN-4344-branch-2.6.001.patch Uploaded a version for branch-2.6 > NMs reconnecting with

[jira] [Commented] (YARN-4344) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations

[ https://issues.apache.org/jira/browse/YARN-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004024#comment-15004024 ] Varun Vasudev commented on YARN-4344: - The test failures are unrelated to the patch. >

[jira] [Updated] (YARN-4344) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations

[ https://issues.apache.org/jira/browse/YARN-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4344: Attachment: YARN-4344.002.patch Thanks for the feedback everyone. I've uploaded a new patch to use th

[jira] [Updated] (YARN-4344) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations

[ https://issues.apache.org/jira/browse/YARN-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4344: Attachment: YARN-4344.001.patch Uploaded a patch with the fix. [~zxu], [~jlowe] - can you please take

[jira] [Commented] (YARN-4344) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations

[ https://issues.apache.org/jira/browse/YARN-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000229#comment-15000229 ] Varun Vasudev commented on YARN-4344: - An example of a situation is shown below - {code

[jira] [Created] (YARN-4344) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations

Varun Vasudev created YARN-4344: --- Summary: NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations Key: YARN-4344 URL: https://issues.apache.org/jira/browse/YARN-4344

[jira] [Commented] (YARN-4315) NaN in Queue percentage for cluster apps page

[ https://issues.apache.org/jira/browse/YARN-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981023#comment-14981023 ] Varun Vasudev commented on YARN-4315: - [~bibinchundatt] - is this temporary, while all

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980277#comment-14980277 ] Varun Vasudev commented on YARN-4309: - [~ste...@apache.org] - can you give me an exampl

[jira] [Commented] (YARN-4307) Blacklisted nodes for AM container is not getting displayed in the Web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980271#comment-14980271 ] Varun Vasudev commented on YARN-4307: - No - they should be separate. One refers to node

[jira] [Comment Edited] (YARN-4307) Blacklisted nodes for AM container is not getting displayed in the Web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980271#comment-14980271 ] Varun Vasudev edited comment on YARN-4307 at 10/29/15 11:12 AM: -

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978867#comment-14978867 ] Varun Vasudev commented on YARN-4309: - Yeah, tar-ing up the local dir may not be the be

[jira] [Created] (YARN-4309) Add debug information to application logs when a container fails

Varun Vasudev created YARN-4309: --- Summary: Add debug information to application logs when a container fails Key: YARN-4309 URL: https://issues.apache.org/jira/browse/YARN-4309 Project: Hadoop YARN

[jira] [Commented] (YARN-4307) Blacklisted nodes for AM container is not getting displayed in the Web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978771#comment-14978771 ] Varun Vasudev commented on YARN-4307: - So the blacklisted nodes in the UI refers to nod

[jira] [Commented] (YARN-4302) SLS not able start due to NPE in SchedulerApplicationAttempt#getResourceUsageReport

[ https://issues.apache.org/jira/browse/YARN-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976082#comment-14976082 ] Varun Vasudev commented on YARN-4302: - My apologies for not catching this [~bibinchunda

[jira] [Commented] (YARN-4285) Display resource usage as percentage of queue and cluster in the RM UI

[ https://issues.apache.org/jira/browse/YARN-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974643#comment-14974643 ] Varun Vasudev commented on YARN-4285: - The test failures are not related to the patch.

[jira] [Updated] (YARN-4285) Display resource usage as percentage of queue and cluster in the RM UI

[ https://issues.apache.org/jira/browse/YARN-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4285: Attachment: YARN-4285.004.patch The failing tests are due to a deadlock caused by calling getQueueInf

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970734#comment-14970734 ] Varun Vasudev commented on YARN-4009: - Makes sense. +1 for the latest patch. > CORS su

[jira] [Updated] (YARN-4285) Display resource usage as percentage of queue and cluster in the RM UI

[ https://issues.apache.org/jira/browse/YARN-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4285: Attachment: YARN-4285.003.patch bq. 1) Since ApplicationResourceUsageReport is public API, I suggest

[jira] [Updated] (YARN-4285) Display resource usage as percentage of queue and cluster in the RM UI

[ https://issues.apache.org/jira/browse/YARN-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4285: Attachment: YARN-4285.002.patch Thanks for the feedback [~leftnoteasy]. I've updated a new patch with

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968844#comment-14968844 ] Varun Vasudev commented on YARN-4009: - [~jeagles] - with your patch, the timeline servi

<    2   3   4   5   6   7   8   9   10   11   >