[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v7.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Commented] (YARN-2986) (Umbrella) Support hierarchical and unified scheduler configuration

[ https://issues.apache.org/jira/browse/YARN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337372#comment-14337372 ] Wangda Tan commented on YARN-2986: -- Hi [~jianhe], I think it should only take effect when

[jira] [Created] (YARN-3264) [Storage implementation] Create a POC only file based storage implementation for ATS writes

Vrushali C created YARN-3264: Summary: [Storage implementation] Create a POC only file based storage implementation for ATS writes Key: YARN-3264 URL: https://issues.apache.org/jira/browse/YARN-3264

[jira] [Updated] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2893: Attachment: YARN-2893.000.patch AMLaucher: sporadic job failures due to EOFException in

[jira] [Updated] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3251: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-3243) CapacityScheduler deadlock when

[jira] [Updated] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3251: - Assignee: Craig Welch (was: Wangda Tan) CapacityScheduler deadlock when computing absolute max avail

[jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337567#comment-14337567 ] Wangda Tan commented on YARN-3251: -- +1 for the suggestion, moved it out of YARN-3243,

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337585#comment-14337585 ] Vinod Kumar Vavilapalli commented on YARN-3131: --- Yeah, I missed the larger

[jira] [Updated] (YARN-3255) RM and NM main() should support generic options

[ https://issues.apache.org/jira/browse/YARN-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated YARN-3255: -- Attachment: YARN-3255-02.patch Added {{GenericOptionsParser}} to {{WebAppProxyServer}}

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337668#comment-14337668 ] Abin Shahab commented on YARN-3080: --- [~raviprakash], [~vinodkv], [~vvasudev] [~ywskycn]

[jira] [Updated] (YARN-3262) Suface application resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3262: -- Attachment: YARN-3262.1.patch uploaded a patch to surface the outstanding resource requests on the UI Suface

[jira] [Commented] (YARN-3254) HealthReport should include disk full information

[ https://issues.apache.org/jira/browse/YARN-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337364#comment-14337364 ] Hadoop QA commented on YARN-3254: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337393#comment-14337393 ] Vrushali C commented on YARN-3031: -- Yes, will update it in the next patch. [Storage

[jira] [Commented] (YARN-2928) Application Timeline Server (ATS) next gen: phase 1

[ https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337419#comment-14337419 ] Gopal V commented on YARN-2928: --- The original discussion about ATS v1 drew inspiration from

[jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337529#comment-14337529 ] Vinod Kumar Vavilapalli commented on YARN-3251: --- Actually let's use this JIRA

[jira] [Updated] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3251: - Summary: CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337577#comment-14337577 ] Vinod Kumar Vavilapalli commented on YARN-3265: --- Pasting comments I was going

[jira] [Commented] (YARN-3254) HealthReport should include disk full information

[ https://issues.apache.org/jira/browse/YARN-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337366#comment-14337366 ] Hadoop QA commented on YARN-3254: - {color:red}-1 overall{color}. Here are the results of

[jira] [Created] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

Wangda Tan created YARN-3265: Summary: CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2) Key: YARN-3265 URL: https://issues.apache.org/jira/browse/YARN-3265

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337592#comment-14337592 ] Vinod Kumar Vavilapalli commented on YARN-41: - [~djp], can you please respond to

[jira] [Commented] (YARN-2423) TimelineClient should wrap all GET APIs to facilitate Java users

[ https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337622#comment-14337622 ] Vinod Kumar Vavilapalli commented on YARN-2423: --- [~rkanter], I am just

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337641#comment-14337641 ] Hadoop QA commented on YARN-3080: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3125: - Attachment: YARN-3125v3.patch Thanks [~zjshen] for review and comments! Address both of your comments in

[jira] [Commented] (YARN-3087) [Aggregator implementation] the REST server (web server) for per-node aggregator does not work if it runs inside node manager

[ https://issues.apache.org/jira/browse/YARN-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337921#comment-14337921 ] Hadoop QA commented on YARN-3087: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3251: -- Attachment: YARN-3251.2-6-0.2.patch Patch against branch-2.6.0 CapacityScheduler deadlock when

[jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337962#comment-14337962 ] Craig Welch commented on YARN-3251: --- bq. 1) Since the target of your patch is to make a

[jira] [Assigned] (YARN-3087) [Aggregator implementation] the REST server (web server) for per-node aggregator does not work if it runs inside node manager

[ https://issues.apache.org/jira/browse/YARN-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu reassigned YARN-3087: --- Assignee: Li Lu (was: Devaraj K) [Aggregator implementation] the REST server (web server) for per-node

[jira] [Commented] (YARN-3087) [Aggregator implementation] the REST server (web server) for per-node aggregator does not work if it runs inside node manager

[ https://issues.apache.org/jira/browse/YARN-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337914#comment-14337914 ] Li Lu commented on YARN-3087: - Assign this to myself since this is blocking our prototype, and

[jira] [Updated] (YARN-3087) [Aggregator implementation] the REST server (web server) for per-node aggregator does not work if it runs inside node manager

[ https://issues.apache.org/jira/browse/YARN-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3087: Attachment: YARN-3087-022515.patch I've just updated my patch. This patch is rebased to the latest YARN-2928

[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=14337925#comment-14337925 ] Sangjin Lee commented on YARN-2902: --- We definitely see this (usually coupled with

[jira] [Updated] (YARN-3087) [Aggregator implementation] the REST server (web server) for per-node aggregator does not work if it runs inside node manager

[ https://issues.apache.org/jira/browse/YARN-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3087: Target Version/s: YARN-2928 Fix Version/s: YARN-2928 [Aggregator implementation] the REST server (web

[jira] [Assigned] (YARN-3261) rewrite resourcemanager restart doc to remove roadmap bits

[ https://issues.apache.org/jira/browse/YARN-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gururaj Shetty reassigned YARN-3261: Assignee: Gururaj Shetty rewrite resourcemanager restart doc to remove roadmap bits

[jira] [Commented] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

[ https://issues.apache.org/jira/browse/YARN-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337995#comment-14337995 ] Hadoop QA commented on YARN-3217: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

[ https://issues.apache.org/jira/browse/YARN-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3217: --- Attachment: YARN-3217-004.patch rebased the patch Remove httpclient dependency from

[jira] [Resolved] (YARN-3240) [Data Mode] Implement client API to put generic entities

[ https://issues.apache.org/jira/browse/YARN-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-3240. -- Resolution: Fixed Fix Version/s: YARN-2928 Hadoop Flags: Reviewed I have commit v3 patch to

[jira] [Updated] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gururaj Shetty updated YARN-3168: - Attachment: YARN-3168.20150225.2.patch Convert site documentation from apt to markdown

[jira] [Commented] (YARN-3256) TestClientToAMToken#testClientTokenRace is not running against all Schedulers even when using ParameterizedSchedulerTestBase

[ https://issues.apache.org/jira/browse/YARN-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336333#comment-14336333 ] Rohith commented on YARN-3256: -- Good catch!! +1(non-binding) lgtm

[jira] [Commented] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336332#comment-14336332 ] Gururaj Shetty commented on YARN-3168: -- [~Naganarasimha Garla] Updated your comments

[jira] [Created] (YARN-3257) FairScheduler: MaxAm may be set too low preventing apps from starting

Anubhav Dhoot created YARN-3257: --- Summary: FairScheduler: MaxAm may be set too low preventing apps from starting Key: YARN-3257 URL: https://issues.apache.org/jira/browse/YARN-3257 Project: Hadoop YARN

[jira] [Created] (YARN-3256) TestClientToAMToken#testClientTokenRace is not running against all Schedulers even when using ParameterizedSchedulerTestBase

Anubhav Dhoot created YARN-3256: --- Summary: TestClientToAMToken#testClientTokenRace is not running against all Schedulers even when using ParameterizedSchedulerTestBase Key: YARN-3256 URL:

[jira] [Updated] (YARN-3256) TestClientToAMToken#testClientTokenRace is not running against all Schedulers even when using ParameterizedSchedulerTestBase

[ https://issues.apache.org/jira/browse/YARN-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3256: Attachment: YARN-3256.001.patch Fix that removes the local conf object hiding the base class conf.

[jira] [Updated] (YARN-3249) Add the kill application to the Resource Manager Web UI

[ https://issues.apache.org/jira/browse/YARN-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-3249: - Attachment: killapp-failed.log [~ryu_kobayashi] thank you for updating. I deployed pseudo

[jira] [Commented] (YARN-3249) Add the kill application to the Resource Manager Web UI

[ https://issues.apache.org/jira/browse/YARN-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336314#comment-14336314 ] Hadoop QA commented on YARN-3249: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

[ https://issues.apache.org/jira/browse/YARN-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336183#comment-14336183 ] Hadoop QA commented on YARN-3217: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

[ https://issues.apache.org/jira/browse/YARN-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-3217: - Attachment: YARN-3217-003.patch javac warnings looks strange - let me submit same patch again.

[jira] [Commented] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

[ https://issues.apache.org/jira/browse/YARN-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336197#comment-14336197 ] Brahma Reddy Battula commented on YARN-3217: {{findbugs}},{{Java doc warn}} and

[jira] [Commented] (YARN-3249) Add the kill application to the Resource Manager Web UI

[ https://issues.apache.org/jira/browse/YARN-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336212#comment-14336212 ] Hadoop QA commented on YARN-3249: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

[ https://issues.apache.org/jira/browse/YARN-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336246#comment-14336246 ] Hadoop QA commented on YARN-3217: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3255) RM and NM main() should support generic options

[ https://issues.apache.org/jira/browse/YARN-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336204#comment-14336204 ] Hadoop QA commented on YARN-3255: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336219#comment-14336219 ] Robert Kanter commented on YARN-3039: - Sorry for not commenting earlier. Thanks for

[jira] [Assigned] (YARN-3257) FairScheduler: MaxAm may be set too low preventing apps from starting

[ https://issues.apache.org/jira/browse/YARN-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3257: --- Assignee: Anubhav Dhoot FairScheduler: MaxAm may be set too low preventing apps from

[jira] [Updated] (YARN-3257) FairScheduler: MaxAm may be set too low preventing apps from starting

[ https://issues.apache.org/jira/browse/YARN-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3257: Attachment: YARN-3257.001.patch Patch demonstrating the behavior change FairScheduler: MaxAm may

[jira] [Commented] (YARN-3256) TestClientToAMToken#testClientTokenRace is not running against all Schedulers even when using ParameterizedSchedulerTestBase

[ https://issues.apache.org/jira/browse/YARN-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336370#comment-14336370 ] Hadoop QA commented on YARN-3256: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3249) Add the kill application to the Resource Manager Web UI

[ https://issues.apache.org/jira/browse/YARN-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryu Kobayashi updated YARN-3249: Attachment: YARN-3249.3.patch Add the kill application to the Resource Manager Web UI

[jira] [Commented] (YARN-3249) Add the kill application to the Resource Manager Web UI

[ https://issues.apache.org/jira/browse/YARN-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336375#comment-14336375 ] Ryu Kobayashi commented on YARN-3249: - [~ozawa] got it. I have attached a patch that

[jira] [Commented] (YARN-2980) Move health check script related functionality to hadoop-common

[ https://issues.apache.org/jira/browse/YARN-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336382#comment-14336382 ] Hudson commented on YARN-2980: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #115 (See

[jira] [Commented] (YARN-3247) TestQueueMappings should use CapacityScheduler explicitly

[ https://issues.apache.org/jira/browse/YARN-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336390#comment-14336390 ] Hudson commented on YARN-3247: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #115 (See

[jira] [Updated] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3125: - Attachment: YARN-3125v2.patch [Event producers] Change distributed shell to use new timeline service

[jira] [Commented] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336395#comment-14336395 ] Junping Du commented on YARN-3125: -- Thanks for comments, [~vinodkv] and [~zjshen]!

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336396#comment-14336396 ] Tsuyoshi Ozawa commented on YARN-1809: -- Sure, let me check. Synchronize RM and

<    1   2