[jira] [Commented] (YARN-2730) Only one localizer can run on a NodeManager at a time

[ https://issues.apache.org/jira/browse/YARN-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191893#comment-14191893 ] Jason Lowe commented on YARN-2730: -- Thanks for the patch, Siqi. We could go two ways with

[jira] [Commented] (YARN-2707) Potential null dereference in FSDownload

[ https://issues.apache.org/jira/browse/YARN-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14192663#comment-14192663 ] Jason Lowe commented on YARN-2707: -- +1 lgtm. Committing this. Potential null

[jira] [Commented] (YARN-2730) Only one localizer can run on a NodeManager at a time

[ https://issues.apache.org/jira/browse/YARN-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194593#comment-14194593 ] Jason Lowe commented on YARN-2730: -- Thanks for updating the patch, Siqi. In the latest

[jira] [Updated] (YARN-2730) DefaultContainerExecutor runs only one localizer at a time

[ https://issues.apache.org/jira/browse/YARN-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2730: - Summary: DefaultContainerExecutor runs only one localizer at a time (was: Only one localizer can run on a

[jira] [Assigned] (YARN-2079) Recover NonAggregatingLogHandler state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-2079: Assignee: Jason Lowe Recover NonAggregatingLogHandler state upon nodemanager restart

[jira] [Updated] (YARN-2079) Recover NonAggregatingLogHandler state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2079: - Attachment: YARN-2079.patch Patch that saves the state of scheduled LogDeleterRunnable objects to the

[jira] [Updated] (YARN-2805) RM2 in HA setup tries to login using the RM1's kerberos principal

[ https://issues.apache.org/jira/browse/YARN-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2805: - Target Version/s: 2.6.0 RM2 in HA setup tries to login using the RM1's kerberos principal

[jira] [Commented] (YARN-2816) NM fail to start with NPE during container recovery

[ https://issues.apache.org/jira/browse/YARN-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14200241#comment-14200241 ] Jason Lowe commented on YARN-2816: -- This seems like a dubious use case. If something

[jira] [Commented] (YARN-2632) Document NM Restart feature

[ https://issues.apache.org/jira/browse/YARN-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202069#comment-14202069 ] Jason Lowe commented on YARN-2632: -- Thanks for taking this up, Junping, and for reviews,

[jira] [Commented] (YARN-2816) NM fail to start with NPE during container recovery

[ https://issues.apache.org/jira/browse/YARN-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202177#comment-14202177 ] Jason Lowe commented on YARN-2816: -- bq. It won't cause containers leaks. Because

[jira] [Commented] (YARN-2825) Container leak on NM

[ https://issues.apache.org/jira/browse/YARN-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202287#comment-14202287 ] Jason Lowe commented on YARN-2825: -- Thanks for the patch, Jian! Is there a reason we need

[jira] [Commented] (YARN-2825) Container leak on NM

[ https://issues.apache.org/jira/browse/YARN-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202521#comment-14202521 ] Jason Lowe commented on YARN-2825: -- Curious, what's the reasoning to avoid checking for

[jira] [Updated] (YARN-2830) Add backwords compatible ContainerId.newInstance constructor for use within Tez Local Mode

[ https://issues.apache.org/jira/browse/YARN-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2830: - Priority: Blocker (was: Major) Add backwords compatible ContainerId.newInstance constructor for use

[jira] [Commented] (YARN-2632) Document NM Restart feature

[ https://issues.apache.org/jira/browse/YARN-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202681#comment-14202681 ] Jason Lowe commented on YARN-2632: -- Thanks for the update, Vinod.

[jira] [Commented] (YARN-2825) Container leak on NM

[ https://issues.apache.org/jira/browse/YARN-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202905#comment-14202905 ] Jason Lowe commented on YARN-2825: -- +1 lgtm. Committing this. Container leak on NM

[jira] [Commented] (YARN-2632) Document NM Restart feature

[ https://issues.apache.org/jira/browse/YARN-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202943#comment-14202943 ] Jason Lowe commented on YARN-2632: -- +1 lgtm. Committing this. Document NM Restart

[jira] [Commented] (YARN-2780) Log aggregated resource allocation in rm-appsummary.log

[ https://issues.apache.org/jira/browse/YARN-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206532#comment-14206532 ] Jason Lowe commented on YARN-2780: -- +1 lgtm. Will commit this later today if there are no

[jira] [Commented] (YARN-2846) Incorrect persist exit code for running containers in reacquireContainer() that interrupted by NodeManager restart.

[ https://issues.apache.org/jira/browse/YARN-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206616#comment-14206616 ] Jason Lowe commented on YARN-2846: -- Thanks for the report and patch, Junping! Nit: If

[jira] [Created] (YARN-2847) Linux native container executor segfaults if default banned user detected

Jason Lowe created YARN-2847: Summary: Linux native container executor segfaults if default banned user detected Key: YARN-2847 URL: https://issues.apache.org/jira/browse/YARN-2847 Project: Hadoop YARN

[jira] [Commented] (YARN-2847) Linux native container executor segfaults if default banned user detected

[ https://issues.apache.org/jira/browse/YARN-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206801#comment-14206801 ] Jason Lowe commented on YARN-2847: -- The problem is in this code: {code} char

[jira] [Commented] (YARN-2846) Incorrect persist exit code for running containers in reacquireContainer() that interrupted by NodeManager restart.

[ https://issues.apache.org/jira/browse/YARN-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208087#comment-14208087 ] Jason Lowe commented on YARN-2846: -- Thanks, Junping, patch looks better. I'm +1 pending

[jira] [Updated] (YARN-2780) Log aggregated resource allocation in rm-appsummary.log

[ https://issues.apache.org/jira/browse/YARN-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2780: - Issue Type: Improvement (was: New Feature) Log aggregated resource allocation in rm-appsummary.log

[jira] [Commented] (YARN-2846) Incorrect persist exit code for running containers in reacquireContainer() that interrupted by NodeManager restart.

[ https://issues.apache.org/jira/browse/YARN-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14209948#comment-14209948 ] Jason Lowe commented on YARN-2846: -- Agreed. Committing this. Incorrect persist exit

[jira] [Commented] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

[ https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14209986#comment-14209986 ] Jason Lowe commented on YARN-2604: -- bq. Actually, I wonder if we should add a config to

[jira] [Commented] (YARN-2857) ConcurrentModificationException in ContainerLogAppender

[ https://issues.apache.org/jira/browse/YARN-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212792#comment-14212792 ] Jason Lowe commented on YARN-2857: -- +1 lgtm. Committing this.

[jira] [Commented] (YARN-2816) NM fail to start with NPE during container recovery

[ https://issues.apache.org/jira/browse/YARN-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212838#comment-14212838 ] Jason Lowe commented on YARN-2816: -- +1 lgtm. Committing this. NM fail to start with NPE

[jira] [Commented] (YARN-2414) RM web UI: app page will crash if app is failed before any attempt has been created

[ https://issues.apache.org/jira/browse/YARN-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14215174#comment-14215174 ] Jason Lowe commented on YARN-2414: -- +1 lgtm. Committing this. RM web UI: app page will

[jira] [Commented] (YARN-2765) Add leveldb-based implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221448#comment-14221448 ] Jason Lowe commented on YARN-2765: -- bq. Can't we do one create if missing? This is to

[jira] [Commented] (YARN-2056) Disable preemption at Queue level

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221583#comment-14221583 ] Jason Lowe commented on YARN-2056: -- I'm +1 on the latest patch as well. I'll commit this

[jira] [Commented] (YARN-1984) LeveldbTimelineStore does not handle db exceptions properly

[ https://issues.apache.org/jira/browse/YARN-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223079#comment-14223079 ] Jason Lowe commented on YARN-1984: -- Thanks for picking this up, Varun. getStartTimeLong

[jira] [Comment Edited] (YARN-2898) Contaniner-executor prints out wrong error information when failed

[ https://issues.apache.org/jira/browse/YARN-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223288#comment-14223288 ] Jason Lowe edited comment on YARN-2898 at 11/24/14 6:52 PM:

[jira] [Resolved] (YARN-2898) Contaniner-executor prints out wrong error information when failed

[ https://issues.apache.org/jira/browse/YARN-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-2898. -- Resolution: Duplicate This is a duplicate of YAN-2847. Contaniner-executor prints out wrong error

[jira] [Commented] (YARN-1984) LeveldbTimelineStore does not handle db exceptions properly

[ https://issues.apache.org/jira/browse/YARN-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223511#comment-14223511 ] Jason Lowe commented on YARN-1984: -- +1 latest patch lgtm. [~zjshen] do you have further

[jira] [Created] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

Jason Lowe created YARN-2902: Summary: Killing a container that is localizing can orphan resources in the DOWNLOADING state Key: YARN-2902 URL: https://issues.apache.org/jira/browse/YARN-2902 Project:

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224766#comment-14224766 ] Jason Lowe commented on YARN-2902: -- This resource leak can be seen in the NM log when the

[jira] [Created] (YARN-2905) AggregatedLogsBlock page can infinitely loop if the aggregated log file is corrupted

Jason Lowe created YARN-2905: Summary: AggregatedLogsBlock page can infinitely loop if the aggregated log file is corrupted Key: YARN-2905 URL: https://issues.apache.org/jira/browse/YARN-2905 Project:

[jira] [Commented] (YARN-2905) AggregatedLogsBlock page can infinitely loop if the aggregated log file is corrupted

[ https://issues.apache.org/jira/browse/YARN-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14225259#comment-14225259 ] Jason Lowe commented on YARN-2905: -- The code assumes skip will return an EOF indicator if

[jira] [Created] (YARN-2906) CapacitySchedulerPage shows HTML tags for a queue's Active Users

Jason Lowe created YARN-2906: Summary: CapacitySchedulerPage shows HTML tags for a queue's Active Users Key: YARN-2906 URL: https://issues.apache.org/jira/browse/YARN-2906 Project: Hadoop YARN

[jira] [Updated] (YARN-2906) CapacitySchedulerPage shows HTML tags for a queue's Active Users

[ https://issues.apache.org/jira/browse/YARN-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2906: - Target Version/s: 2.7.0 Assignee: Jason Lowe CapacitySchedulerPage shows HTML tags for a

[jira] [Commented] (YARN-2906) CapacitySchedulerPage shows HTML tags for a queue's Active Users

[ https://issues.apache.org/jira/browse/YARN-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14225306#comment-14225306 ] Jason Lowe commented on YARN-2906: -- This was broken by YARN-2503, as it changed _r to _

[jira] [Updated] (YARN-2906) CapacitySchedulerPage shows HTML tags for a queue's Active Users

[ https://issues.apache.org/jira/browse/YARN-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2906: - Attachment: YARN-2906v1.patch It looks like YARN-2503 (inadvertently?) moved the _r from active users to

[jira] [Comment Edited] (YARN-2906) CapacitySchedulerPage shows HTML tags for a queue's Active Users

[ https://issues.apache.org/jira/browse/YARN-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14225306#comment-14225306 ] Jason Lowe edited comment on YARN-2906 at 11/25/14 10:22 PM: -

[jira] [Updated] (YARN-2765) Add leveldb-based implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2765: - Attachment: YARN-2765v3.patch Thanks for the review, Jian! bq. Patch needs updated on top of YARN-2404.

[jira] [Commented] (YARN-2905) AggregatedLogsBlock page can infinitely loop if the aggregated log file is corrupted

[ https://issues.apache.org/jira/browse/YARN-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230571#comment-14230571 ] Jason Lowe commented on YARN-2905: -- +1 lgtm. Committing this. AggregatedLogsBlock page

[jira] [Commented] (YARN-2056) Disable preemption at Queue level

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14233205#comment-14233205 ] Jason Lowe commented on YARN-2056: -- Last call for comments, as I'm planning to commit by

[jira] [Commented] (YARN-2056) Disable preemption at Queue level

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14236099#comment-14236099 ] Jason Lowe commented on YARN-2056: -- Committing this. Disable preemption at Queue level

[jira] [Commented] (YARN-2964) RM prematurely cancels tokens for jobs that submit jobs (oozie)

[ https://issues.apache.org/jira/browse/YARN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14248470#comment-14248470 ] Jason Lowe commented on YARN-2964: -- bq. AFAIR, this code never had the concept of a first

[jira] [Commented] (YARN-2964) RM prematurely cancels tokens for jobs that submit jobs (oozie)

[ https://issues.apache.org/jira/browse/YARN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14248669#comment-14248669 ] Jason Lowe commented on YARN-2964: -- bq. One question, who is setting the shouldCancelAtEnd

[jira] [Created] (YARN-2972) DelegationTokenRenewer thread pool never expands

Jason Lowe created YARN-2972: Summary: DelegationTokenRenewer thread pool never expands Key: YARN-2972 URL: https://issues.apache.org/jira/browse/YARN-2972 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-2972) DelegationTokenRenewer thread pool never expands

[ https://issues.apache.org/jira/browse/YARN-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2972: - Affects Version/s: (was: 2.5.0) 2.3.0 DelegationTokenRenewer thread pool never

[jira] [Commented] (YARN-2972) DelegationTokenRenewer thread pool never expands

[ https://issues.apache.org/jira/browse/YARN-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14248839#comment-14248839 ] Jason Lowe commented on YARN-2972: -- This is the same kind of situation as MAPREDUCE-4662,

[jira] [Updated] (YARN-2972) DelegationTokenRenewer thread pool never expands

[ https://issues.apache.org/jira/browse/YARN-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2972: - Attachment: YARN-2972.001.patch Patch to use the configured number of threads as the core pool size.

[jira] [Commented] (YARN-2964) RM prematurely cancels tokens for jobs that submit jobs (oozie)

[ https://issues.apache.org/jira/browse/YARN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250802#comment-14250802 ] Jason Lowe commented on YARN-2964: -- IIUC it worked in the past because typically the Oozie

[jira] [Commented] (YARN-2964) RM prematurely cancels tokens for jobs that submit jobs (oozie)

[ https://issues.apache.org/jira/browse/YARN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14251818#comment-14251818 ] Jason Lowe commented on YARN-2964: -- Thanks for the patch, Jian! Findbug warnings appear

[jira] [Commented] (YARN-2964) RM prematurely cancels tokens for jobs that submit jobs (oozie)

[ https://issues.apache.org/jira/browse/YARN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252218#comment-14252218 ] Jason Lowe commented on YARN-2964: -- bq. If launcher job first gets added to the appTokens

[jira] [Commented] (YARN-2964) RM prematurely cancels tokens for jobs that submit jobs (oozie)

[ https://issues.apache.org/jira/browse/YARN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252259#comment-14252259 ] Jason Lowe commented on YARN-2964: -- Sure, we can fix that as a followup issue since it's

[jira] [Commented] (YARN-2964) RM prematurely cancels tokens for jobs that submit jobs (oozie)

[ https://issues.apache.org/jira/browse/YARN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252510#comment-14252510 ] Jason Lowe commented on YARN-2964: -- +1 lgtm. I don't believe the test failures are

[jira] [Reopened] (YARN-3083) Resource format isn't correct in Fair Scheduler web page

[ https://issues.apache.org/jira/browse/YARN-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reopened YARN-3083: -- This was fixed by YARN-1975. Reopening to resolve this as a duplicate of that. Resource format isn't

[jira] [Resolved] (YARN-3083) Resource format isn't correct in Fair Scheduler web page

[ https://issues.apache.org/jira/browse/YARN-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-3083. -- Resolution: Duplicate Resource format isn't correct in Fair Scheduler web page

[jira] [Resolved] (YARN-3096) RM Configured Min User % still showing as 100% in Scheduler

[ https://issues.apache.org/jira/browse/YARN-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-3096. -- Resolution: Invalid The user interface still shows 100% because the wrong property is being set, so the

[jira] [Commented] (YARN-3088) LinuxContainerExecutor.deleteAsUser can throw NPE if native executor returns an error

[ https://issues.apache.org/jira/browse/YARN-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14291960#comment-14291960 ] Jason Lowe commented on YARN-3088: -- +1 lgtm. Committing this.

[jira] [Commented] (YARN-3085) Application summary should include the application type

[ https://issues.apache.org/jira/browse/YARN-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14292044#comment-14292044 ] Jason Lowe commented on YARN-3085: -- Thanks for the patch, Rohith! For backwards

[jira] [Created] (YARN-3097) Logging of resource recovery on NM restart has redundancies

Jason Lowe created YARN-3097: Summary: Logging of resource recovery on NM restart has redundancies Key: YARN-3097 URL: https://issues.apache.org/jira/browse/YARN-3097 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3090) DeletionService can silently ignore deletion task failures

[ https://issues.apache.org/jira/browse/YARN-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305514#comment-14305514 ] Jason Lowe commented on YARN-3090: -- Thanks for the patch, Varun! I kicked the tires on

[jira] [Commented] (YARN-3089) LinuxContainerExecutor does not handle file arguments to deleteAsUser

[ https://issues.apache.org/jira/browse/YARN-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305562#comment-14305562 ] Jason Lowe commented on YARN-3089: -- Thanks for updating the patch, Eric! I have one last

[jira] [Commented] (YARN-3085) Application summary should include the application type

[ https://issues.apache.org/jira/browse/YARN-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303367#comment-14303367 ] Jason Lowe commented on YARN-3085: -- +1 lgtm. The test failure appears to be unrelated.

[jira] [Commented] (YARN-3137) CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock

[ https://issues.apache.org/jira/browse/YARN-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305758#comment-14305758 ] Jason Lowe commented on YARN-3137: -- This can be aggravated by the

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305740#comment-14305740 ] Jason Lowe commented on YARN-3136: -- Sample stacktrace: {noformat}

[jira] [Created] (YARN-3137) CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock

Jason Lowe created YARN-3137: Summary: CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock Key: YARN-3137 URL: https://issues.apache.org/jira/browse/YARN-3137 Project: Hadoop YARN

[jira] [Created] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

Jason Lowe created YARN-3136: Summary: getTransferredContainers can be a bottleneck during AM registration Key: YARN-3136 URL: https://issues.apache.org/jira/browse/YARN-3136 Project: Hadoop YARN

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305891#comment-14305891 ] Jason Lowe commented on YARN-3136: -- It appears getTransferredContainers is grabbing the

[jira] [Updated] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3136: - Issue Type: Sub-task (was: Bug) Parent: YARN-3091 getTransferredContainers can be a bottleneck

[jira] [Commented] (YARN-3137) CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock

[ https://issues.apache.org/jira/browse/YARN-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305881#comment-14305881 ] Jason Lowe commented on YARN-3137: -- Thanks for the pointer, Wangda! I missed that JIRA

[jira] [Updated] (YARN-3137) CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock

[ https://issues.apache.org/jira/browse/YARN-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3137: - Issue Type: Sub-task (was: Bug) Parent: YARN-3091 CapacityScheduler.checkAccess unnecessarily

[jira] [Commented] (YARN-3104) RM generates new AMRM tokens every heartbeat between rolling and activation

[ https://issues.apache.org/jira/browse/YARN-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305173#comment-14305173 ] Jason Lowe commented on YARN-3104: -- Maybe, although that may be harder to do than it

[jira] [Commented] (YARN-3089) LinuxContainerExecutor does not handle file arguments to deleteAsUser

[ https://issues.apache.org/jira/browse/YARN-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14306163#comment-14306163 ] Jason Lowe commented on YARN-3089: -- +1 latest patch lgtm. The eclipse warnings don't

[jira] [Updated] (YARN-3143) RM Apps REST API can return NPE or entries missing id and other fields

[ https://issues.apache.org/jira/browse/YARN-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3143: - Attachment: YARN-3143.001.patch Patch to skip non-existent apps as we're walking the app reports. RM

[jira] [Commented] (YARN-3137) CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock

[ https://issues.apache.org/jira/browse/YARN-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14306130#comment-14306130 ] Jason Lowe commented on YARN-3137: -- bq. Queue hierarchy may change at any point of time

[jira] [Assigned] (YARN-3143) RM Apps REST API can return NPE or entries missing id and other fields

[ https://issues.apache.org/jira/browse/YARN-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-3143: Assignee: Jason Lowe RM Apps REST API can return NPE or entries missing id and other fields

[jira] [Commented] (YARN-3143) RM Apps REST API can return NPE or entries missing id and other fields

[ https://issues.apache.org/jira/browse/YARN-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14306169#comment-14306169 ] Jason Lowe commented on YARN-3143: -- I think this is caused by this code in the

[jira] [Updated] (YARN-3104) RM generates new AMRM tokens every heartbeat between rolling and activation

[ https://issues.apache.org/jira/browse/YARN-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3104: - Attachment: YARN-3104.003.patch Doh, sorry for the silly mistake, and thanks for catching it. I updated

[jira] [Commented] (YARN-3113) Release audit warning for Sorting icons.psd

[ https://issues.apache.org/jira/browse/YARN-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301425#comment-14301425 ] Jason Lowe commented on YARN-3113: -- Feel free, Steve! I was hoping to get to this later

[jira] [Commented] (YARN-3144) Configuration for making delegation token failures to timeline server not-fatal

[ https://issues.apache.org/jira/browse/YARN-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309886#comment-14309886 ] Jason Lowe commented on YARN-3144: -- Committing this. The test failures appear to be

[jira] [Commented] (YARN-2809) Implement workaround for linux kernel panic when removing cgroup

[ https://issues.apache.org/jira/browse/YARN-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309920#comment-14309920 ] Jason Lowe commented on YARN-2809: -- +1 lgtm. Will commit this early next week if there

[jira] [Commented] (YARN-3154) Should not upload partial logs for MR jobs or other short-running' applications

[ https://issues.apache.org/jira/browse/YARN-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309986#comment-14309986 ] Jason Lowe commented on YARN-3154: -- Note that even LRS apps have issues if they don't do

[jira] [Commented] (YARN-3143) RM Apps REST API can return NPE or entries missing id and other fields

[ https://issues.apache.org/jira/browse/YARN-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309949#comment-14309949 ] Jason Lowe commented on YARN-3143: -- Thanks for the review, Kihwal! Committing this. RM

[jira] [Commented] (YARN-3143) RM Apps REST API can return NPE or entries missing id and other fields

[ https://issues.apache.org/jira/browse/YARN-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310004#comment-14310004 ] Jason Lowe commented on YARN-3143: -- My apologies, I also meant to thank Eric for the

[jira] [Commented] (YARN-3104) RM generates new AMRM tokens every heartbeat between rolling and activation

[ https://issues.apache.org/jira/browse/YARN-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303577#comment-14303577 ] Jason Lowe commented on YARN-3104: -- The test failure is unrelated, and it passes for me

[jira] [Commented] (YARN-3089) LinuxContainerExecutor does not handle file arguments to deleteAsUser

[ https://issues.apache.org/jira/browse/YARN-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303805#comment-14303805 ] Jason Lowe commented on YARN-3089: -- Thanks for the patch, Eric! Just a few nits: We

[jira] [Commented] (YARN-1778) TestFSRMStateStore fails on trunk

[ https://issues.apache.org/jira/browse/YARN-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303776#comment-14303776 ] Jason Lowe commented on YARN-1778: -- We may also want to check if this should be handled in

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14307335#comment-14307335 ] Jason Lowe commented on YARN-3136: -- I have one main concern with the patch.

[jira] [Commented] (YARN-3143) RM Apps REST API can return NPE or entries missing id and other fields

[ https://issues.apache.org/jira/browse/YARN-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14307381#comment-14307381 ] Jason Lowe commented on YARN-3143: -- bq. Could you provide the RM logs, please ? That will

[jira] [Commented] (YARN-2246) Job History Link in RM UI is redirecting to the URL which contains Job Id twice

[ https://issues.apache.org/jira/browse/YARN-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14308101#comment-14308101 ] Jason Lowe commented on YARN-2246: -- I think the bug is in RMAppAttemptImpl. When the AM

[jira] [Commented] (YARN-3089) LinuxContainerExecutor does not handle file arguments to deleteAsUser

[ https://issues.apache.org/jira/browse/YARN-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14308238#comment-14308238 ] Jason Lowe commented on YARN-3089: -- Looking closer at AppLogAggregatorImpl's rolling

[jira] [Commented] (YARN-3089) LinuxContainerExecutor does not handle file arguments to deleteAsUser

[ https://issues.apache.org/jira/browse/YARN-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14308245#comment-14308245 ] Jason Lowe commented on YARN-3089: -- Ah, comment race. Thanks for confirming Xuan. To

[jira] [Commented] (YARN-3089) LinuxContainerExecutor does not handle file arguments to deleteAsUser

[ https://issues.apache.org/jira/browse/YARN-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14308204#comment-14308204 ] Jason Lowe commented on YARN-3089: -- bq. But if the user does not set any

[jira] [Commented] (YARN-3144) Configuration for making delegation token failures to timeline server not-fatal

[ https://issues.apache.org/jira/browse/YARN-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14307598#comment-14307598 ] Jason Lowe commented on YARN-3144: -- Seems reasonable to allow the timeline service, which

[jira] [Commented] (YARN-914) Support graceful decommission of nodemanager

[ https://issues.apache.org/jira/browse/YARN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14307545#comment-14307545 ] Jason Lowe commented on YARN-914: - For transferring knowledge to the standby RM, we could

[jira] [Commented] (YARN-3144) Configuration for making delegation token failures to timeline server not-fatal

[ https://issues.apache.org/jira/browse/YARN-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309344#comment-14309344 ] Jason Lowe commented on YARN-3144: -- Thanks for updating the patch. Comments: * The added

[jira] [Commented] (YARN-3144) Configuration for making delegation token failures to timeline server not-fatal

[ https://issues.apache.org/jira/browse/YARN-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309585#comment-14309585 ] Jason Lowe commented on YARN-3144: -- Thanks, Jon! We're almost there, but on the final

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