Sumana Sathish created YARN-8508:
Summary: GPU does not get released even though the container is
killed
Key: YARN-8508
URL: https://issues.apache.org/jira/browse/YARN-8508
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-8474:
-
Description:
Sleeper job fails with Authentication required.
{code}
yarn app -launch sl1
Sumana Sathish created YARN-8474:
Summary: sleeper service fails to launch with "Authentication
Required"
Key: YARN-8474
URL: https://issues.apache.org/jira/browse/YARN-8474
Project: Hadoop YARN
Sumana Sathish created YARN-8460:
Summary: please add a way to fetch
'yarn.cluster.max-application-priority'
Key: YARN-8460
URL: https://issues.apache.org/jira/browse/YARN-8460
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-8423:
-
Description:
Run an Tensor flow app requesting one GPU.
Kill the application once the GPU is
Sumana Sathish created YARN-8423:
Summary: GPU does not get released even though the application
gets killed.
Key: YARN-8423
URL: https://issues.apache.org/jira/browse/YARN-8423
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-8317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish resolved YARN-8317.
--
Resolution: Won't Fix
href is #0 since clicking on the queue does not redirect to new page
Sumana Sathish created YARN-8317:
Summary: fix href in Queue page for RM UIV2
Key: YARN-8317
URL: https://issues.apache.org/jira/browse/YARN-8317
Project: Hadoop YARN
Issue Type: Bug
Sumana Sathish created YARN-8292:
Summary: Preemption of GPU resource does not happen if
memory/vcores is not required to be preempted
Key: YARN-8292
URL: https://issues.apache.org/jira/browse/YARN-8292
Sumana Sathish created YARN-8264:
Summary: [UI2 GPU] GPU Info tab disappears if we click any sub
link under List of Applications or List of Containers
Key: YARN-8264
URL:
Sumana Sathish created YARN-8230:
Summary: [UI2] Attempt Info page url shows NA for several fields
for container info
Key: YARN-8230
URL: https://issues.apache.org/jira/browse/YARN-8230
Project:
[
https://issues.apache.org/jira/browse/YARN-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish reassigned YARN-8229:
Assignee: Wangda Tan
> Expose api to fetch info on how many GPUs being preempted
>
Sumana Sathish created YARN-8229:
Summary: exp
Key: YARN-8229
URL: https://issues.apache.org/jira/browse/YARN-8229
Project: Hadoop YARN
Issue Type: Bug
Reporter: Sumana Sathish
[
https://issues.apache.org/jira/browse/YARN-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-8229:
-
Component/s: yarn
> Expose api to fetch info on how many GPUs being preempted
>
[
https://issues.apache.org/jira/browse/YARN-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-8229:
-
Summary: Expose api to fetch info on how many GPUs being preempted (was:
exp)
> Expose api to
Sumana Sathish created YARN-8205:
Summary: AM launching is delayed, then state is not updated in ATS
Key: YARN-8205
URL: https://issues.apache.org/jira/browse/YARN-8205
Project: Hadoop YARN
Sumana Sathish created YARN-8197:
Summary: Tracking URL in the app state does not get redirected to
MR ApplicationMaster for Running applications
Key: YARN-8197
URL:
Sumana Sathish created YARN-8187:
Summary: [UI2] clicking on Individual Nodes does not contain
breadcums in Nodes Page
Key: YARN-8187
URL: https://issues.apache.org/jira/browse/YARN-8187
Project:
[
https://issues.apache.org/jira/browse/YARN-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-8183:
-
Priority: Critical (was: Major)
> yClient for Kill Application stuck in infinite loop with
Sumana Sathish created YARN-8183:
Summary: yClient for Kill Application stuck in infinite loop with
message "Waiting for Application to be killed"
Key: YARN-8183
URL:
Sumana Sathish created YARN-8182:
Summary: [UI2] Proxy- Clicking on nodes under Nodes HeatMap gives
401 error
Key: YARN-8182
URL: https://issues.apache.org/jira/browse/YARN-8182
Project: Hadoop YARN
Sumana Sathish created YARN-8075:
Summary: DShell does not Fail when we ask more GPUs than available
even though AM throws 'InvalidResourceRequestException'
Key: YARN-8075
URL:
Sumana Sathish created YARN-8005:
Summary: Add unit tests for queue priority with dominant resource
calculator
Key: YARN-8005
URL: https://issues.apache.org/jira/browse/YARN-8005
Project: Hadoop
Sumana Sathish created YARN-8004:
Summary: Add unit tests for inter queue preemption for dominant
resource calculator
Key: YARN-8004
URL: https://issues.apache.org/jira/browse/YARN-8004
Project:
Sumana Sathish created YARN-7761:
Summary: [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-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-7760:
-
Summary: [UI2]Clicking 'Master Node' or link next to 'AM Node Web UI' under
application's
Sumana Sathish created YARN-7760:
Summary: [UI2}Clicking 'Master Node' or link next to 'AM Node Web
UI' under application's appAttempt page goes to OLD RM UI
Key: YARN-7760
URL:
Sumana Sathish created YARN-7759:
Summary: [UI2]GPU chart shows as "Available: 0" even though GPU is
available
Key: YARN-7759
URL: https://issues.apache.org/jira/browse/YARN-7759
Project: Hadoop YARN
Sumana Sathish created YARN-7738:
Summary: DShell requesting gpu resources fails to run
Key: YARN-7738
URL: https://issues.apache.org/jira/browse/YARN-7738
Project: Hadoop YARN
Issue Type:
[
https://issues.apache.org/jira/browse/YARN-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-7234:
-
Release Note: (was: Do not see the issue anymore)
Do not see the issue anymore. Hence closing
[
https://issues.apache.org/jira/browse/YARN-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish resolved YARN-7234.
--
Resolution: Cannot Reproduce
Release Note: Do not see the issue anymore
> Kill Application
Sumana Sathish created YARN-7269:
Summary: Tracking URL in the app state does not get redirected to
ApplicationMaster for Running applications
Key: YARN-7269
URL: https://issues.apache.org/jira/browse/YARN-7269
Sumana Sathish created YARN-7234:
Summary: Kill Application button shows "404 Error" even though the
application gets killed
Key: YARN-7234
URL: https://issues.apache.org/jira/browse/YARN-7234
[
https://issues.apache.org/jira/browse/YARN-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-7185:
-
Fix Version/s: 3.0.0
> Application fails to go to FINISHED state or sometimes to RUNNING state
>
Sumana Sathish created YARN-7185:
Summary: Application fails to go to FINISHED state or sometimes to
RUNNING state
Key: YARN-7185
URL: https://issues.apache.org/jira/browse/YARN-7185
Project: Hadoop
[
https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129622#comment-16129622
]
Sumana Sathish commented on YARN-7011:
--
bq. There's the problem then. Remove it. Setting
[
https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129303#comment-16129303
]
Sumana Sathish edited comment on YARN-7011 at 8/16/17 7:35 PM:
---
yarn --config
[
https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129303#comment-16129303
]
Sumana Sathish edited comment on YARN-7011 at 8/16/17 7:35 PM:
---
yarn --config
[
https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129303#comment-16129303
]
Sumana Sathish commented on YARN-7011:
--
yarn --config /tmp/hadoopConf --daemon start --debug
[
https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128024#comment-16128024
]
Sumana Sathish edited comment on YARN-7011 at 8/15/17 11:08 PM:
Hi [~aw],
[
https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128024#comment-16128024
]
Sumana Sathish commented on YARN-7011:
--
Hi [~aw],
I could see "DEBUG: HADOOP_CONF_DIR=/tmp/hadoop"
Sumana Sathish created YARN-7011:
Summary: yarn-daemon.sh is not respecting --config option
Key: YARN-7011
URL: https://issues.apache.org/jira/browse/YARN-7011
Project: Hadoop YARN
Issue
Sumana Sathish created YARN-6992:
Summary: "Kill application" button is present even if the
application is FINISHED in RM UI
Key: YARN-6992
URL: https://issues.apache.org/jira/browse/YARN-6992
Sumana Sathish created YARN-6991:
Summary: "Kill application" button does not show error if other
user tries to kill the application for secure cluster
Key: YARN-6991
URL:
[
https://issues.apache.org/jira/browse/YARN-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-6977:
-
Description:
There is no information on which node non am container is being assigned in the
Sumana Sathish created YARN-6977:
Summary: Node information is not provided for non am containers in
RM logs
Key: YARN-6977
URL: https://issues.apache.org/jira/browse/YARN-6977
Project: Hadoop YARN
Sumana Sathish created YARN-6891:
Summary: Can kill other user's applications via RM UI
Key: YARN-6891
URL: https://issues.apache.org/jira/browse/YARN-6891
Project: Hadoop YARN
Issue Type:
Sumana Sathish created YARN-6570:
Summary: No logs were found for running application, running
container
Key: YARN-6570
URL: https://issues.apache.org/jira/browse/YARN-6570
Project: Hadoop YARN
Sumana Sathish created YARN-6271:
Summary: yarn rmadin -getGroups returns information from standby RM
Key: YARN-6271
URL: https://issues.apache.org/jira/browse/YARN-6271
Project: Hadoop YARN
Sumana Sathish created YARN-6174:
Summary: Log files pattern should be same for both running and
finished container
Key: YARN-6174
URL: https://issues.apache.org/jira/browse/YARN-6174
Project: Hadoop
[
https://issues.apache.org/jira/browse/YARN-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish resolved YARN-5539.
--
Resolution: Cannot Reproduce
Not able to reproduce the issue.
> AM fails due to
Sumana Sathish created YARN-5539:
Summary: AM fails due to "java.net.SocketTimeoutException: Read
timed out"
Key: YARN-5539
URL: https://issues.apache.org/jira/browse/YARN-5539
Project: Hadoop YARN
Sumana Sathish created YARN-5500:
Summary: 'Master node' link under application tab is broken
Key: YARN-5500
URL: https://issues.apache.org/jira/browse/YARN-5500
Project: Hadoop YARN
Issue
[
https://issues.apache.org/jira/browse/YARN-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-5499:
-
Description:
Steps to reproduce:
* Click on Nodes. This page will list nodes of the cluster
*
Sumana Sathish created YARN-5499:
Summary: Logs of container loads first time but fails if you go
back and click again
Key: YARN-5499
URL: https://issues.apache.org/jira/browse/YARN-5499
Project:
[
https://issues.apache.org/jira/browse/YARN-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-5339:
-
Description:
passing file to -out for YARN log CLI doesnt give warning or error code
{code}
yarn
Sumana Sathish created YARN-5361:
Summary: Obtaining logs for completed container says 'file belongs
to a running container ' at the end
Key: YARN-5361
URL: https://issues.apache.org/jira/browse/YARN-5361
[
https://issues.apache.org/jira/browse/YARN-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish reopened YARN-5080:
--
> Cannot obtain logs using YARN CLI -am for either KILLED or RUNNING AM
>
Sumana Sathish created YARN-5340:
Summary: App Name/User/RPC Port/AM Host info is missing from ATS
web service or YARN CLI's app info
Key: YARN-5340
URL: https://issues.apache.org/jira/browse/YARN-5340
[
https://issues.apache.org/jira/browse/YARN-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-5340:
-
Assignee: (was: Li Lu)
> App Name/User/RPC Port/AM Host info is missing from ATS web service
Sumana Sathish created YARN-5339:
Summary: passing file to -out for YARN log CLI doesnt give warning
or error code
Key: YARN-5339
URL: https://issues.apache.org/jira/browse/YARN-5339
Project: Hadoop
Sumana Sathish created YARN-5337:
Summary: Dshell AM failed with "java.lang.OutOfMemoryError: GC
overhead limit exceeded"
Key: YARN-5337
URL: https://issues.apache.org/jira/browse/YARN-5337
Project:
Sumana Sathish created YARN-5268:
Summary: DShell AM fails java.lang.InterruptedException
Key: YARN-5268
URL: https://issues.apache.org/jira/browse/YARN-5268
Project: Hadoop YARN
Issue Type:
Sumana Sathish created YARN-5266:
Summary: Wrong exit code while trying to get app logs using regex
via CLI
Key: YARN-5266
URL: https://issues.apache.org/jira/browse/YARN-5266
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-5231:
-
Summary: obtaining app logs for last 'n' bytes using CLI gives
'java.io.IOException' (was:
Sumana Sathish created YARN-5231:
Summary: obtaining yarn logs for last 'n' bytes using CLI gives
'java.io.IOException'
Key: YARN-5231
URL: https://issues.apache.org/jira/browse/YARN-5231
Project:
Sumana Sathish created YARN-5131:
Summary: Distributed shell AM fails Java Null Point Exception
Key: YARN-5131
URL: https://issues.apache.org/jira/browse/YARN-5131
Project: Hadoop YARN
Issue
[
https://issues.apache.org/jira/browse/YARN-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-5103:
-
Description:
AM is restarted when NM is restarted multiple times even though NM recovery is
Sumana Sathish created YARN-5103:
Summary: With NM recovery enabled, restarting NM multiple times
results in AM restart
Key: YARN-5103
URL: https://issues.apache.org/jira/browse/YARN-5103
Project:
Sumana Sathish created YARN-5084:
Summary: Cannot obtain AM container logs for the finished
application using YARN CLI
Key: YARN-5084
URL: https://issues.apache.org/jira/browse/YARN-5084
Project:
Sumana Sathish created YARN-5083:
Summary: YARN CLI for AM logs does not give any error message if
entered invalid am value
Key: YARN-5083
URL: https://issues.apache.org/jira/browse/YARN-5083
Sumana Sathish created YARN-5080:
Summary: Cannot obtain logs using YARN CLI -am for either KILLED
or RUNNING AM
Key: YARN-5080
URL: https://issues.apache.org/jira/browse/YARN-5080
Project: Hadoop
[
https://issues.apache.org/jira/browse/YARN-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-5002:
-
Assignee: Jian He
> getApplicationReport call may raise NPE
>
Sumana Sathish created YARN-5002:
Summary: getApplicationReport call may raise NPE
Key: YARN-5002
URL: https://issues.apache.org/jira/browse/YARN-5002
Project: Hadoop YARN
Issue Type: Bug
Sumana Sathish created YARN-4965:
Summary: Distributed shell AM failed due to ClientHandlerException
thrown by jersey
Key: YARN-4965
URL: https://issues.apache.org/jira/browse/YARN-4965
Project:
[
https://issues.apache.org/jira/browse/YARN-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-4794:
-
Description:
Distributed shell app gets stuck on stopping containers after App completes
with the
[
https://issues.apache.org/jira/browse/YARN-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-4794:
-
Description:
Distributed shell app gets stuck on stopping containers after App completes
with the
Sumana Sathish created YARN-4794:
Summary: Distributed shell app gets stuck on stopping containers
after App completes
Key: YARN-4794
URL: https://issues.apache.org/jira/browse/YARN-4794
Project:
Sumana Sathish created YARN-3753:
Summary: RM failed to come up with java.io.IOException: Wait for
ZKClient creation timed out
Key: YARN-3753
URL: https://issues.apache.org/jira/browse/YARN-3753
Sumana Sathish created YARN-3681:
Summary: yarn cmd says could not find main class 'queue' in
windows
Key: YARN-3681
URL: https://issues.apache.org/jira/browse/YARN-3681
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-3681:
-
Labels: windows yarn-client (was: yarn-client)
yarn cmd says could not find main class 'queue'
[
https://issues.apache.org/jira/browse/YARN-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-3681:
-
Attachment: yarncmd.png
yarn cmd says could not find main class 'queue' in windows
Sumana Sathish created YARN-3493:
Summary: RM fails to come up with error Failed to load/recover
state when mem settings are changed
Key: YARN-3493
URL: https://issues.apache.org/jira/browse/YARN-3493
[
https://issues.apache.org/jira/browse/YARN-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated YARN-3493:
-
Attachment: yarn-yarn-resourcemanager.log.zip
RM fails to come up with error Failed to
84 matches
Mail list logo
