[jira] [Commented] (YARN-3856) YARN shoud allocate container that is closest to the data

[ https://issues.apache.org/jira/browse/YARN-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14607945#comment-14607945 ] jaehoon ko commented on YARN-3856: -- Hi, Ravi. Thanks for your comment. I wasn't aware of

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14607921#comment-14607921 ] Tsuyoshi Ozawa commented on YARN-3798: -- I'm replying today. ZKRMStateStore shouldn't

[jira] [Commented] (YARN-3768) Index out of range exception with environment variables without values

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

[jira] [Commented] (YARN-3841) [Storage implementation] Create HDFS backing storage implementation for ATS writes

[ https://issues.apache.org/jira/browse/YARN-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609454#comment-14609454 ] Tsuyoshi Ozawa commented on YARN-3841: -- [~zjshen] thank you for sharing. I'll start

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609294#comment-14609294 ] Giovanni Matteo Fumarola commented on YARN-3116: Do you have any feedback

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609397#comment-14609397 ] Giovanni Matteo Fumarola commented on YARN-3116: I have already taken care

[jira] [Commented] (YARN-313) Add Admin API for supporting node resource configuration in command line

[ https://issues.apache.org/jira/browse/YARN-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609404#comment-14609404 ] Inigo Goiri commented on YARN-313: -- I'd like to add the option to do: yarn rmadmin

[jira] [Commented] (YARN-313) Add Admin API for supporting node resource configuration in command line

[ https://issues.apache.org/jira/browse/YARN-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609410#comment-14609410 ] Inigo Goiri commented on YARN-313: -- My bad. It already has it; anyway, I volunteer to

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609452#comment-14609452 ] Tsuyoshi Ozawa commented on YARN-3798: -- I'll ping here after releasing 2.7.1.

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

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

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

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

[jira] [Resolved] (YARN-3871) ResourceManager down after Blueprint install

[ https://issues.apache.org/jira/browse/YARN-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zack Marsh resolved YARN-3871. -- Resolution: Invalid ResourceManager down after Blueprint install

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609377#comment-14609377 ] Zhijie Shen commented on YARN-3116: --- In fact jenkins complains much fewer checkstyle

[jira] [Commented] (YARN-3793) Several NPEs when deleting local files on NM recovery

[ https://issues.apache.org/jira/browse/YARN-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609302#comment-14609302 ] Varun Saxena commented on YARN-3793: [~ka...@cloudera.com] / [~jlowe], kindly review

[jira] [Updated] (YARN-3840) Resource Manager web ui issue when sorting application by id (with application having id 9999)

[ https://issues.apache.org/jira/browse/YARN-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Shahid Khan updated YARN-3840: --- Attachment: (was: YARN-3840.patch) Resource Manager web ui issue when sorting

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608030#comment-14608030 ] Tsuyoshi Ozawa commented on YARN-3798: -- [~zxu] I see, the workaround makes sense to

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608273#comment-14608273 ] Mohammad Shahid Khan commented on YARN-3798: Hi Devaraj, I was not the watcher

[jira] [Updated] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-3798: - Attachment: YARN-3798-branch-2.7.003.patch ZKRMStateStore shouldn't create new session without

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608089#comment-14608089 ] Lavkesh Lahngir commented on YARN-3591: --- Thanks [~jlowe] and [~zxu] for detailed

[jira] [Commented] (YARN-3830) AbstractYarnScheduler.createReleaseCache may try to clean a null attempt

[ https://issues.apache.org/jira/browse/YARN-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608093#comment-14608093 ] nijel commented on YARN-3830: - Thanks [~devaraj.k] for the review Test case looks bit tricky :)

[jira] [Created] (YARN-3873) pendingApplications in LeafQueue should also use OrderingPolicy

Sunil G created YARN-3873: - Summary: pendingApplications in LeafQueue should also use OrderingPolicy Key: YARN-3873 URL: https://issues.apache.org/jira/browse/YARN-3873 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-3823) Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property

[ https://issues.apache.org/jira/browse/YARN-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-3823: Hadoop Flags: Reviewed Thanks [~zjshen] for confirmation. +1 for the latest patch. Fix mismatch in

[jira] [Updated] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.003.patch Added a call to update nodeHostCount before getting blacklist

[jira] [Commented] (YARN-3823) Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property

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

[jira] [Commented] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

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

[jira] [Updated] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2003: -- Attachment: (was: 0015-YARN-2003.patch) Support to process Job priority from Submission Context in

[jira] [Updated] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2003: -- Attachment: 0015-YARN-2003.patch Missed one file earlier. Support to process Job priority from Submission

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608446#comment-14608446 ] Tsuyoshi Ozawa commented on YARN-3798: -- The result of test-patch.sh is as follows.

[jira] [Commented] (YARN-3770) SerializedException should also handle java.lang.Error

[ https://issues.apache.org/jira/browse/YARN-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608529#comment-14608529 ] Hudson commented on YARN-3770: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2190 (See

[jira] [Commented] (YARN-3770) SerializedException should also handle java.lang.Error

[ https://issues.apache.org/jira/browse/YARN-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608473#comment-14608473 ] Hudson commented on YARN-3770: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #242 (See

[jira] [Commented] (YARN-3695) ServerProxy (NMProxy, etc.) shouldn't retry forever for non network exception.

[ https://issues.apache.org/jira/browse/YARN-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608469#comment-14608469 ] Hudson commented on YARN-3695: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #242 (See

[jira] [Commented] (YARN-3784) Indicate preemption timout along with the list of containers to AM (preemption message)

[ https://issues.apache.org/jira/browse/YARN-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608543#comment-14608543 ] Sunil G commented on YARN-3784: --- Thankyou [~chris.douglas] for the comments. I will update a

[jira] [Updated] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2003: -- Attachment: 0015-YARN-2003.patch Updating patch to in-cooperate comments in YARN-2004. Support to process Job

[jira] [Updated] (YARN-2004) Priority scheduling support in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2004: -- Attachment: 0009-YARN-2004.patch Thank you very much [~jianhe] and [~leftnoteasy] for the review and comments -

[jira] [Created] (YARN-3870) Providing raw container request information for fine scheduling

Lei Guo created YARN-3870: - Summary: Providing raw container request information for fine scheduling Key: YARN-3870 URL: https://issues.apache.org/jira/browse/YARN-3870 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3695) ServerProxy (NMProxy, etc.) shouldn't retry forever for non network exception.

[ https://issues.apache.org/jira/browse/YARN-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608525#comment-14608525 ] Hudson commented on YARN-3695: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2190 (See

[jira] [Created] (YARN-3869) Add app name to RM audit log

Shay Rojansky created YARN-3869: --- Summary: Add app name to RM audit log Key: YARN-3869 URL: https://issues.apache.org/jira/browse/YARN-3869 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608549#comment-14608549 ] Varun Saxena commented on YARN-3047: [~zjshen], basically will have to add a servlet

[jira] [Commented] (YARN-624) Support gang scheduling in the AM RM protocol

[ https://issues.apache.org/jira/browse/YARN-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608386#comment-14608386 ] Lei Guo commented on YARN-624: -- [~john.lil...@redpoint.net], with your use case, do you also

[jira] [Commented] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

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

[jira] [Commented] (YARN-3827) Migrate YARN native build to new CMake framework

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

[jira] [Commented] (YARN-3823) Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property

[ https://issues.apache.org/jira/browse/YARN-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608811#comment-14608811 ] Zhijie Shen commented on YARN-3823: --- Hm... I think we forgot changing the default in the

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608746#comment-14608746 ] Varun Saxena commented on YARN-3508: [~leftnoteasy], yes this is what the patch does

[jira] [Updated] (YARN-3840) Resource Manager web ui issue when sorting application by id (with application having id 9999)

[ https://issues.apache.org/jira/browse/YARN-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Shahid Khan updated YARN-3840: --- Attachment: YARN-3840-1.patch Submitting the updated patch Resource Manager web ui

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608797#comment-14608797 ] Wangda Tan commented on YARN-3508: -- I think my comment confusing you:

[jira] [Commented] (YARN-3840) Resource Manager web ui issue when sorting application by id (with application having id 9999)

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

[jira] [Updated] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

[ https://issues.apache.org/jira/browse/YARN-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Burlison updated YARN-3844: Attachment: YARN-3844.003.patch Make hadoop-yarn-project Native code -Wall-clean

[jira] [Updated] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

[ https://issues.apache.org/jira/browse/YARN-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Burlison updated YARN-3844: Attachment: (was: YARN-3844.002.PATCH) Make hadoop-yarn-project Native code -Wall-clean

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608729#comment-14608729 ] Wangda Tan commented on YARN-3508: -- Thanks for explanation, [~varun_saxena]. Currently,

[jira] [Commented] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

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

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608774#comment-14608774 ] Zhijie Shen commented on YARN-3051: --- bq. One more thing I have changed is limit of

[jira] [Updated] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

[ https://issues.apache.org/jira/browse/YARN-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Burlison updated YARN-3844: Attachment: YARN-3844.002.PATCH Trailing whitespace fixed in patch Make hadoop-yarn-project Native

[jira] [Updated] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

[ https://issues.apache.org/jira/browse/YARN-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Burlison updated YARN-3844: Attachment: YARN-3844.002.patch Make hadoop-yarn-project Native code -Wall-clean

[jira] [Commented] (YARN-624) Support gang scheduling in the AM RM protocol

[ https://issues.apache.org/jira/browse/YARN-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608653#comment-14608653 ] john lilley commented on YARN-624: -- We don't have any data locality needs for these use

[jira] [Commented] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

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

[jira] [Commented] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

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

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608744#comment-14608744 ] Zhijie Shen commented on YARN-3116: --- [~subru] and [~giovanni.fumarola], in yesterdays

[jira] [Updated] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

[ https://issues.apache.org/jira/browse/YARN-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Burlison updated YARN-3844: Attachment: (was: YARN-3844.003.patch) Make hadoop-yarn-project Native code -Wall-clean

[jira] [Commented] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

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

[jira] [Commented] (YARN-3866) AM-RM protocol changes to support container resizing

[ https://issues.apache.org/jira/browse/YARN-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609056#comment-14609056 ] Wangda Tan commented on YARN-3866: -- And could you add ContainerStatus PB-related changes

[jira] [Commented] (YARN-2004) Priority scheduling support in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608857#comment-14608857 ] Wangda Tan commented on YARN-2004: -- Thanks for update, [~sunilg], comments to latest

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608947#comment-14608947 ] Wangda Tan commented on YARN-3849: -- Thanks for working on this, [~sunilg]! The fix of

[jira] [Updated] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

[ https://issues.apache.org/jira/browse/YARN-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Burlison updated YARN-3844: Attachment: YARN-3844.004.patch Make hadoop-yarn-project Native code -Wall-clean

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608986#comment-14608986 ] Wangda Tan commented on YARN-3508: -- bq. Ok, IIUC you want me to pass RMContext to

[jira] [Commented] (YARN-3823) Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property

[ https://issues.apache.org/jira/browse/YARN-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608864#comment-14608864 ] Ray Chiang commented on YARN-3823: -- That makes sense. I'll update yarn-default.xml to

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608870#comment-14608870 ] Varun Saxena commented on YARN-3508: bq. Instead of passing EventHandlerSchedulerEvent

[jira] [Commented] (YARN-3823) Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property

[ https://issues.apache.org/jira/browse/YARN-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608988#comment-14608988 ] Ray Chiang commented on YARN-3823: -- RE: No new unit test Same as before. The unit test

[jira] [Updated] (YARN-3823) Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property

[ https://issues.apache.org/jira/browse/YARN-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-3823: - Attachment: YARN-3823.002.patch - Adjust yarn.scheduler.maximum-allocation-vcores to 4 in yarn-default.xml

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608911#comment-14608911 ] Varun Saxena commented on YARN-3508: Any reason you want this changed ? Even if we pass

[jira] [Commented] (YARN-3823) Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property

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

[jira] [Commented] (YARN-3866) AM-RM protocol changes to support container resizing

[ https://issues.apache.org/jira/browse/YARN-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609055#comment-14609055 ] Wangda Tan commented on YARN-3866: -- Hi [~mding], Thanks for working on the patch, some

[jira] [Commented] (YARN-3823) Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property

[ https://issues.apache.org/jira/browse/YARN-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14607600#comment-14607600 ] Ray Chiang commented on YARN-3823: -- I see this for YARN-193, using git blame

[jira] [Updated] (YARN-3768) Index out of range exception with environment variables without values

[ https://issues.apache.org/jira/browse/YARN-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3768: Attachment: YARN-3768.004.patch Index out of range exception with environment variables without values

[jira] [Updated] (YARN-3768) Index out of range exception with environment variables without values

[ https://issues.apache.org/jira/browse/YARN-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3768: Attachment: (was: YARN-3768.004.patch) Index out of range exception with environment variables without

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

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

[jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608128#comment-14608128 ] Varun Saxena commented on YARN-3047: bq. 1. We should be able to reuse TimelineAbout.

[jira] [Commented] (YARN-3830) AbstractYarnScheduler.createReleaseCache may try to clean a null attempt

[ https://issues.apache.org/jira/browse/YARN-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608147#comment-14608147 ] Devaraj K commented on YARN-3830: - You can possibly extract the code contained in the run()

[jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609188#comment-14609188 ] Sangjin Lee commented on YARN-3047: --- Sorry, you're right. It should be really about the

[jira] [Commented] (YARN-3768) ArrayIndexOutOfBoundsException with empty environment variables

[ https://issues.apache.org/jira/browse/YARN-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609191#comment-14609191 ] Hudson commented on YARN-3768: -- FAILURE: Integrated in Hadoop-trunk-Commit #8097 (See

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

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

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609248#comment-14609248 ] Rohit Agarwal commented on YARN-3633: - Yes, the {{clusterMaxAMShare}} is acting as an

[jira] [Updated] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3508: --- Attachment: YARN-3508.06.patch Fixed one checkstyle issue Preemption processing occuring on the main

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609280#comment-14609280 ] Giovanni Matteo Fumarola commented on YARN-3116: Thanks [~zjshen] for the

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609080#comment-14609080 ] Varun Saxena commented on YARN-3508: [~leftnoteasy], bq. Init is used by production

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

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

[jira] [Updated] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3508: --- Attachment: YARN-3508.05.patch [~leftnoteasy], updated the patch as per your comments. Kindly review.

[jira] [Updated] (YARN-3871) ResourceManager down after Blueprint install

[ https://issues.apache.org/jira/browse/YARN-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zack Marsh updated YARN-3871: - Description: On a 3-Master HDP 2.3 cluster installed with HDP-2.3.0.0-2482 and Ambari-2.1.0-1266, the

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609119#comment-14609119 ] Arun Suresh commented on YARN-3633: --- [~ragarwal], Was just wondering.. wrt the scenario

[jira] [Updated] (YARN-3871) ResourceManager down after Blueprint install

[ https://issues.apache.org/jira/browse/YARN-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zack Marsh updated YARN-3871: - Priority: Major (was: Critical) ResourceManager down after Blueprint install

[jira] [Updated] (YARN-3872) TimelineReader Web UI Implementation

[ https://issues.apache.org/jira/browse/YARN-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3872: --- Issue Type: Sub-task (was: Bug) Parent: YARN-2928 TimelineReader Web UI Implementation

[jira] [Commented] (YARN-3827) Migrate YARN native build to new CMake framework

[ https://issues.apache.org/jira/browse/YARN-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609252#comment-14609252 ] Hudson commented on YARN-3827: -- FAILURE: Integrated in Hadoop-trunk-Commit #8100 (See

[jira] [Comment Edited] (YARN-3827) Migrate YARN native build to new CMake framework

[ https://issues.apache.org/jira/browse/YARN-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609251#comment-14609251 ] Colin Patrick McCabe edited comment on YARN-3827 at 6/30/15 11:32 PM:

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609278#comment-14609278 ] Arun Suresh commented on YARN-3633: --- I guess the line that was introduced needs to be

[jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609160#comment-14609160 ] Varun Saxena commented on YARN-3047: [~sjlee0], bq. As for the tests (and for the

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609172#comment-14609172 ] Varun Saxena commented on YARN-3051: bq. Maybe we can hold back the method and promote

[jira] [Commented] (YARN-3800) Simplify inmemory state for ReservationAllocation

[ https://issues.apache.org/jira/browse/YARN-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609174#comment-14609174 ] Anubhav Dhoot commented on YARN-3800: - [~kasha] [~jianhe] appreciate your review of

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609205#comment-14609205 ] Sangjin Lee commented on YARN-3051: --- bq. It's not that straightforward. For example, I

[jira] [Commented] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

[ https://issues.apache.org/jira/browse/YARN-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609240#comment-14609240 ] Colin Patrick McCabe commented on YARN-3844: Thanks for looking at this, Alan.

[jira] [Updated] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-3116: --- Attachment: YARN-3116.v3.patch [Collector wireup] We need an assured way to

[jira] [Commented] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609096#comment-14609096 ] Varun Saxena commented on YARN-3508: BTW, as we are passing RMContext into

  1   2   >