[jira] [Updated] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2820: Description: Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to I

[jira] [Updated] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2820: Description: Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to I

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325561#comment-14325561 ] Tsuyoshi OZAWA commented on YARN-2820: -- [~zxu], thank you for the update! The patch lo

[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-tabpanel&focusedCommentId=14325576#comment-14325576 ] Sunil G commented on YARN-2004: --- About the priority inversion problem, I feel we could use be

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325581#comment-14325581 ] Devaraj K commented on YARN-3197: - Thanks [~varun_saxena] for patch and [~rohithsharma] for

[jira] [Updated] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2820: Attachment: YARN-2820.003.patch > Do retry in FileSystemRMStateStore for better error recovery when > update

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325589#comment-14325589 ] zhihai xu commented on YARN-2820: - [~ozawa], thanks for the review. Your suggestion is good

[jira] [Commented] (YARN-3194) After NM restart,completed containers are not released by RM which are sent during NM registration

[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325610#comment-14325610 ] Rohith commented on YARN-3194: -- Thanks [~jlowe] [~djp] [~jianhe] for detailed review:-) bq. t

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

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

[jira] [Commented] (YARN-3199) Fair Scheduler documentation improvements

[ https://issues.apache.org/jira/browse/YARN-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325618#comment-14325618 ] Gururaj Shetty commented on YARN-3199: -- [~ka...@cloudera.com] your comment is been inc

[jira] [Updated] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3194: - Summary: After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected no

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325621#comment-14325621 ] zhihai xu commented on YARN-2820: - I checked the warning message, all these 5 findbugs are

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325620#comment-14325620 ] Varun Saxena commented on YARN-3197: Hmm...But we do have Container ID. Would it be rig

[jira] [Created] (YARN-3211) Do not use zero as the beginning number for commands for LinuxContainerExecutor

Liang-Chi Hsieh created YARN-3211: - Summary: Do not use zero as the beginning number for commands for LinuxContainerExecutor Key: YARN-3211 URL: https://issues.apache.org/jira/browse/YARN-3211 Project

[jira] [Updated] (YARN-3211) Do not use zero as the beginning number for commands for LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated YARN-3211: -- Attachment: YARN-3211.patch > Do not use zero as the beginning number for commands for > LinuxCo

[jira] [Updated] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3194: - Description: On NM restart ,NM sends all the outstanding NMContainerStatus to RM during registration. The registra

[jira] [Updated] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3194: - Description: On NM restart ,NM sends all the outstanding NMContainerStatus to RM during registration. The registra

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

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

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325702#comment-14325702 ] Devaraj K commented on YARN-3197: - rmContainer could be null when SchedulerApplicationAttem

[jira] [Commented] (YARN-3207) secondary filter matches entites which do not have the key being filtered for.

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

[jira] [Commented] (YARN-3207) secondary filter matches entites which do not have the key being filtered for.

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

[jira] [Commented] (YARN-3207) secondary filter matches entites which do not have the key being filtered for.

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

[jira] [Commented] (YARN-3207) secondary filter matches entites which do not have the key being filtered for.

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

[jira] [Commented] (YARN-3207) secondary filter matches entites which do not have the key being filtered for.

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

[jira] [Commented] (YARN-3207) secondary filter matches entites which do not have the key being filtered for.

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

[jira] [Commented] (YARN-1916) Leveldb timeline store applies secondary filters incorrectly

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

[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-tabpanel&focusedCommentId=14326145#comment-14326145 ] Jason Lowe commented on YARN-2004: -- I'm not sure I understand the priority inversion probl

[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 ] Sunil G updated YARN-3136: -- Attachment: 0003-YARN-3136.patch Yes [~jlowe]. Its good to keep the backward compatibility. bq. can be overridden

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

[ https://issues.apache.org/jira/browse/YARN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-914: Attachment: GracefullyDecommissionofNodeManagerv3.pdf Update proposal to incorporate most comments above, incl

[jira] [Commented] (YARN-3041) [Data Model] create overall data objects of TS next gen

[ https://issues.apache.org/jira/browse/YARN-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326178#comment-14326178 ] Joep Rottinghuis commented on YARN-3041: Agreed with [~sjlee0] that we should use

[jira] [Commented] (YARN-3041) [Data Model] create overall data objects of TS next gen

[ https://issues.apache.org/jira/browse/YARN-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326183#comment-14326183 ] Joep Rottinghuis commented on YARN-3041: Some additional throughs: If we have the t

[jira] [Updated] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3194: - Attachment: 0001-YARN-3194.patch > After NM restart, RM should handle NMCotainerStatuses sent by NM while > regist

[jira] [Commented] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326191#comment-14326191 ] Rohith commented on YARN-3194: -- Attached the patch addressing all the above comments.. Kindly

[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-tabpanel&focusedCommentId=14326197#comment-14326197 ] Sunil G commented on YARN-2004: --- Hi Jason, thank you for sharing the thoughts. In one way, w

[jira] [Commented] (YARN-3041) [Data Model] create overall data objects of TS next gen

[ https://issues.apache.org/jira/browse/YARN-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326185#comment-14326185 ] Joep Rottinghuis commented on YARN-3041: I think version may have to be something m

[jira] [Commented] (YARN-933) Potential InvalidStateTransitonException: Invalid event: LAUNCHED at FINAL_SAVING

[ https://issues.apache.org/jira/browse/YARN-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326235#comment-14326235 ] Rohith commented on YARN-933: - [~jianhe] kindly review the updated patch. > Potential InvalidSt

[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-tabpanel&focusedCommentId=14326238#comment-14326238 ] Jason Lowe commented on YARN-2004: -- For your first scenario, it can happen today without p

[jira] [Created] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

Junping Du created YARN-3212: Summary: RMNode State Transition Update with DECOMMISSIONING state Key: YARN-3212 URL: https://issues.apache.org/jira/browse/YARN-3212 Project: Hadoop YARN Issue Typ

[jira] [Updated] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

[ https://issues.apache.org/jira/browse/YARN-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3212: - Attachment: RMNodeImpl - new.png Attache the new state transition diagram for RMNode. > RMNode State Trans

[jira] [Commented] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

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

[jira] [Commented] (YARN-2942) Aggregated Log Files should be compacted

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326333#comment-14326333 ] Karthik Kambatla commented on YARN-2942: I have been involved in the design. I like

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326344#comment-14326344 ] Wangda Tan commented on YARN-3197: -- I think it's better not saying {code} 1276

[jira] [Commented] (YARN-2942) Aggregated Log Files should be compacted

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326368#comment-14326368 ] Robert Kanter commented on YARN-2942: - In the end, the cleaner service isn't necessary

[jira] [Commented] (YARN-3132) RMNodeLabelsManager should remove node from node-to-label mapping when node becomes deactivated

[ https://issues.apache.org/jira/browse/YARN-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326460#comment-14326460 ] Jian He commented on YARN-3132: --- +1 > RMNodeLabelsManager should remove node from node-to-la

[jira] [Commented] (YARN-3132) RMNodeLabelsManager should remove node from node-to-label mapping when node becomes deactivated

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

[jira] [Commented] (YARN-3166) [Source organization] Decide detailed package structures for timeline service v2 components

[ https://issues.apache.org/jira/browse/YARN-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326538#comment-14326538 ] Li Lu commented on YARN-3166: - Hi [~sjlee0], [~rkanter], [~zjshen] and [~vinodkv], would (anyon

[jira] [Commented] (YARN-933) Potential InvalidStateTransitonException: Invalid event: LAUNCHED at FINAL_SAVING

[ https://issues.apache.org/jira/browse/YARN-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326557#comment-14326557 ] Jian He commented on YARN-933: -- lgtm, +1 > Potential InvalidStateTransitonException: Invalid e

[jira] [Updated] (YARN-1615) Fix typos in FSAppAttempt.java

[ https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-1615: Attachment: YARN-1615-002.patch Attaching a patch. > Fix typos in FSAppAttempt.java > --

[jira] [Updated] (YARN-1615) Fix typos in FSAppAttempt.java

[ https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-1615: Description: In FSAppAttempt.java there're 4 typos: {code} * containers over rack-local or o

[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-tabpanel&focusedCommentId=14326582#comment-14326582 ] Wangda Tan commented on YARN-2004: -- [~sunilg], Thanks for uploading patch, I just read co

[jira] [Commented] (YARN-3034) [Aggregator wireup] Implement RM starting its ATS writer

[ https://issues.apache.org/jira/browse/YARN-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326630#comment-14326630 ] Li Lu commented on YARN-3034: - Hi [~Naganarasimha], thanks for the patch! I briefly looked at i

[jira] [Commented] (YARN-2942) Aggregated Log Files should be compacted

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326637#comment-14326637 ] Karthik Kambatla commented on YARN-2942: Thanks for clarifying that, Robert. Also,

[jira] [Created] (YARN-3213) Respect labels in Capacity Scheduler when computing user-limit

Wangda Tan created YARN-3213: Summary: Respect labels in Capacity Scheduler when computing user-limit Key: YARN-3213 URL: https://issues.apache.org/jira/browse/YARN-3213 Project: Hadoop YARN Iss

[jira] [Updated] (YARN-3214) Add non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3214: - Summary: Add non-exclusive node labels (was: Adding non-exclusive node labels ) > Add non-exclusive node

[jira] [Created] (YARN-3214) Adding non-exclusive node labels

Wangda Tan created YARN-3214: Summary: Adding non-exclusive node labels Key: YARN-3214 URL: https://issues.apache.org/jira/browse/YARN-3214 Project: Hadoop YARN Issue Type: Sub-task Co

[jira] [Created] (YARN-3215) Respect labels in CapacityScheduler when computing headroom

Wangda Tan created YARN-3215: Summary: Respect labels in CapacityScheduler when computing headroom Key: YARN-3215 URL: https://issues.apache.org/jira/browse/YARN-3215 Project: Hadoop YARN Issue

[jira] [Created] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

Wangda Tan created YARN-3216: Summary: Max-AM-Resource-Percentage should respect node labels Key: YARN-3216 URL: https://issues.apache.org/jira/browse/YARN-3216 Project: Hadoop YARN Issue Type: S

[jira] [Commented] (YARN-1615) Fix typos in FSAppAttempt.java

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

[jira] [Commented] (YARN-3040) [Data Model] Implement client-side API for handling flows

[ https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326716#comment-14326716 ] Robert Kanter commented on YARN-3040: - [~Naganarasimha] # I think the Entities (YARN-30

[jira] [Commented] (YARN-2942) Aggregated Log Files should be compacted

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326722#comment-14326722 ] Robert Kanter commented on YARN-2942: - Sure. I think Combined Aggregated Logs is more

[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-tabpanel&focusedCommentId=14326737#comment-14326737 ] Jason Lowe commented on YARN-2004: -- I took a closer look at the patch, and the following l

[jira] [Updated] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-2942: Summary: Aggregated Log Files should be combined (was: Aggregated Log Files should be compacted) >

[jira] [Updated] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-2942: Attachment: CombinedAggregatedLogsProposal_v3.pdf I've just uploaded CombinedAggregatedLogsProposal_v

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

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

[jira] [Commented] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326772#comment-14326772 ] Jian He commented on YARN-1514: --- +1 > Utility to benchmark ZKRMStateStore#loadState for Reso

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

Akira AJISAKA created YARN-3217: --- Summary: Remove httpclient dependency from hadoop-yarn-server-web-proxy Key: YARN-3217 URL: https://issues.apache.org/jira/browse/YARN-3217 Project: Hadoop YARN

[jira] [Commented] (YARN-3166) [Source organization] Decide detailed package structures for timeline service v2 components

[ https://issues.apache.org/jira/browse/YARN-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326812#comment-14326812 ] Zhijie Shen commented on YARN-3166: --- Thanks for raising the package structure definition.

[jira] [Created] (YARN-3218) Implement CombinedAggregatedLogFormat Reader and Writer

Robert Kanter created YARN-3218: --- Summary: Implement CombinedAggregatedLogFormat Reader and Writer Key: YARN-3218 URL: https://issues.apache.org/jira/browse/YARN-3218 Project: Hadoop YARN Issue

[jira] [Created] (YARN-3219) Use CombinedAggregatedLogFormat Writer to combine aggregated log files

Robert Kanter created YARN-3219: --- Summary: Use CombinedAggregatedLogFormat Writer to combine aggregated log files Key: YARN-3219 URL: https://issues.apache.org/jira/browse/YARN-3219 Project: Hadoop YARN

[jira] [Created] (YARN-3220) JHS should display Combined Aggregated Logs when available

Robert Kanter created YARN-3220: --- Summary: JHS should display Combined Aggregated Logs when available Key: YARN-3220 URL: https://issues.apache.org/jira/browse/YARN-3220 Project: Hadoop YARN Is

[jira] [Commented] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

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

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326821#comment-14326821 ] Robert Kanter commented on YARN-2942: - I've created 4 subtasks (one is in HADOOP): # HA

[jira] [Commented] (YARN-3166) [Source organization] Decide detailed package structures for timeline service v2 components

[ https://issues.apache.org/jira/browse/YARN-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326823#comment-14326823 ] Li Lu commented on YARN-3166: - bq. 1. Should we sort out the package for RM and NM code of writ

[jira] [Updated] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3122: Attachment: YARN-3122.002.patch Fixed the test failure. The test was failing because the test was doi

[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 ] Akira AJISAKA updated YARN-3217: Labels: newbie (was: ) > Remove httpclient dependency from hadoop-yarn-server-web-proxy > --

[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-tabpanel&focusedCommentId=14326830#comment-14326830 ] Li Lu commented on YARN-3087: - I found this issue (#635 of Guice, https://code.google.com/p/go

[jira] [Commented] (YARN-1615) Fix typos in FSAppAttempt.java

[ https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326831#comment-14326831 ] Tsuyoshi OZAWA commented on YARN-1615: -- +1, committing this shortly. > Fix typos in F

[jira] [Created] (YARN-3221) Applications should be able to 're-register'

Sidharta Seethana created YARN-3221: --- Summary: Applications should be able to 're-register' Key: YARN-3221 URL: https://issues.apache.org/jira/browse/YARN-3221 Project: Hadoop YARN Issue T

[jira] [Updated] (YARN-1615) Fix typos in delay scheduler's description

[ https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1615: - Summary: Fix typos in delay scheduler's description (was: Fix typos in FSAppAttempt.java) > Fix t

[jira] [Assigned] (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 reassigned YARN-3217: -- Assignee: Brahma Reddy Battula > Remove httpclient dependency from hadoop-yarn-s

[jira] [Updated] (YARN-1615) Fix typos in description about delay scheduling

[ https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1615: - Summary: Fix typos in description about delay scheduling (was: Fix typos in delay scheduler's desc

[jira] [Updated] (YARN-1615) Fix typos in description about delay scheduling

[ https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1615: - Hadoop Flags: Reviewed > Fix typos in description about delay scheduling >

[jira] [Updated] (YARN-3218) Implement CombinedAggregatedLogFormat Reader and Writer

[ https://issues.apache.org/jira/browse/YARN-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3218: Attachment: YARN-3218.001.patch > Implement CombinedAggregatedLogFormat Reader and Writer > -

[jira] [Commented] (YARN-3076) YarnClient implementation to retrieve label to node mapping

[ https://issues.apache.org/jira/browse/YARN-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326861#comment-14326861 ] Wangda Tan commented on YARN-3076: -- Thanks, patch LGTM, will commit after Jenkins get back

[jira] [Commented] (YARN-3122) Metrics for container's actual CPU usage

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

[jira] [Commented] (YARN-1615) Fix typos in description about delay scheduling

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

[jira] [Commented] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326877#comment-14326877 ] Tsuyoshi OZAWA commented on YARN-1514: -- Thanks Jian for your review! > Utility to ben

[jira] [Commented] (YARN-1615) Fix typos in description about delay scheduling

[ https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326898#comment-14326898 ] Akira AJISAKA commented on YARN-1615: - Thanks Tsuyoshi for review and commit. > Fix ty

[jira] [Commented] (YARN-3218) Implement CombinedAggregatedLogFormat Reader and Writer

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

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326912#comment-14326912 ] Vinod Kumar Vavilapalli commented on YARN-2942: --- Apologies for coming in real

[jira] [Commented] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326924#comment-14326924 ] Rohith commented on YARN-3194: -- FIndbugs warnings are unrelated to this Jira. These warnings w

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326953#comment-14326953 ] Robert Kanter commented on YARN-2942: - {quote}We should try to avoid rereading the enti

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326958#comment-14326958 ] Vinod Kumar Vavilapalli commented on YARN-2942: --- bq. The problem here is that

[jira] [Created] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

Rohith created YARN-3222: Summary: RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order Key: YARN-3222 URL: https://issues.apache.org/jira/browse/YARN-3222 Project: Hadoop YARN

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326965#comment-14326965 ] Rohith commented on YARN-3222: -- Attaching the logs which gives more information about issue. I

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326969#comment-14326969 ] Rohith commented on YARN-3197: -- bq. Do you see any other info logs coming for the same contain

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326980#comment-14326980 ] Rohith commented on YARN-3197: -- bq. I think INFO could be fine since it will be at most once f

[jira] [Commented] (YARN-3166) [Source organization] Decide detailed package structures for timeline service v2 components

[ https://issues.apache.org/jira/browse/YARN-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326987#comment-14326987 ] Zhijie Shen commented on YARN-3166: --- bq. I assume they will post data through our clients

[jira] [Commented] (YARN-3076) YarnClient implementation to retrieve label to node mapping

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

[jira] [Updated] (YARN-3041) [Data Model] create overall data objects of TS next gen

[ https://issues.apache.org/jira/browse/YARN-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3041: -- Attachment: YARN-3041.5.patch Thanks for the feedback, Sangjin, Vrushali and Joep! We had an offline dis

  1   2   >