[jira] [Updated] (YARN-11231) FSDownload set wrong permission in destinationTmp
[ https://issues.apache.org/jira/browse/YARN-11231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-11231: -- Labels: pull-request-available (was: ) > FSDownload set wrong permission in destinationTmp > - > > Key: YARN-11231 > URL: https://issues.apache.org/jira/browse/YARN-11231 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Zhang Dongsheng >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > FSDownload calls createDir in the call method to create the destinationTmp > directory, which is later used as the parent directory to create the > directory dFinal, which is used in doAs to perform operations such as path > creation and path traversal. doAs cannot determine the user's identity, so > there is a problem with setting 755 permissions for destinationTmp here, I > think it should be set to 777 permissions here. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11231) FSDownload set wrong permission in destinationTmp
[ https://issues.apache.org/jira/browse/YARN-11231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhang Dongsheng updated YARN-11231: --- Component/s: yarn Description: FSDownload calls createDir in the call method to create the destinationTmp directory, which is later used as the parent directory to create the directory dFinal, which is used in doAs to perform operations such as path creation and path traversal. doAs cannot determine the user's identity, so there is a problem with setting 755 permissions for destinationTmp here, I think it should be set to 777 permissions here. > FSDownload set wrong permission in destinationTmp > - > > Key: YARN-11231 > URL: https://issues.apache.org/jira/browse/YARN-11231 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Reporter: Zhang Dongsheng >Priority: Major > > FSDownload calls createDir in the call method to create the destinationTmp > directory, which is later used as the parent directory to create the > directory dFinal, which is used in doAs to perform operations such as path > creation and path traversal. doAs cannot determine the user's identity, so > there is a problem with setting 755 permissions for destinationTmp here, I > think it should be set to 777 permissions here. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-11210) Fix YARN RMAdminCLI retry logic for non-retryable kerberos configuration exception
[
https://issues.apache.org/jira/browse/YARN-11210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka reassigned YARN-11210:
Assignee: Kevin Wikant
> Fix YARN RMAdminCLI retry logic for non-retryable kerberos configuration
> exception
> --
>
> Key: YARN-11210
> URL: https://issues.apache.org/jira/browse/YARN-11210
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
>Reporter: Kevin Wikant
>Assignee: Kevin Wikant
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> h2. Description of Problem
> Applications which call YARN RMAdminCLI (i.e. YARN ResourceManager client)
> synchronously can be blocked for up to 15 minutes with the default
> configuration of "yarn.resourcemanager.connect.max-wait.ms"; this is not an
> issue in of itself, but there is a non-retryable IllegalArgumentException
> exception thrown within the YARN ResourceManager client that is getting
> swallowed & treated as a retryable "connection exception" meaning that it
> gets retried for 15 minutes.
> The purpose of this JIRA (and PR) is to modify the YARN client so that it
> does not retry on this non-retryable exception.
> h2. Background Information
> YARN ResourceManager client treats connection exceptions as retryable & with
> the default value of "yarn.resourcemanager.connect.max-wait.ms" will attempt
> to connect to the ResourceManager for up to 15 minutes when facing
> "connection exceptions". This arguably makes sense because connection
> exceptions are in some cases transient & can be recovered from without any
> action needed from the client. See example below where YARN ResourceManager
> client was able to recover from connection issues that resulted from the
> ResourceManager process being down.
> {quote}> yarn rmadmin -refreshNodes
> 22/06/28 14:40:17 INFO client.RMProxy: Connecting to ResourceManager at
> /0.0.0.0:8033
> 22/06/28 14:40:18 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:19 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:20 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 2 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ...
> 22/06/28 14:40:27 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 9 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:28 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:29 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ...
> 22/06/28 14:40:37 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 9 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:37 INFO retry.RetryInvocationHandler:
> java.net.ConnectException: Your endpoint configuration is wrong; For more
> details see: [http://wiki.apache.org/hadoop/UnsetHostnameOrPort], while
> invoking ResourceManagerAdministrationProtocolPBClientImpl.refreshNodes over
> null after 1 failover attempts. Trying to failover after sleeping for 41061ms.
> 22/06/28 14:41:19 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:41:20 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ...
> 22/06/28 14:41:28 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 9 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:41:28 INFO retry.RetryInvocationHandler:
> java.net.ConnectException: Your endpoint configuration is wrong; For more
> details see: [http://wiki.apache.org/hadoop/UnsetHostnameOrPort], while
> invoking ResourceManagerAdministrationProtoco
[jira] [Commented] (YARN-11210) Fix YARN RMAdminCLI retry logic for non-retryable kerberos configuration exception
[
https://issues.apache.org/jira/browse/YARN-11210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571183#comment-17571183
]
Akira Ajisaka commented on YARN-11210:
--
[~prabhujoseph] Yes. Done.
I think all the Hadoop committers have the privilege to make someone to
contributor. You can go to
https://issues.apache.org/jira/plugins/servlet/project-config/YARN/roles and
add Kevin as contributor.
> Fix YARN RMAdminCLI retry logic for non-retryable kerberos configuration
> exception
> --
>
> Key: YARN-11210
> URL: https://issues.apache.org/jira/browse/YARN-11210
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
>Reporter: Kevin Wikant
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> h2. Description of Problem
> Applications which call YARN RMAdminCLI (i.e. YARN ResourceManager client)
> synchronously can be blocked for up to 15 minutes with the default
> configuration of "yarn.resourcemanager.connect.max-wait.ms"; this is not an
> issue in of itself, but there is a non-retryable IllegalArgumentException
> exception thrown within the YARN ResourceManager client that is getting
> swallowed & treated as a retryable "connection exception" meaning that it
> gets retried for 15 minutes.
> The purpose of this JIRA (and PR) is to modify the YARN client so that it
> does not retry on this non-retryable exception.
> h2. Background Information
> YARN ResourceManager client treats connection exceptions as retryable & with
> the default value of "yarn.resourcemanager.connect.max-wait.ms" will attempt
> to connect to the ResourceManager for up to 15 minutes when facing
> "connection exceptions". This arguably makes sense because connection
> exceptions are in some cases transient & can be recovered from without any
> action needed from the client. See example below where YARN ResourceManager
> client was able to recover from connection issues that resulted from the
> ResourceManager process being down.
> {quote}> yarn rmadmin -refreshNodes
> 22/06/28 14:40:17 INFO client.RMProxy: Connecting to ResourceManager at
> /0.0.0.0:8033
> 22/06/28 14:40:18 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:19 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:20 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 2 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ...
> 22/06/28 14:40:27 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 9 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:28 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:29 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ...
> 22/06/28 14:40:37 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 9 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:37 INFO retry.RetryInvocationHandler:
> java.net.ConnectException: Your endpoint configuration is wrong; For more
> details see: [http://wiki.apache.org/hadoop/UnsetHostnameOrPort], while
> invoking ResourceManagerAdministrationProtocolPBClientImpl.refreshNodes over
> null after 1 failover attempts. Trying to failover after sleeping for 41061ms.
> 22/06/28 14:41:19 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:41:20 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ...
> 22/06/28 14:41:28 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 9 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:41:28 INFO retry.Retr
[jira] [Created] (YARN-11231) FSDownload set wrong permission in destinationTmp
Zhang Dongsheng created YARN-11231: -- Summary: FSDownload set wrong permission in destinationTmp Key: YARN-11231 URL: https://issues.apache.org/jira/browse/YARN-11231 Project: Hadoop YARN Issue Type: Bug Reporter: Zhang Dongsheng -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-11210) Fix YARN RMAdminCLI retry logic for non-retryable kerberos configuration exception
[
https://issues.apache.org/jira/browse/YARN-11210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571182#comment-17571182
]
Prabhu Joseph commented on YARN-11210:
--
[~aajisaka] Could you make [~KevinWikant] as contributor to YARN.
> Fix YARN RMAdminCLI retry logic for non-retryable kerberos configuration
> exception
> --
>
> Key: YARN-11210
> URL: https://issues.apache.org/jira/browse/YARN-11210
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
>Reporter: Kevin Wikant
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> h2. Description of Problem
> Applications which call YARN RMAdminCLI (i.e. YARN ResourceManager client)
> synchronously can be blocked for up to 15 minutes with the default
> configuration of "yarn.resourcemanager.connect.max-wait.ms"; this is not an
> issue in of itself, but there is a non-retryable IllegalArgumentException
> exception thrown within the YARN ResourceManager client that is getting
> swallowed & treated as a retryable "connection exception" meaning that it
> gets retried for 15 minutes.
> The purpose of this JIRA (and PR) is to modify the YARN client so that it
> does not retry on this non-retryable exception.
> h2. Background Information
> YARN ResourceManager client treats connection exceptions as retryable & with
> the default value of "yarn.resourcemanager.connect.max-wait.ms" will attempt
> to connect to the ResourceManager for up to 15 minutes when facing
> "connection exceptions". This arguably makes sense because connection
> exceptions are in some cases transient & can be recovered from without any
> action needed from the client. See example below where YARN ResourceManager
> client was able to recover from connection issues that resulted from the
> ResourceManager process being down.
> {quote}> yarn rmadmin -refreshNodes
> 22/06/28 14:40:17 INFO client.RMProxy: Connecting to ResourceManager at
> /0.0.0.0:8033
> 22/06/28 14:40:18 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:19 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:20 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 2 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ...
> 22/06/28 14:40:27 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 9 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:28 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:29 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ...
> 22/06/28 14:40:37 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 9 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:40:37 INFO retry.RetryInvocationHandler:
> java.net.ConnectException: Your endpoint configuration is wrong; For more
> details see: [http://wiki.apache.org/hadoop/UnsetHostnameOrPort], while
> invoking ResourceManagerAdministrationProtocolPBClientImpl.refreshNodes over
> null after 1 failover attempts. Trying to failover after sleeping for 41061ms.
> 22/06/28 14:41:19 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:41:20 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ...
> 22/06/28 14:41:28 INFO ipc.Client: Retrying connect to server:
> 0.0.0.0/0.0.0.0:8033. Already tried 9 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 22/06/28 14:41:28 INFO retry.RetryInvocationHandler:
> java.net.ConnectException: Your endpoint configuration is wrong; For more
> details see: [http://wiki.apache.org/hadoop/UnsetHostnameOrPort],
[jira] [Commented] (YARN-11161) Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes API's for Federation
[ https://issues.apache.org/jira/browse/YARN-11161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571129#comment-17571129 ] fanshilun commented on YARN-11161: -- [~elgoiri] Thank you very much for helping to review the code! > Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes > API's for Federation > - > > Key: YARN-11161 > URL: https://issues.apache.org/jira/browse/YARN-11161 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes > API's for Federation. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-10883) [Router] Router Audit Log Add Client IP Address.
[
https://issues.apache.org/jira/browse/YARN-10883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Íñigo Goiri resolved YARN-10883.
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
> [Router] Router Audit Log Add Client IP Address.
>
>
> Key: YARN-10883
> URL: https://issues.apache.org/jira/browse/YARN-10883
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: chaosju
>Assignee: fanshilun
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> the Router should record the client address which killed the application
> Now the log information is printed as follows:
> {code:java}
> 2022-06-10 08:06:26,322 INFO [main] router.RouterAuditLogger
> (RouterAuditLogger.java:logSuccess(89)) - USER=test-user OPERATION=Submit
> New App TARGET=RouterClientRMService RESULT=SUCCESS
> APPID=application_1654873569440_0001 SUBCLUSTERID=2{code}
> The log of adding IP information is as follows:
> {code:java}
> 2022-06-10 08:09:05,392 INFO [main] router.RouterAuditLogger
> (RouterAuditLogger.java:logSuccess(89)) - USER=test-user IP=127.0.0.1
> OPERATION=Submit New App TARGET=RouterClientRMService RESULT=SUCCESS
> APPID=application_1654873732359_0001 SUBCLUSTERID=3 {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10883) [Router] Router Audit Log Add Client IP Address.
[
https://issues.apache.org/jira/browse/YARN-10883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571053#comment-17571053
]
Íñigo Goiri commented on YARN-10883:
Thank you all for the push and thanks [~slfan1989] for the PR and [~ayushtkn]
for the review.
Merged PR 4426 into trunk.
> [Router] Router Audit Log Add Client IP Address.
>
>
> Key: YARN-10883
> URL: https://issues.apache.org/jira/browse/YARN-10883
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: chaosju
>Assignee: fanshilun
>Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> the Router should record the client address which killed the application
> Now the log information is printed as follows:
> {code:java}
> 2022-06-10 08:06:26,322 INFO [main] router.RouterAuditLogger
> (RouterAuditLogger.java:logSuccess(89)) - USER=test-user OPERATION=Submit
> New App TARGET=RouterClientRMService RESULT=SUCCESS
> APPID=application_1654873569440_0001 SUBCLUSTERID=2{code}
> The log of adding IP information is as follows:
> {code:java}
> 2022-06-10 08:09:05,392 INFO [main] router.RouterAuditLogger
> (RouterAuditLogger.java:logSuccess(89)) - USER=test-user IP=127.0.0.1
> OPERATION=Submit New App TARGET=RouterClientRMService RESULT=SUCCESS
> APPID=application_1654873732359_0001 SUBCLUSTERID=3 {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11161) Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes API's for Federation
[ https://issues.apache.org/jira/browse/YARN-11161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Íñigo Goiri updated YARN-11161: --- Description: Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes API's for Federation. > Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes > API's for Federation > - > > Key: YARN-11161 > URL: https://issues.apache.org/jira/browse/YARN-11161 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > Labels: pull-request-available > Time Spent: 3h 40m > Remaining Estimate: 0h > > Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes > API's for Federation. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-11161) Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes API's for Federation
[ https://issues.apache.org/jira/browse/YARN-11161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571006#comment-17571006 ] Íñigo Goiri commented on YARN-11161: Thanks [~slfan1989] for the PR. Merged PR 4610 into trunk. > Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes > API's for Federation > - > > Key: YARN-11161 > URL: https://issues.apache.org/jira/browse/YARN-11161 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes > API's for Federation. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-11161) Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes API's for Federation
[ https://issues.apache.org/jira/browse/YARN-11161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Íñigo Goiri resolved YARN-11161. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed > Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes > API's for Federation > - > > Key: YARN-11161 > URL: https://issues.apache.org/jira/browse/YARN-11161 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > Support getAttributesToNodes, getClusterNodeAttributes, getNodesToAttributes > API's for Federation. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11230) [Federation] Add getContainer,signalToContainer REST APIs for Router
fanshilun created YARN-11230: Summary: [Federation] Add getContainer,signalToContainer REST APIs for Router Key: YARN-11230 URL: https://issues.apache.org/jira/browse/YARN-11230 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun Assignee: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11229) [Federation] Add checkUserAccessToQueue REST APIs for Router
fanshilun created YARN-11229: Summary: [Federation] Add checkUserAccessToQueue REST APIs for Router Key: YARN-11229 URL: https://issues.apache.org/jira/browse/YARN-11229 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun Assignee: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11228) [Federation] Add getAppAttempts, getAppAttempt REST APIs for Router
fanshilun created YARN-11228: Summary: [Federation] Add getAppAttempts, getAppAttempt REST APIs for Router Key: YARN-11228 URL: https://issues.apache.org/jira/browse/YARN-11228 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun Assignee: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11227) [Federation] Add getAppTimeout, getAppTimeouts, updateApplicationTimeout REST APIs for Router
fanshilun created YARN-11227: Summary: [Federation] Add getAppTimeout, getAppTimeouts, updateApplicationTimeout REST APIs for Router Key: YARN-11227 URL: https://issues.apache.org/jira/browse/YARN-11227 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun Assignee: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-11226) [Federation] Add createNewReservation, submitReservation, updateReservation, deleteReservation, listReservation REST APIs for Router
[ https://issues.apache.org/jira/browse/YARN-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fanshilun reassigned YARN-11226: Assignee: fanshilun > [Federation] Add createNewReservation, submitReservation, updateReservation, > deleteReservation, listReservation REST APIs for Router > > > Key: YARN-11226 > URL: https://issues.apache.org/jira/browse/YARN-11226 > Project: Hadoop YARN > Issue Type: Sub-task > Components: federation >Affects Versions: 3.4.0, 3.3.4 >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11226) [Federation] Add createNewReservation, submitReservation, updateReservation, deleteReservation, listReservation REST APIs for Router
fanshilun created YARN-11226: Summary: [Federation] Add createNewReservation, submitReservation, updateReservation, deleteReservation, listReservation REST APIs for Router Key: YARN-11226 URL: https://issues.apache.org/jira/browse/YARN-11226 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-11225) [Federation] Add postDelegationToken, postDelegationTokenExpiration, cancelDelegationToken REST APIs for Router
[ https://issues.apache.org/jira/browse/YARN-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fanshilun reassigned YARN-11225: Assignee: fanshilun > [Federation] Add postDelegationToken, postDelegationTokenExpiration, > cancelDelegationToken REST APIs for Router > > > Key: YARN-11225 > URL: https://issues.apache.org/jira/browse/YARN-11225 > Project: Hadoop YARN > Issue Type: Sub-task > Components: federation >Affects Versions: 3.4.0, 3.3.4 >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11225) [Federation] Add postDelegationToken, postDelegationTokenExpiration, cancelDelegationToken REST APIs for Router
fanshilun created YARN-11225: Summary: [Federation] Add postDelegationToken, postDelegationTokenExpiration, cancelDelegationToken REST APIs for Router Key: YARN-11225 URL: https://issues.apache.org/jira/browse/YARN-11225 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11223) [Federation] Add getAppPriority, updateApplicationPriority REST APIs for Router
fanshilun created YARN-11223: Summary: [Federation] Add getAppPriority, updateApplicationPriority REST APIs for Router Key: YARN-11223 URL: https://issues.apache.org/jira/browse/YARN-11223 Project: Hadoop YARN Issue Type: Sub-task Components: federation Reporter: fanshilun Assignee: fanshilun Fix For: 3.4.0, 3.3.4 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11224) [Federation] Add getAppQueue, updateAppQueue REST APIs for Router
fanshilun created YARN-11224: Summary: [Federation] Add getAppQueue, updateAppQueue REST APIs for Router Key: YARN-11224 URL: https://issues.apache.org/jira/browse/YARN-11224 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun Assignee: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11220) [Federation] Add getLabelsToNodes, getClusterNodeLabels, getLabelsOnNode REST APIs for Router
[ https://issues.apache.org/jira/browse/YARN-11220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fanshilun updated YARN-11220: - Summary: [Federation] Add getLabelsToNodes, getClusterNodeLabels, getLabelsOnNode REST APIs for Router (was: [Federation] Add getLabelsToNodes, getClusterNodeLabels REST APIs for Router) > [Federation] Add getLabelsToNodes, getClusterNodeLabels, getLabelsOnNode REST > APIs for Router > - > > Key: YARN-11220 > URL: https://issues.apache.org/jira/browse/YARN-11220 > Project: Hadoop YARN > Issue Type: Sub-task > Components: federation >Affects Versions: 3.4.0, 3.3.4 >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11222) [Federation] Add addToClusterNodeLabels, removeFromClusterNodeLabels REST APIs for Router
fanshilun created YARN-11222: Summary: [Federation] Add addToClusterNodeLabels, removeFromClusterNodeLabels REST APIs for Router Key: YARN-11222 URL: https://issues.apache.org/jira/browse/YARN-11222 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun Assignee: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-11220) [Federation] Add getLabelsToNodes, getClusterNodeLabels REST APIs for Router
[ https://issues.apache.org/jira/browse/YARN-11220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fanshilun reassigned YARN-11220: Assignee: fanshilun > [Federation] Add getLabelsToNodes, getClusterNodeLabels REST APIs for Router > > > Key: YARN-11220 > URL: https://issues.apache.org/jira/browse/YARN-11220 > Project: Hadoop YARN > Issue Type: Sub-task > Components: federation >Affects Versions: 3.4.0, 3.3.4 >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11221) [Federation] Add replaceLabelsOnNodes, replaceLabelsOnNode REST APIs for Router
fanshilun created YARN-11221: Summary: [Federation] Add replaceLabelsOnNodes, replaceLabelsOnNode REST APIs for Router Key: YARN-11221 URL: https://issues.apache.org/jira/browse/YARN-11221 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun Assignee: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11220) [Federation] Add getLabelsToNodes, getClusterNodeLabels REST APIs for Router
fanshilun created YARN-11220: Summary: [Federation] Add getLabelsToNodes, getClusterNodeLabels REST APIs for Router Key: YARN-11220 URL: https://issues.apache.org/jira/browse/YARN-11220 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11218) [Federation] Add getActivities, getBulkActivities REST APIs for Router
[ https://issues.apache.org/jira/browse/YARN-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fanshilun updated YARN-11218: - Summary: [Federation] Add getActivities, getBulkActivities REST APIs for Router (was: [Federation] Add getActivities,getBulkActivities REST APIs for Router) > [Federation] Add getActivities, getBulkActivities REST APIs for Router > -- > > Key: YARN-11218 > URL: https://issues.apache.org/jira/browse/YARN-11218 > Project: Hadoop YARN > Issue Type: Sub-task > Components: federation >Affects Versions: 3.4.0, 3.3.4 >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11219) [Federation] Add getAppActivities, getAppStatistics REST APIs for Router
fanshilun created YARN-11219: Summary: [Federation] Add getAppActivities, getAppStatistics REST APIs for Router Key: YARN-11219 URL: https://issues.apache.org/jira/browse/YARN-11219 Project: Hadoop YARN Issue Type: Sub-task Components: federation Reporter: fanshilun Assignee: fanshilun Fix For: 3.4.0, 3.3.4 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11218) [Federation] Add getActivities,getBulkActivities REST APIs for Router
fanshilun created YARN-11218: Summary: [Federation] Add getActivities,getBulkActivities REST APIs for Router Key: YARN-11218 URL: https://issues.apache.org/jira/browse/YARN-11218 Project: Hadoop YARN Issue Type: Sub-task Components: federation Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun Assignee: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11217) [Federation] Add dumpSchedulerLogs REST APIs for Router
fanshilun created YARN-11217: Summary: [Federation] Add dumpSchedulerLogs REST APIs for Router Key: YARN-11217 URL: https://issues.apache.org/jira/browse/YARN-11217 Project: Hadoop YARN Issue Type: Sub-task Affects Versions: 3.4.0, 3.3.4 Reporter: fanshilun Assignee: fanshilun -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11212) [Federation] Add getNodeToLabels REST APIs for Router
[ https://issues.apache.org/jira/browse/YARN-11212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fanshilun updated YARN-11212: - Parent: YARN-10146 Issue Type: Sub-task (was: Task) > [Federation] Add getNodeToLabels REST APIs for Router > - > > Key: YARN-11212 > URL: https://issues.apache.org/jira/browse/YARN-11212 > Project: Hadoop YARN > Issue Type: Sub-task > Components: federation >Affects Versions: 3.4.0, 3.3.4 >Reporter: fanshilun >Assignee: fanshilun >Priority: Major > Labels: pull-request-available > Time Spent: 2h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10146) [Federation] Add missing REST APIs for Router
[ https://issues.apache.org/jira/browse/YARN-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fanshilun updated YARN-10146: - Parent: (was: YARN-5597) Issue Type: Improvement (was: Sub-task) > [Federation] Add missing REST APIs for Router > - > > Key: YARN-10146 > URL: https://issues.apache.org/jira/browse/YARN-10146 > Project: Hadoop YARN > Issue Type: Improvement > Components: federation >Reporter: Bilwa S T >Assignee: fanshilun >Priority: Major > > In FederationInterceptorREST following API are not implemented: > |getClusterInfo| > |getSchedulerInfo| > |dumpSchedulerLogs| > |getActivities| > |getAppActivities| > |getAppStatistics| > |getAppState| > |getNodeToLabels| > |getLabelsToNodes| > |replaceLabelsOnNodes| > |replaceLabelsOnNode| > |getClusterNodeLabels| > |addToClusterNodeLabels| > |removeFromCluserNodeLabels| > |getLabelsOnNode| > |getAppPriority| > |updateApplicationPriority| > |getAppQueue| > |updateAppQueue| > |postDelegationToken| > |postDelegationTokenExpiration| > |cancelDelegationToken| > |createNewReservation| > |submitReservation| > |updateReservation| > |deleteReservation| > |listReservation| > |getAppTimeout| > |getAppTimeouts| > |updateApplicationTimeout| > |getAppAttempts| > |checkUserAccessToQueue| > |getAppAttempt| > |getContainers| > |getContainer| -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-11063) Support auto queue creation template wildcards for arbitrary queue depths
[ https://issues.apache.org/jira/browse/YARN-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bence Kosztolnik reassigned YARN-11063: --- Assignee: Bence Kosztolnik (was: Andras Gyori) > Support auto queue creation template wildcards for arbitrary queue depths > - > > Key: YARN-11063 > URL: https://issues.apache.org/jira/browse/YARN-11063 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Andras Gyori >Assignee: Bence Kosztolnik >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > With the introduction of YARN-10632, we need to support more than one > wildcard in queue templates. -- This message was sent by Atlassian Jira (v8.20.10#820010) - 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-11063) Support auto queue creation template wildcards for arbitrary queue depths
[ https://issues.apache.org/jira/browse/YARN-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570813#comment-17570813 ] Bence Kosztolnik edited comment on YARN-11063 at 7/25/22 9:58 AM: -- I had a sync with [~gandras] , and we discussed I will fix this issue as a basic ramp-up task was (Author: JIRAUSER292672): I had a sync with [~gandras] , and we discussed I will fix this issue as basic ramp-up task > Support auto queue creation template wildcards for arbitrary queue depths > - > > Key: YARN-11063 > URL: https://issues.apache.org/jira/browse/YARN-11063 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > With the introduction of YARN-10632, we need to support more than one > wildcard in queue templates. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-11063) Support auto queue creation template wildcards for arbitrary queue depths
[ https://issues.apache.org/jira/browse/YARN-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570813#comment-17570813 ] Bence Kosztolnik commented on YARN-11063: - I had a sync with [~gandras] , and we discussed I will fix this issue as basic ramp-up task > Support auto queue creation template wildcards for arbitrary queue depths > - > > Key: YARN-11063 > URL: https://issues.apache.org/jira/browse/YARN-11063 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > With the introduction of YARN-10632, we need to support more than one > wildcard in queue templates. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11063) Support auto queue creation template wildcards for arbitrary queue depths
[ https://issues.apache.org/jira/browse/YARN-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-11063: -- Labels: pull-request-available (was: ) > Support auto queue creation template wildcards for arbitrary queue depths > - > > Key: YARN-11063 > URL: https://issues.apache.org/jira/browse/YARN-11063 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > With the introduction of YARN-10632, we need to support more than one > wildcard in queue templates. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
