[jira] [Commented] (YARN-9337) GPU auto-discovery script runs even when the resource is given by hand
[
https://issues.apache.org/jira/browse/YARN-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884135#comment-16884135
]
Chen Liang commented on YARN-9337:
--
I am getting the following compilation error on branch-3.1, which seems related
to this change:
{code:java}
TestGpuDiscoverer.java:[508,31] incompatible types: inferred type does not
conform to upper bound(s)
inferred:
java.lang.Class
upper bound(s):
org.apache.hadoop.yarn.server.nodemanager.containermanager.resourceplugin.gpu.GpuDiscoverer,java.lang.Object{code}
I do not have this error on trunk though. I think this is related to mockito
version differences. Can someone verify please?
> GPU auto-discovery script runs even when the resource is given by hand
> --
>
> Key: YARN-9337
> URL: https://issues.apache.org/jira/browse/YARN-9337
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn
>Affects Versions: 3.2.0
>Reporter: Adam Antal
>Assignee: Adam Antal
>Priority: Major
> Fix For: 3.3.0, 3.2.1, 3.1.3
>
> Attachments: YARN-9337.001.patch, YARN-9337.002.patch,
> YARN-9337.003.patch, YARN-9337.003.patch, YARN-9337.branch-3.1.001.patch,
> YARN-9337.branch-3.2.001.patch
>
>
> The nvidia-smi script is called even when the gpu configs are given by hand
> (so there's no need for GPU auto-discovery).
> We should mitigate the call of that script, since it has no effect. (The
> configs written by the user is not overwritten by the result of the
> auto-discovery script.)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7895) Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
[
https://issues.apache.org/jira/browse/YARN-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352720#comment-16352720
]
Chen Liang commented on YARN-7895:
--
Posting a patch (not able to assign the JIRA though). [~jianhe] could you
please take a look?
> Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
> ---
>
> Key: YARN-7895
> URL: https://issues.apache.org/jira/browse/YARN-7895
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Chen Liang
>Priority: Minor
> Attachments: YARN-7895-branch-2.7.patch
>
>
> We are hitting a consistently failing test
> {{testAMContainerAllocationWhenDNSUnavailable}} in
> {{TestContainerAllocation}} in our internal branch-2.7. Tested YARN-3564
> locally, which looks to be fixing this test. Filing this jira to backport
> YARN-3564 to branch-2.7.
--
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-7895) Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
[
https://issues.apache.org/jira/browse/YARN-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Liang updated YARN-7895:
-
Attachment: (was: YARN-7895-branch-2.7.diff)
> Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
> ---
>
> Key: YARN-7895
> URL: https://issues.apache.org/jira/browse/YARN-7895
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Chen Liang
>Priority: Minor
> Attachments: YARN-7895-branch-2.7.patch
>
>
> We are hitting a consistently failing test
> {{testAMContainerAllocationWhenDNSUnavailable}} in
> {{TestContainerAllocation}} in our internal branch-2.7. Tested YARN-3564
> locally, which looks to be fixing this test. Filing this jira to backport
> YARN-3564 to branch-2.7.
--
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-7895) Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
[
https://issues.apache.org/jira/browse/YARN-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Liang updated YARN-7895:
-
Attachment: YARN-7895-branch-2.7.patch
> Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
> ---
>
> Key: YARN-7895
> URL: https://issues.apache.org/jira/browse/YARN-7895
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Chen Liang
>Priority: Minor
> Attachments: YARN-7895-branch-2.7.patch
>
>
> We are hitting a consistently failing test
> {{testAMContainerAllocationWhenDNSUnavailable}} in
> {{TestContainerAllocation}} in our internal branch-2.7. Tested YARN-3564
> locally, which looks to be fixing this test. Filing this jira to backport
> YARN-3564 to branch-2.7.
--
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-7895) Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
[
https://issues.apache.org/jira/browse/YARN-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Liang updated YARN-7895:
-
Description: We are hitting a consistently failing test
{{testAMContainerAllocationWhenDNSUnavailable}} in {{TestContainerAllocation}}
in our internal branch-2.7. Tested YARN-3564 locally, which looks to be fixing
this test. Filing this jira to backport YARN-3564 to branch-2.7. (was: We are
hitting a consistently failing test
{{testAMContainerAllocationWhenDNSUnavailable}} in {{TestContainerAllocation}}
on our branch-2.7. Tested YARN-3564 locally, which looks to be fixing this
test. Filing this jira to backport to branch-2.7.)
> Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
> ---
>
> Key: YARN-7895
> URL: https://issues.apache.org/jira/browse/YARN-7895
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Chen Liang
>Priority: Minor
> Attachments: YARN-7895-branch-2.7.diff
>
>
> We are hitting a consistently failing test
> {{testAMContainerAllocationWhenDNSUnavailable}} in
> {{TestContainerAllocation}} in our internal branch-2.7. Tested YARN-3564
> locally, which looks to be fixing this test. Filing this jira to backport
> YARN-3564 to branch-2.7.
--
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-7895) Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
[
https://issues.apache.org/jira/browse/YARN-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Liang updated YARN-7895:
-
Attachment: YARN-7895-branch-2.7.diff
> Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
> ---
>
> Key: YARN-7895
> URL: https://issues.apache.org/jira/browse/YARN-7895
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Chen Liang
>Priority: Minor
> Attachments: YARN-7895-branch-2.7.diff
>
>
> We are hitting a consistently failing test
> {{testAMContainerAllocationWhenDNSUnavailable}} in
> {{TestContainerAllocation}} on our branch-2.7. Tested YARN-3564 locally,
> which looks to be fixing this test. Filing this jira to backport to
> branch-2.7.
--
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-7895) Backport YARN-3564 to branch-2.7 to fix TestContainerAllocation
Chen Liang created YARN-7895:
Summary: Backport YARN-3564 to branch-2.7 to fix
TestContainerAllocation
Key: YARN-7895
URL: https://issues.apache.org/jira/browse/YARN-7895
Project: Hadoop YARN
Issue Type: Bug
Components: test
Reporter: Chen Liang
We are hitting a consistently failing test
{{testAMContainerAllocationWhenDNSUnavailable}} in {{TestContainerAllocation}}
on our branch-2.7. Tested YARN-3564 locally, which looks to be fixing this
test. Filing this jira to backport to branch-2.7.
--
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
