[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934695#comment-14934695 ] zhihai xu commented on YARN-4209: - Thanks for the review [~rohithsharma]! Yes, that is a go

[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934670#comment-14934670 ] Rohith Sharma K S commented on YARN-4209: - I debugged your test case, and I got you

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

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934627#comment-14934627 ] Hudson commented on YARN-4180: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2372 (See [https://

[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934605#comment-14934605 ] Rohith Sharma K S commented on YARN-4209: - bq. removeRMDelegationToken => handleSto

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934534#comment-14934534 ] Dian Fu commented on YARN-3964: --- Thanks a lot for the comments [~leftnoteasy]. What's your th

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

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934516#comment-14934516 ] Hudson commented on YARN-4180: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2399 (See [htt

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934515#comment-14934515 ] Hudson commented on YARN-4141: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2399 (See [htt

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

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934506#comment-14934506 ] Hudson commented on YARN-4180: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #431 (See [htt

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

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934504#comment-14934504 ] Hudson commented on YARN-4180: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1194 (See [https://

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934492#comment-14934492 ] Hudson commented on YARN-4141: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2371 (See [https://

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

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934485#comment-14934485 ] Brahma Reddy Battula commented on YARN-3528: [~rkanter] can you please take a l

[jira] [Commented] (YARN-4075) [reader REST API] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934454#comment-14934454 ] Li Lu commented on YARN-4075: - BTW, I hit NPEs with the above format. I also checked my hbase a

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

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934453#comment-14934453 ] Hudson commented on YARN-4180: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #462 (See [htt

[jira] [Commented] (YARN-4075) [reader REST API] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934450#comment-14934450 ] Li Lu commented on YARN-4075: - Hi [~varun_saxena]. I'm working on the web UI POC right now and

[jira] [Commented] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934442#comment-14934442 ] Sangjin Lee commented on YARN-4178: --- Thanks [~varun_saxena] for the proposed patch. I'm g

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

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

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934423#comment-14934423 ] Hudson commented on YARN-4141: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #1193 (See [https://

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934418#comment-14934418 ] Naganarasimha G R commented on YARN-3964: - Thanks for the input [~wangda], Yes it w

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934405#comment-14934405 ] Hudson commented on YARN-4141: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #461 (See [htt

[jira] [Updated] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-4178: -- Description: Currently the app id is used in various places as part of row keys. However, currently they

[jira] [Updated] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-4178: -- Summary: [storage implementation] app id as string in row keys can cause incorrect ordering (was: [stora

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

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4180: Attachment: YARN-4180-branch-2.7.2.txt Minor conflicts in backporting changes to branch 2.7 > AMLaun

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934393#comment-14934393 ] Hudson commented on YARN-4141: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #430 (See [htt

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

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934368#comment-14934368 ] Hudson commented on YARN-4180: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #455 (See

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934367#comment-14934367 ] Hudson commented on YARN-4141: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #455 (See

[jira] [Commented] (YARN-3996) YARN-789 (Support for zero capabilities in fairscheduler) is broken after YARN-3305

[ https://issues.apache.org/jira/browse/YARN-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934349#comment-14934349 ] Neelesh Srinivas Salian commented on YARN-3996: --- I would like to work on this

[jira] [Commented] (YARN-4185) Retry interval delay for NM client can be improved from the fixed static retry

[ https://issues.apache.org/jira/browse/YARN-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934350#comment-14934350 ] Neelesh Srinivas Salian commented on YARN-4185: --- I would like to work on this

[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=14934342#comment-14934342 ] Wangda Tan commented on YARN-4172: -- Haven't finished all review, some comments so far: 1)

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

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934339#comment-14934339 ] Hudson commented on YARN-4180: -- FAILURE: Integrated in Hadoop-trunk-Commit #8535 (See [https:

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934338#comment-14934338 ] Hudson commented on YARN-4141: -- FAILURE: Integrated in Hadoop-trunk-Commit #8535 (See [https:

[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934261#comment-14934261 ] zhihai xu commented on YARN-4209: - Hi [~jianhe], Could you help review the patch? I add loc

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934256#comment-14934256 ] Jason Lowe commented on YARN-4141: -- +1 lgtm. Committing this. > Runtime Application Prio

[jira] [Commented] (YARN-4204) ConcurrentModificationException in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934217#comment-14934217 ] Hudson commented on YARN-4204: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #429 (See [htt

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

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

[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

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

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934169#comment-14934169 ] Wangda Tan commented on YARN-3964: -- [~dian.fu], bq. RMDelegatedNodeLabelsUpdater doesn't c

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934155#comment-14934155 ] Wangda Tan commented on YARN-3964: -- bq. This piece of code i think should be done by the c

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934124#comment-14934124 ] Sangjin Lee commented on YARN-3554: --- The change applied cleanly to branch-2.6 for 2.6.2.

[jira] [Updated] (YARN-1415) In scheduler UI, including used memory in "Memory Total" seems to be inaccurate

[ https://issues.apache.org/jira/browse/YARN-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1415: -- Fix Version/s: (was: 2.1.0-beta) > In scheduler UI, including used memory in

[jira] [Commented] (YARN-4204) ConcurrentModificationException in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933869#comment-14933869 ] Hudson commented on YARN-4204: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2369 (See [https://

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933864#comment-14933864 ] Jason Lowe commented on YARN-3942: -- Greg wrote: bq. I was even able to create the problem

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.2.patch > Make AMRMClient support send increase container request and get > increased/

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.1.patch Submit the first patch for review. [~leftnoteasy], recall during design stage

[jira] [Updated] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4209: Attachment: YARN-4209.000.patch > RMStateStore FENCED state doesn’t work due to updateFencedState called by

[jira] [Updated] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4209: Attachment: (was: YARN-4209.000.patch) > RMStateStore FENCED state doesn’t work due to updateFencedState

[jira] [Assigned] (YARN-162) nodemanager log aggregation has scaling issues with namenode

[ https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla reassigned YARN-162: Assignee: Kuhu Shukla (was: Siddharth Seth) > nodemanager log aggregation has scaling issues with na

[jira] [Updated] (YARN-1501) Fair Scheduler will NPE if it hits IOException on queue assignment

[ https://issues.apache.org/jira/browse/YARN-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1501: -- Fix Version/s: (was: 2.2.1) Dropping fix-version which should be set at commi

[jira] [Updated] (YARN-1513) One message is misleading in LogsCLI

[ https://issues.apache.org/jira/browse/YARN-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1513: -- Fix Version/s: (was: 2.2.1) Dropping fix-version which should be set at commi

[jira] [Commented] (YARN-4204) ConcurrentModificationException in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933768#comment-14933768 ] Hudson commented on YARN-4204: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #1191 (See [https://

[jira] [Commented] (YARN-4204) ConcurrentModificationException in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933765#comment-14933765 ] Hudson commented on YARN-4204: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #458 (See [htt

[jira] [Closed] (YARN-3301) Fix the format issue of the new RM web UI and AHS web UI after YARN-3272 / YARN-3262

[ https://issues.apache.org/jira/browse/YARN-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli closed YARN-3301. - > Fix the format issue of the new RM web UI and AHS web UI after YARN-3272 / > YARN-32

[jira] [Updated] (YARN-3724) Use POSIX nftw(3) instead of fts(3)

[ https://issues.apache.org/jira/browse/YARN-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3724: -- Target Version/s: 2.8.0, 2.7.2 Fix Version/s: (was: 2.7.1) [~alanburli

[jira] [Commented] (YARN-162) nodemanager log aggregation has scaling issues with namenode

[ https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933751#comment-14933751 ] Siddharth Seth commented on YARN-162: - Go ahead. > nodemanager log aggregation has scal

[jira] [Closed] (YARN-3700) ATS Web Performance issue at load time when large number of jobs

[ https://issues.apache.org/jira/browse/YARN-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli closed YARN-3700. - > ATS Web Performance issue at load time when large number of jobs > --

[jira] [Closed] (YARN-3740) Fixed the typo with the configuration name: APPLICATION_HISTORY_PREFIX_MAX_APPS

[ https://issues.apache.org/jira/browse/YARN-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli closed YARN-3740. - > Fixed the typo with the configuration name: > APPLICATION_HISTORY_PREFIX_MAX_APPS >

[jira] [Closed] (YARN-3999) RM hangs on draining events

[ https://issues.apache.org/jira/browse/YARN-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli closed YARN-3999. - > RM hangs on draining events > --- > > Key: YA

[jira] [Closed] (YARN-2890) MiniYarnCluster should turn on timeline service if configured to do so

[ https://issues.apache.org/jira/browse/YARN-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli closed YARN-2890. - > MiniYarnCluster should turn on timeline service if configured to do so >

[jira] [Closed] (YARN-3978) Configurably turn off the saving of container info in Generic AHS

[ https://issues.apache.org/jira/browse/YARN-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli closed YARN-3978. - > Configurably turn off the saving of container info in Generic AHS > -

[jira] [Closed] (YARN-3248) Display count of nodes blacklisted by apps in the web UI

[ https://issues.apache.org/jira/browse/YARN-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli closed YARN-3248. - > Display count of nodes blacklisted by apps in the web UI > --

[jira] [Closed] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli closed YARN-3990. - > AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is > connected/di

[jira] [Closed] (YARN-4047) ClientRMService getApplications has high scheduler lock contention

[ https://issues.apache.org/jira/browse/YARN-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli closed YARN-4047. - > ClientRMService getApplications has high scheduler lock contention >

[jira] [Commented] (YARN-4203) Add request/response logging & timing for each REST endpoint call

[ https://issues.apache.org/jira/browse/YARN-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933726#comment-14933726 ] Vrushali C commented on YARN-4203: -- Thanks [~varun_saxena], patch looks good to me. + 1

[jira] [Commented] (YARN-4204) ConcurrentModificationException in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933691#comment-14933691 ] Hudson commented on YARN-4204: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2396 (See [htt

[jira] [Updated] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-3554: -- Fix Version/s: 2.6.2 > Default value for maximum nodemanager connect wait time is too high >

[jira] [Updated] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-3554: -- Target Version/s: 2.7.1, 2.6.2 (was: 2.7.1) > Default value for maximum nodemanager connect wait time is

[jira] [Updated] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-3944: -- Target Version/s: (was: 2.7.2, 2.6.2) > Connection refused to nodemanagers are retried at multiple leve

[jira] [Commented] (YARN-4204) ConcurrentModificationException in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933641#comment-14933641 ] Hudson commented on YARN-4204: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #452 (See

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933639#comment-14933639 ] Siqi Li commented on YARN-3944: --- Agreed, I will close this one > Connection refused to nodem

[jira] [Commented] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

[ https://issues.apache.org/jira/browse/YARN-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933636#comment-14933636 ] Bibin A Chundatt commented on YARN-4140: Checkstyle issues are not from modified li

[jira] [Commented] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933617#comment-14933617 ] Sangjin Lee commented on YARN-1480: --- [~kj-ki], [~zjshen], any update on this JIRA? > RM

[jira] [Commented] (YARN-1681) When "banned.users" is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message

[ https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933615#comment-14933615 ] Sangjin Lee commented on YARN-1681: --- [~wzc1989], would you be able to pick this up again

[jira] [Commented] (YARN-2506) TimelineClient should NOT be in yarn-common project

[ https://issues.apache.org/jira/browse/YARN-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933611#comment-14933611 ] Sangjin Lee commented on YARN-2506: --- [~zjshen], is this something that can be done relati

[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-tabpanel&focusedCommentId=14933600#comment-14933600 ] Sangjin Lee commented on YARN-3798: --- [~varun_saxena], [~ozawa], [~zxu], where are we on t

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933594#comment-14933594 ] Sangjin Lee commented on YARN-3944: --- [~l201514], [~zxu], what's your thought on this? Sho

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933584#comment-14933584 ] Dian Fu commented on YARN-3964: --- Hi [~Naganarasimha] and [~sunilg], Thanks for your comments.

[jira] [Commented] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

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

[jira] [Commented] (YARN-4204) ConcurrentModificationException in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933550#comment-14933550 ] Hudson commented on YARN-4204: -- FAILURE: Integrated in Hadoop-trunk-Commit #8531 (See [https:

[jira] [Commented] (YARN-4204) ConcurrentModificationException in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933547#comment-14933547 ] Anubhav Dhoot commented on YARN-4204: - Committed to trunk and branch-2. Thanks [~kasha]

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

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

[jira] [Updated] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4205: Attachment: YARN-4205_03.patch > Add a service for monitoring application life time out > ---

[jira] [Commented] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933513#comment-14933513 ] nijel commented on YARN-4205: - Thanks [~rohithsharma] for the comments Updated the patch. > A

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933506#comment-14933506 ] Varun Saxena commented on YARN-4178: Also for the sake of consistency, I have done the

[jira] [Commented] (YARN-4053) Change the way metric values are stored in HBase Storage

[ https://issues.apache.org/jira/browse/YARN-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933492#comment-14933492 ] Varun Saxena commented on YARN-4053: I think we need to revive this JIRA and decide its

[jira] [Commented] (YARN-4170) AM need to be notified with priority in AllocateResponse

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

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933487#comment-14933487 ] Varun Saxena commented on YARN-4178: After giving some further thought over it, in the

[jira] [Updated] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4178: --- Attachment: YARN-4178-YARN-2928.01.patch > [storage implementation] app id as string can cause incorrec

[jira] [Commented] (YARN-4155) TestLogAggregationService.testLogAggregationServiceWithInterval failing

[ https://issues.apache.org/jira/browse/YARN-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933471#comment-14933471 ] Bibin A Chundatt commented on YARN-4155: Please review patch attached > TestLogAgg

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

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

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933455#comment-14933455 ] Naganarasimha G R commented on YARN-3964: - Hi [~sunilg] and [~wangda], One small op

[jira] [Updated] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4178: --- Attachment: (was: YARN-4178-YARN-2928.01.patch) > [storage implementation] app id as string can cau

[jira] [Updated] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4178: --- Attachment: YARN-4178-YARN-2928.01.patch > [storage implementation] app id as string can cause incorrec

[jira] [Updated] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

[ https://issues.apache.org/jira/browse/YARN-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4140: --- Attachment: 0012-YARN-4140.patch > RM container allocation delayed incase of app submitted to N

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933423#comment-14933423 ] Sunil G commented on YARN-3964: --- Hi [~Naganarasimha Garla] I had this concern also earlier. {

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933385#comment-14933385 ] Naganarasimha G R commented on YARN-3964: - Hi [~dian.fu], The scenario what is addr

[jira] [Updated] (YARN-4170) AM need to be notified with priority in AllocateResponse

[ https://issues.apache.org/jira/browse/YARN-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4170: -- Attachment: 0002-YARN-4170.patch Re-basing the patch as it has gone stale. Hi [~jianhe] and [~jlowe] Could you p

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933342#comment-14933342 ] Dian Fu commented on YARN-3964: --- Hi [~leftnoteasy], Thanks a lot for your review. Updated the

[jira] [Updated] (YARN-4142) add a way for an attempt to report an attempt failure

[ https://issues.apache.org/jira/browse/YARN-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4142: -- Attachment: 0001-YARN-4142.patch Uploading an initial version of patch. Few points: - Used a new configuration f

[jira] [Updated] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dian Fu updated YARN-3964: -- Attachment: YARN-3964.012.patch > Support NodeLabelsProvider at Resource Manager side > -

[jira] [Commented] (YARN-4203) Add request/response logging & timing for each REST endpoint call

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

[jira] [Updated] (YARN-4169) jenkins trunk+java build failed in TestNodeStatusUpdaterForLabels

[ https://issues.apache.org/jira/browse/YARN-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4169: Attachment: YARN-4169.v1.003.patch > jenkins trunk+java build failed in TestNodeStatusUpdater

  1   2   >