Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Umbrella jira to track all forms of usability issues in YARN that need to be addressed before YARN can be considered stable.
Attachments
Issue Links
- is blocked by
-
YARN-378 ApplicationMaster retry times should be set by Client
- Closed
-
YARN-416 Limiting the Diagnostic related data on Application Overview Page
- Open
-
YARN-182 Unnecessary "Container killed by the ApplicationMaster" message for successful containers
- Resolved
-
YARN-471 NM does not validate the resource capabilities before it registers with RM
- Resolved
-
YARN-227 Application expiration difficult to debug for end-users
- Closed
-
YARN-337 RM handles killed application tracking URL poorly
- Closed
-
YARN-379 yarn [node,application] command print logger info messages
- Closed
-
YARN-380 yarn node -status prints Last-Last-Health-Update
- Closed
-
YARN-410 New lines in diagnostics for a failed app on the per-application page make it hard to read
- Closed
-
YARN-470 Support a way to disable resource monitoring on the NodeManager
- Closed
-
YARN-257 NM should gracefully handle a full local disk
- Open
-
YARN-463 Show explicitly excluded nodes on the UI
- Open
-
YARN-1019 YarnConfiguration validation for local disk path and http addresses.
- Open
-
YARN-237 Refreshing the RM page forgets how many rows I had in my Datatables
- Closed
-
YARN-249 Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)
- Closed
-
YARN-198 If we are navigating to Nodemanager UI from Resourcemanager,then there is not link to navigate back to Resource manager
- Closed