[jira] [Assigned] (YARN-9243) Support limiting network outbound bandwidth for multiple interfaces
[ https://issues.apache.org/jira/browse/YARN-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam reassigned YARN-9243: -- Assignee: kyungwan nam > Support limiting network outbound bandwidth for multiple interfaces > --- > > Key: YARN-9243 > URL: https://issues.apache.org/jira/browse/YARN-9243 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: kyungwan nam >Assignee: kyungwan nam >Priority: Major > Attachments: YARN-9243.001.patch > > > YARN-3366 introduced limiting network outbound bandwidth. currently it is > available for one network interface. > but, we need to set for multiple interfaces in some circumstances. > It would be good if it can be set for multiple interfaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9243) Support limiting network outbound bandwidth for multiple interfaces
[ https://issues.apache.org/jira/browse/YARN-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753756#comment-16753756 ] kyungwan nam commented on YARN-9243: Attaches patch. please review or any comment > Support limiting network outbound bandwidth for multiple interfaces > --- > > Key: YARN-9243 > URL: https://issues.apache.org/jira/browse/YARN-9243 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: kyungwan nam >Priority: Major > Attachments: YARN-9243.001.patch > > > YARN-3366 introduced limiting network outbound bandwidth. currently it is > available for one network interface. > but, we need to set for multiple interfaces in some circumstances. > It would be good if it can be set for multiple interfaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9243) Support limiting network outbound bandwidth for multiple interfaces
[ https://issues.apache.org/jira/browse/YARN-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-9243: --- Attachment: YARN-9243.001.patch > Support limiting network outbound bandwidth for multiple interfaces > --- > > Key: YARN-9243 > URL: https://issues.apache.org/jira/browse/YARN-9243 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: kyungwan nam >Priority: Major > Attachments: YARN-9243.001.patch > > > YARN-3366 introduced limiting network outbound bandwidth. currently it is > available for one network interface. > but, we need to set for multiple interfaces in some circumstances. > It would be good if it can be set for multiple interfaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9243) Support limiting network outbound bandwidth for multiple interfaces
kyungwan nam created YARN-9243: -- Summary: Support limiting network outbound bandwidth for multiple interfaces Key: YARN-9243 URL: https://issues.apache.org/jira/browse/YARN-9243 Project: Hadoop YARN Issue Type: Improvement Reporter: kyungwan nam YARN-3366 introduced limiting network outbound bandwidth. currently it is available for one network interface. but, we need to set for multiple interfaces in some circumstances. It would be good if it can be set for multiple interfaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753719#comment-16753719 ] Akhil PB edited comment on YARN-7761 at 1/28/19 7:27 AM: - Attached a patch for branch-3.2. cc [~sunilg] was (Author: akhilpb): Attached a patch for branch-3.2 > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Fix For: 3.3.0 > > Attachments: YARN-7761-branch-3.2.001.patch, YARN-7761.001.patch, > YARN-7761.002.patch, YARN-7761.003.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9060) [YARN-8851] Phase 1 - Support device isolation and use the Nvidia GPU plugin as an example
[ https://issues.apache.org/jira/browse/YARN-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-9060: --- Summary: [YARN-8851] Phase 1 - Support device isolation and use the Nvidia GPU plugin as an example (was: [YARN-8851] Phase 1 - Support device isolation in native container-executor) > [YARN-8851] Phase 1 - Support device isolation and use the Nvidia GPU plugin > as an example > -- > > Key: YARN-9060 > URL: https://issues.apache.org/jira/browse/YARN-9060 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Zhankun Tang >Assignee: Zhankun Tang >Priority: Major > Attachments: YARN-9060-trunk.001.patch, YARN-9060-trunk.002.patch, > YARN-9060-trunk.003.patch, YARN-9060-trunk.004.patch, > YARN-9060-trunk.005.patch, YARN-9060-trunk.006.patch, > YARN-9060-trunk.007.patch, YARN-9060-trunk.008.patch, > YARN-9060-trunk.009.patch, YARN-9060-trunk.010.patch, > YARN-9060-trunk.011.patch, YARN-9060-trunk.012.patch > > > Due to the cgroups v1 implementation policy in linux kernel, we cannot update > the value of the device cgroups controller unless we have the root permission > ([here|https://github.com/torvalds/linux/blob/6f0d349d922ba44e4348a17a78ea51b7135965b1/security/device_cgroup.c#L604]). > So we need to support this in container-executor for Java layer to invoke. > This Jira will have three parts: > # native c-e module > # Java layer code to isolate devices for container (docker and non-docker) > # A sample Nvidia GPU plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9060) [YARN-8851] Phase 1 - Support device isolation in native container-executor
[ https://issues.apache.org/jira/browse/YARN-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated YARN-9060: --- Description: Due to the cgroups v1 implementation policy in linux kernel, we cannot update the value of the device cgroups controller unless we have the root permission ([here|https://github.com/torvalds/linux/blob/6f0d349d922ba44e4348a17a78ea51b7135965b1/security/device_cgroup.c#L604]). So we need to support this in container-executor for Java layer to invoke. This Jira will have three parts: # native c-e module # Java layer code to isolate devices for container (docker and non-docker) # A sample Nvidia GPU plugin was:Due to the cgroups v1 implementation policy in linux kernel, we cannot update the value of the device cgroups controller unless we have the root permission ([here|https://github.com/torvalds/linux/blob/6f0d349d922ba44e4348a17a78ea51b7135965b1/security/device_cgroup.c#L604]). So we need to support this in container-executor for Java layer to invoke. > [YARN-8851] Phase 1 - Support device isolation in native container-executor > --- > > Key: YARN-9060 > URL: https://issues.apache.org/jira/browse/YARN-9060 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Zhankun Tang >Assignee: Zhankun Tang >Priority: Major > Attachments: YARN-9060-trunk.001.patch, YARN-9060-trunk.002.patch, > YARN-9060-trunk.003.patch, YARN-9060-trunk.004.patch, > YARN-9060-trunk.005.patch, YARN-9060-trunk.006.patch, > YARN-9060-trunk.007.patch, YARN-9060-trunk.008.patch, > YARN-9060-trunk.009.patch, YARN-9060-trunk.010.patch, > YARN-9060-trunk.011.patch, YARN-9060-trunk.012.patch > > > Due to the cgroups v1 implementation policy in linux kernel, we cannot update > the value of the device cgroups controller unless we have the root permission > ([here|https://github.com/torvalds/linux/blob/6f0d349d922ba44e4348a17a78ea51b7135965b1/security/device_cgroup.c#L604]). > So we need to support this in container-executor for Java layer to invoke. > This Jira will have three parts: > # native c-e module > # Java layer code to isolate devices for container (docker and non-docker) > # A sample Nvidia GPU plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9242) Revert YARN-8270 from branch-3.1 and branch-3.1.2
[
https://issues.apache.org/jira/browse/YARN-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S updated YARN-9242:
Summary: Revert YARN-8270 from branch-3.1 and branch-3.1.2 (was: Revert
YARN-8270 from branch-3.1)
> Revert YARN-8270 from branch-3.1 and branch-3.1.2
> -
>
> Key: YARN-9242
> URL: https://issues.apache.org/jira/browse/YARN-9242
> Project: Hadoop YARN
> Issue Type: Task
>Reporter: Rohith Sharma K S
>Assignee: Rohith Sharma K S
>Priority: Blocker
>
> It is observed that in hadoop-3.1-RC0, NodeManager are unable to initialize
> TimelineCollectorWebService!
> Primary reason is HADOOP-15657 is not present in hadoop-3.1 branch!
> Following error is seen NM logs
> {noformat}
> Caused by: org.apache.hadoop.metrics2.MetricsException: Unsupported metric
> field putEntitiesFailureLatency of type
> org.apache.hadoop.metrics2.lib.MutableQuantiles
> at
> org.apache.hadoop.metrics2.lib.MutableMetricsFactory.newForField(MutableMetricsFactory.java:87)
> {noformat}
> We need to revert YARN-8270 from branch-3.1!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753719#comment-16753719 ] Akhil PB commented on YARN-7761: Attached a patch for branch-3.2 > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Fix For: 3.3.0 > > Attachments: YARN-7761-branch-3.2.001.patch, YARN-7761.001.patch, > YARN-7761.002.patch, YARN-7761.003.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link
[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-7761: --- Attachment: YARN-7761-branch-3.2.001.patch > [UI2] Clicking 'master container log' or 'Link' next to 'log' under > application's appAttempt goes to Old UI's Log link > -- > > Key: YARN-7761 > URL: https://issues.apache.org/jira/browse/YARN-7761 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sumana Sathish >Assignee: Akhil PB >Priority: Major > Fix For: 3.3.0 > > Attachments: YARN-7761-branch-3.2.001.patch, YARN-7761.001.patch, > YARN-7761.002.patch, YARN-7761.003.patch > > > Clicking 'master container log' or 'Link' next to 'Log' under application's > appAttempt goes to Old UI's Log link -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-9242) Revert YARN-8270 from branch-3.1
[
https://issues.apache.org/jira/browse/YARN-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S resolved YARN-9242.
-
Resolution: Done
I have reverted YARN-8270 in branch-3.1 and branch-3.1.2. Also updated Fix
Version in YARN-8270.
Closing as Done!
> Revert YARN-8270 from branch-3.1
>
>
> Key: YARN-9242
> URL: https://issues.apache.org/jira/browse/YARN-9242
> Project: Hadoop YARN
> Issue Type: Task
>Reporter: Rohith Sharma K S
>Assignee: Rohith Sharma K S
>Priority: Blocker
>
> It is observed that in hadoop-3.1-RC0, NodeManager are unable to initialize
> TimelineCollectorWebService!
> Primary reason is HADOOP-15657 is not present in hadoop-3.1 branch!
> Following error is seen NM logs
> {noformat}
> Caused by: org.apache.hadoop.metrics2.MetricsException: Unsupported metric
> field putEntitiesFailureLatency of type
> org.apache.hadoop.metrics2.lib.MutableQuantiles
> at
> org.apache.hadoop.metrics2.lib.MutableMetricsFactory.newForField(MutableMetricsFactory.java:87)
> {noformat}
> We need to revert YARN-8270 from branch-3.1!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8270) Adding JMX Metrics for Timeline Collector and Reader
[ https://issues.apache.org/jira/browse/YARN-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753714#comment-16753714 ] Rohith Sharma K S commented on YARN-8270: - In branch-3.1, this was causing error while publishing events from NodeManager. The reason is HADOOP-15657 was't present in branch-3.1. I have reverted this change for unblocking release 3.1.2. Updated the 'Fix Version'! > Adding JMX Metrics for Timeline Collector and Reader > > > Key: YARN-8270 > URL: https://issues.apache.org/jira/browse/YARN-8270 > Project: Hadoop YARN > Issue Type: Sub-task > Components: ATSv2, timelineserver >Reporter: Sushil Ks >Assignee: Sushil Ks >Priority: Major > Fix For: 3.2.0, 3.1.2 > > Attachments: YARN-8270.001.patch, YARN-8270.002.patch, > YARN-8270.003.patch, YARN-8270.004.patch, YARN-8270.005.patch > > > This Jira is for emitting JMX Metrics for ATS v2 Timeline Collector and > Timeline Reader, basically for Timeline Collector it tries to capture success > and failure latencies for *putEntities* and *putEntitiesAsync* from > *TimelineCollectorWebService* , similarly all the API's success and failure > latencies for fetching TimelineEntities from *TimelineReaderWebServices*. > This would actually help in monitoring and measuring performance for ATSv2 at > scale. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8270) Adding JMX Metrics for Timeline Collector and Reader
[ https://issues.apache.org/jira/browse/YARN-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8270: Fix Version/s: (was: 3.1.2) > Adding JMX Metrics for Timeline Collector and Reader > > > Key: YARN-8270 > URL: https://issues.apache.org/jira/browse/YARN-8270 > Project: Hadoop YARN > Issue Type: Sub-task > Components: ATSv2, timelineserver >Reporter: Sushil Ks >Assignee: Sushil Ks >Priority: Major > Fix For: 3.2.0 > > Attachments: YARN-8270.001.patch, YARN-8270.002.patch, > YARN-8270.003.patch, YARN-8270.004.patch, YARN-8270.005.patch > > > This Jira is for emitting JMX Metrics for ATS v2 Timeline Collector and > Timeline Reader, basically for Timeline Collector it tries to capture success > and failure latencies for *putEntities* and *putEntitiesAsync* from > *TimelineCollectorWebService* , similarly all the API's success and failure > latencies for fetching TimelineEntities from *TimelineReaderWebServices*. > This would actually help in monitoring and measuring performance for ATSv2 at > scale. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9242) Revert YARN-8270 from branch-3.1
[
https://issues.apache.org/jira/browse/YARN-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S updated YARN-9242:
Issue Type: Task (was: Bug)
> Revert YARN-8270 from branch-3.1
>
>
> Key: YARN-9242
> URL: https://issues.apache.org/jira/browse/YARN-9242
> Project: Hadoop YARN
> Issue Type: Task
>Reporter: Rohith Sharma K S
>Assignee: Rohith Sharma K S
>Priority: Blocker
>
> It is observed that in hadoop-3.1-RC0, NodeManager are unable to initialize
> TimelineCollectorWebService!
> Primary reason is HADOOP-15657 is not present in hadoop-3.1 branch!
> Following error is seen NM logs
> {noformat}
> Caused by: org.apache.hadoop.metrics2.MetricsException: Unsupported metric
> field putEntitiesFailureLatency of type
> org.apache.hadoop.metrics2.lib.MutableQuantiles
> at
> org.apache.hadoop.metrics2.lib.MutableMetricsFactory.newForField(MutableMetricsFactory.java:87)
> {noformat}
> We need to revert YARN-8270 from branch-3.1!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Moved] (YARN-9242) Revert YARN-8270 from branch-3.1
[
https://issues.apache.org/jira/browse/YARN-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S moved HADOOP-16078 to YARN-9242:
--
Target Version/s: 3.1.2 (was: 3.1.2)
Key: YARN-9242 (was: HADOOP-16078)
Project: Hadoop YARN (was: Hadoop Common)
> Revert YARN-8270 from branch-3.1
>
>
> Key: YARN-9242
> URL: https://issues.apache.org/jira/browse/YARN-9242
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Rohith Sharma K S
>Assignee: Rohith Sharma K S
>Priority: Blocker
>
> It is observed that in hadoop-3.1-RC0, NodeManager are unable to initialize
> TimelineCollectorWebService!
> Primary reason is HADOOP-15657 is not present in hadoop-3.1 branch!
> Following error is seen NM logs
> {noformat}
> Caused by: org.apache.hadoop.metrics2.MetricsException: Unsupported metric
> field putEntitiesFailureLatency of type
> org.apache.hadoop.metrics2.lib.MutableQuantiles
> at
> org.apache.hadoop.metrics2.lib.MutableMetricsFactory.newForField(MutableMetricsFactory.java:87)
> {noformat}
> We need to revert YARN-8270 from branch-3.1!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9231) TestDistributedShell fix timeout
[ https://issues.apache.org/jira/browse/YARN-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753700#comment-16753700 ] Sunil Govindan commented on YARN-9231: -- Thanks [~Prabhu Joseph] and [~yuan_zac] I think lets try with 2500 for now and see how jenkins is responding. Lets get this now. +1 > TestDistributedShell fix timeout > > > Key: YARN-9231 > URL: https://issues.apache.org/jira/browse/YARN-9231 > Project: Hadoop YARN > Issue Type: Bug > Components: distributed-shell >Affects Versions: 3.1.0 >Reporter: Prabhu Joseph >Assignee: Prabhu Joseph >Priority: Major > Attachments: 0001-YARN-9231.patch > > > TestDistributedShell test cases time out with - "There was a timeout or other > error in the fork" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9231) TestDistributedShell fix timeout
[ https://issues.apache.org/jira/browse/YARN-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753696#comment-16753696 ] Zac Zhou commented on YARN-9231: [~Prabhu Joseph] ， I run into the same problem. Thanks a lot for fixing it. LGTM, +1 But I'm not sure if 2500 seconds is ok. [~sunilg], any comments~ > TestDistributedShell fix timeout > > > Key: YARN-9231 > URL: https://issues.apache.org/jira/browse/YARN-9231 > Project: Hadoop YARN > Issue Type: Bug > Components: distributed-shell >Affects Versions: 3.1.0 >Reporter: Prabhu Joseph >Assignee: Prabhu Joseph >Priority: Major > Attachments: 0001-YARN-9231.patch > > > TestDistributedShell test cases time out with - "There was a timeout or other > error in the fork" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9161) Absolute resources of capacity scheduler doesn't support GPU and FPGA
[ https://issues.apache.org/jira/browse/YARN-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zac Zhou updated YARN-9161: --- Attachment: YARN-9161.008.patch > Absolute resources of capacity scheduler doesn't support GPU and FPGA > - > > Key: YARN-9161 > URL: https://issues.apache.org/jira/browse/YARN-9161 > Project: Hadoop YARN > Issue Type: Bug > Components: capacity scheduler >Reporter: Zac Zhou >Assignee: Zac Zhou >Priority: Major > Attachments: YARN-9161.001.patch, YARN-9161.002.patch, > YARN-9161.003.patch, YARN-9161.004.patch, YARN-9161.005.patch, > YARN-9161.006.patch, YARN-9161.007.patch, YARN-9161.008.patch > > > As the enum CapacitySchedulerConfiguration.AbsoluteResourceType only has two > elements: memory and vcores, which would filter out absolute resources > configuration of gpu and fpga in > AbstractCSQueue.updateConfigurableResourceRequirement. > This issue would cause gpu and fpga can't be allocated correctly -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5336) Limit the flow name size & consider cleanup for hex chars
[ https://issues.apache.org/jira/browse/YARN-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753677#comment-16753677 ] Sushil Ks commented on YARN-5336: - Hi [~vrushalic], Thanks for reviewing, I have updated the patch. Kindly review it. > Limit the flow name size & consider cleanup for hex chars > - > > Key: YARN-5336 > URL: https://issues.apache.org/jira/browse/YARN-5336 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Reporter: Vrushali C >Assignee: Sushil Ks >Priority: Major > Labels: YARN-5355 > Attachments: YARN-5336.001.patch, YARN-5336.002.patch, > YARN-5336.003.patch > > > As recommended by [~jrottinghuis] , need to add in some limit (default and > configurable) for accepting key values to be written to the backend. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9237) NM should ignore sending finished apps to RM during RM fail-over
[
https://issues.apache.org/jira/browse/YARN-9237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated YARN-9237:
--
Summary: NM should ignore sending finished apps to RM during RM fail-over
(was: Ignore sending finished apps to RM)
> NM should ignore sending finished apps to RM during RM fail-over
>
>
> Key: YARN-9237
> URL: https://issues.apache.org/jira/browse/YARN-9237
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
>Reporter: Jiandan Yang
>Assignee: Jiandan Yang
>Priority: Major
> Attachments: YARN-9237.001.patch, YARN-9237.002.patch
>
>
> I found a lot of following log in active RM log file after doing failover RM
> {code:java}
> 2019-01-24 15:43:58,999 WARN
> org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: Cannot get
> RMApp by appId=application_1542178952162_34746156, just added it to
> finishedApplications list for cleanup
> .
> {code}
> I looked forward RM logs and find this app had finished before hours
> {code:java}
> 2019-01-23 21:49:55,683 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl:
> appattempt_1542178952162_34746156_01 State change from FINAL_SAVING to
> FINISHING
> {code}
> The reason of RM prints " Cannot get RMApp by appId" is as follows:
> 1. RM failover
> 2. NM reports all running apps to RM in register request
> 3. The running apps are from NMContext, some apps may already finished
> 4. In my cluster, yarn.log-aggregation-enable=false,
> yarn.nodemanager.log.retain-seconds=86400(1day), so app is kept in NMContext
> before app has finished for 24 hours
> 5. My Yarn cluster runs 50k apps per day and 7k nodes, and NM will report
> many finished apps to RM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9237) Ignore sending finished apps to RM
[
https://issues.apache.org/jira/browse/YARN-9237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated YARN-9237:
--
Summary: Ignore sending finished apps to RM (was: RM prints a lot of
"Cannot get RMApp by appId" log when RM failover)
> Ignore sending finished apps to RM
> --
>
> Key: YARN-9237
> URL: https://issues.apache.org/jira/browse/YARN-9237
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
>Reporter: Jiandan Yang
>Assignee: Jiandan Yang
>Priority: Major
> Attachments: YARN-9237.001.patch, YARN-9237.002.patch
>
>
> I found a lot of following log in active RM log file after doing failover RM
> {code:java}
> 2019-01-24 15:43:58,999 WARN
> org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: Cannot get
> RMApp by appId=application_1542178952162_34746156, just added it to
> finishedApplications list for cleanup
> .
> {code}
> I looked forward RM logs and find this app had finished before hours
> {code:java}
> 2019-01-23 21:49:55,683 INFO
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl:
> appattempt_1542178952162_34746156_01 State change from FINAL_SAVING to
> FINISHING
> {code}
> The reason of RM prints " Cannot get RMApp by appId" is as follows:
> 1. RM failover
> 2. NM reports all running apps to RM in register request
> 3. The running apps are from NMContext, some apps may already finished
> 4. In my cluster, yarn.log-aggregation-enable=false,
> yarn.nodemanager.log.retain-seconds=86400(1day), so app is kept in NMContext
> before app has finished for 24 hours
> 5. My Yarn cluster runs 50k apps per day and 7k nodes, and NM will report
> many finished apps to RM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9191) Add cli option in DS to support enforceExecutionType in resource requests.
[
https://issues.apache.org/jira/browse/YARN-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753584#comment-16753584
]
Hadoop QA commented on YARN-9191:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m
19s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 8m
18s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
34s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
3s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
15m 36s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
40s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
50s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
13s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 7m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 7m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
14m 23s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
1s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 16m 20s{color}
| {color:red} hadoop-yarn-applications-distributedshell in the patch failed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
22s{color} | {color:green} hadoop-yarn-site in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
37s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 93m 31s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f |
| JIRA Issue | YARN-9191 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12956511/YARN-9191.004.patch |
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux 5e01df466bba 4.4.0-138-generic #164~14.04.1-Ubuntu SMP Fri Oct
5 08:56:16 UTC
[jira] [Updated] (YARN-9191) Add cli option in DS to support enforceExecutionType in resource requests.
[ https://issues.apache.org/jira/browse/YARN-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Modi updated YARN-9191: Attachment: YARN-9191.004.patch > Add cli option in DS to support enforceExecutionType in resource requests. > -- > > Key: YARN-9191 > URL: https://issues.apache.org/jira/browse/YARN-9191 > Project: Hadoop YARN > Issue Type: Task >Reporter: Abhishek Modi >Assignee: Abhishek Modi >Priority: Major > Attachments: YARN-9191.001.patch, YARN-9191.002.patch, > YARN-9191.003.patch, YARN-9191.004.patch > > > This JIRA proposes to expose cli option to allow users to additionally > specify the value enforceExecutionType flag (introduced in YARN-5180). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9241) Remove Scheduler specific if/else block and make it injectable in RMController
[ https://issues.apache.org/jira/browse/YARN-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anuj updated YARN-9241: --- Description: RmController contains a hardcoded if and else block for type of scheduler and decides which page to use for which scheduler. [https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RmController.java|http://example.com/] This if else block makes it hard to introduce a new scheduler and corresponding webpage without modifying the existing RMController class. It would be great if we make it extendable. was: RmController contains a hardcoded if and else block for type of scheduler and decides which page to use for which scheduler. [https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RmController.java|http://example.com] This if else block makes it hard to introduce a new scheduler and corresponding webpage with modifying the existing RMController class. It would be great if we make it extendable. > Remove Scheduler specific if/else block and make it injectable in RMController > -- > > Key: YARN-9241 > URL: https://issues.apache.org/jira/browse/YARN-9241 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 3.2.0 >Reporter: Anuj >Priority: Minor > > RmController contains a hardcoded if and else block for type of scheduler and > decides which page to use for which scheduler. > [https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RmController.java|http://example.com/] > This if else block makes it hard to introduce a new scheduler and > corresponding webpage without modifying the existing RMController class. > It would be great if we make it extendable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9241) Remove Scheduler specific if/else block and make it injectable in RMController
[ https://issues.apache.org/jira/browse/YARN-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anuj updated YARN-9241: --- Description: RmController contains a hardcoded if and else block for type of scheduler and decides which page to use for which scheduler. [https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RmController.java|http://example.com] This if else block makes it hard to introduce a new scheduler and corresponding webpage with modifying the existing RMController class. It would be great if we make it extendable. was: RmController contains a hardcoded if and else block for type of scheduler and decides which page to use for which scheduler. This if else block makes it hard to introduce a new scheduler and corresponding webpage with modifying the existing RMController class. It would be great if we make it extendable. > Remove Scheduler specific if/else block and make it injectable in RMController > -- > > Key: YARN-9241 > URL: https://issues.apache.org/jira/browse/YARN-9241 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 3.2.0 >Reporter: Anuj >Priority: Minor > > RmController contains a hardcoded if and else block for type of scheduler and > decides which page to use for which scheduler. > [https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RmController.java|http://example.com] > This if else block makes it hard to introduce a new scheduler and > corresponding webpage with modifying the existing RMController class. > It would be great if we make it extendable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9241) Remove Scheduler specific if/else block and make it injectable in RMController
[ https://issues.apache.org/jira/browse/YARN-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anuj updated YARN-9241: --- Summary: Remove Scheduler specific if/else block and make it injectable in RMController (was: Remove if else block from RmController.java) > Remove Scheduler specific if/else block and make it injectable in RMController > -- > > Key: YARN-9241 > URL: https://issues.apache.org/jira/browse/YARN-9241 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 3.2.0 >Reporter: Anuj >Priority: Minor > > RmController contains a hardcoded if and else block for type of scheduler and > decides which page to use for which scheduler. > This if else block makes it hard to introduce a new scheduler and > corresponding webpage with modifying the existing RMController class. > It would be great if we make it extendable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9241) Remove Scheduler specific if/else block and make it injectable in RMController
[ https://issues.apache.org/jira/browse/YARN-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753497#comment-16753497 ] Anuj commented on YARN-9241: Updated. > Remove Scheduler specific if/else block and make it injectable in RMController > -- > > Key: YARN-9241 > URL: https://issues.apache.org/jira/browse/YARN-9241 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 3.2.0 >Reporter: Anuj >Priority: Minor > > RmController contains a hardcoded if and else block for type of scheduler and > decides which page to use for which scheduler. > This if else block makes it hard to introduce a new scheduler and > corresponding webpage with modifying the existing RMController class. > It would be great if we make it extendable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Moved] (YARN-9241) Remove if else block from RmController.java
[ https://issues.apache.org/jira/browse/YARN-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran moved HADOOP-16070 to YARN-9241: --- Affects Version/s: (was: 3.1.1) (was: 3.0.1) 3.2.0 Component/s: (was: common) resourcemanager Key: YARN-9241 (was: HADOOP-16070) Project: Hadoop YARN (was: Hadoop Common) > Remove if else block from RmController.java > --- > > Key: YARN-9241 > URL: https://issues.apache.org/jira/browse/YARN-9241 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 3.2.0 >Reporter: Anuj >Priority: Minor > > RmController contains a hardcoded if and else block for type of scheduler and > decides which page to use for which scheduler. > This if else block makes it hard to introduce a new scheduler and > corresponding webpage with modifying the existing RMController class. > It would be great if we make it extendable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9241) Remove if else block from RmController.java
[ https://issues.apache.org/jira/browse/YARN-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753481#comment-16753481 ] Steve Loughran commented on YARN-9241: -- Moved to YARN project; recommend changing title to be more specific > Remove if else block from RmController.java > --- > > Key: YARN-9241 > URL: https://issues.apache.org/jira/browse/YARN-9241 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 3.2.0 >Reporter: Anuj >Priority: Minor > > RmController contains a hardcoded if and else block for type of scheduler and > decides which page to use for which scheduler. > This if else block makes it hard to introduce a new scheduler and > corresponding webpage with modifying the existing RMController class. > It would be great if we make it extendable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9191) Add cli option in DS to support enforceExecutionType in resource requests.
[
https://issues.apache.org/jira/browse/YARN-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753456#comment-16753456
]
Hadoop QA commented on YARN-9191:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
44s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
6s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 26m
37s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 12m
4s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
44s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
6s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
17m 3s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
55s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
4s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
16s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 12m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 12m
36s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
1m 43s{color} | {color:orange} hadoop-yarn-project/hadoop-yarn: The patch
generated 1 new + 205 unchanged - 0 fixed = 206 total (was 205) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
14m 54s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
1s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 16m 23s{color}
| {color:red} hadoop-yarn-applications-distributedshell in the patch failed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
25s{color} | {color:green} hadoop-yarn-site in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
49s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}113m 12s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f |
| JIRA Issue | YARN-9191 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12956498/YARN-9191.003.patch |
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
[jira] [Commented] (YARN-7976) [atsv2 read acls] REST API to list domain/domains
[
https://issues.apache.org/jira/browse/YARN-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753398#comment-16753398
]
Abhishek Modi commented on YARN-7976:
-
Checkstyle warnings are due to number of params and nothing much can be done.
> [atsv2 read acls] REST API to list domain/domains
> -
>
> Key: YARN-7976
> URL: https://issues.apache.org/jira/browse/YARN-7976
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelinereader
>Reporter: Rohith Sharma K S
>Assignee: Abhishek Modi
>Priority: Major
> Attachments: YARN-7976.001.patch, YARN-7976.002.patch
>
>
> Provide REST API to list domains and domain in TimelineReaderWebService.
> /domains and /domain/\{domainId}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9191) Add cli option in DS to support enforceExecutionType in resource requests.
[ https://issues.apache.org/jira/browse/YARN-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Modi updated YARN-9191: Attachment: YARN-9191.003.patch > Add cli option in DS to support enforceExecutionType in resource requests. > -- > > Key: YARN-9191 > URL: https://issues.apache.org/jira/browse/YARN-9191 > Project: Hadoop YARN > Issue Type: Task >Reporter: Abhishek Modi >Assignee: Abhishek Modi >Priority: Major > Attachments: YARN-9191.001.patch, YARN-9191.002.patch, > YARN-9191.003.patch > > > This JIRA proposes to expose cli option to allow users to additionally > specify the value enforceExecutionType flag (introduced in YARN-5180). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7976) [atsv2 read acls] REST API to list domain/domains
[
https://issues.apache.org/jira/browse/YARN-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753380#comment-16753380
]
Hadoop QA commented on YARN-7976:
-
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
18s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 3 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
30s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 19m
12s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
33s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
55s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
50s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
13m 31s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase-tests
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
34s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
8s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
12s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
31s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 49s{color} | {color:orange}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server: The patch generated 2 new +
41 unchanged - 0 fixed = 43 total (was 41) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 4s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase-tests
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m
12s{color} | {color:green} hadoop-yarn-server-timelineservice in the patch
passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
27s{color} | {color:green} hadoop-yarn-server-timelineservice-hbase-common in
the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
22s{color} | {color:green} hadoop-yarn-server-timelineservice-hbase-client in
the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 10m
53s{color} | {color:green} hadoop-yarn-server-timelineservice-hbase-tests in
the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
29s{color} | {color:green} The patch does not
[jira] [Updated] (YARN-7976) [atsv2 read acls] REST API to list domain/domains
[
https://issues.apache.org/jira/browse/YARN-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Modi updated YARN-7976:
Attachment: YARN-7976.002.patch
> [atsv2 read acls] REST API to list domain/domains
> -
>
> Key: YARN-7976
> URL: https://issues.apache.org/jira/browse/YARN-7976
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelinereader
>Reporter: Rohith Sharma K S
>Assignee: Abhishek Modi
>Priority: Major
> Attachments: YARN-7976.001.patch, YARN-7976.002.patch
>
>
> Provide REST API to list domains and domain in TimelineReaderWebService.
> /domains and /domain/\{domainId}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
