[
https://issues.apache.org/jira/browse/YARN-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S resolved YARN-5477.
-
Resolution: Duplicate
> ApplicationId should not be visible to client before NEW_SAVING
Hi Jan!
Thanks for your contribution. In your approach what happens when a few
containers on a node are using "excessive" memory (so that total memory
used > RAM available on the machine). Do you have overcommit enabled?
Thanks
Ravi
On Tue, Aug 9, 2016 at 1:31 AM, Jan Lukavský
Based on the sentiment in the "[DISCUSS] 2.6.x line releases" thread, I
have moved forward with some of the initial effort in creating a 2.6.5
release. I am forking this thread so we have a dedicated 2.6.5 release
thread.
I have gone through the git logs and gathered a list of JIRAs that are in
Arun Suresh created YARN-5501:
-
Summary: Container Pooling in YARN
Key: YARN-5501
URL: https://issues.apache.org/jira/browse/YARN-5501
Project: Hadoop YARN
Issue Type: Improvement
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
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:
Gour Saha created YARN-5498:
---
Summary: [Usability] Make UI continue to work and render already
loaded models even when there is no network connection
Key: YARN-5498
URL: https://issues.apache.org/jira/browse/YARN-5498
Yesha Vora created YARN-5497:
Summary: Use different color for Undefined and Succeeded final
state in application page
Key: YARN-5497
URL: https://issues.apache.org/jira/browse/YARN-5497
Project: Hadoop
Yesha Vora created YARN-5496:
Summary: Make Node Heatmap Chart categories clickable
Key: YARN-5496
URL: https://issues.apache.org/jira/browse/YARN-5496
Project: Hadoop YARN
Issue Type: Sub-task
Ray Chiang created YARN-5495:
Summary: Clean up imports in CapacityScheduler
Key: YARN-5495
URL: https://issues.apache.org/jira/browse/YARN-5495
Project: Hadoop YARN
Issue Type: Task
Yesha Vora created YARN-5494:
Summary: Nodes page throws "Sorry Error Occurred" message
Key: YARN-5494
URL: https://issues.apache.org/jira/browse/YARN-5494
Project: Hadoop YARN
Issue Type:
Yesha Vora created YARN-5493:
Summary: In leaf queue page, list applications should only show
applications from that leaf queues
Key: YARN-5493
URL: https://issues.apache.org/jira/browse/YARN-5493
Jason Lowe created YARN-5492:
Summary: TestSubmitApplicationWithRMHA is failing sporadically
during precommit builds
Key: YARN-5492
URL: https://issues.apache.org/jira/browse/YARN-5492
Project: Hadoop
Bibin A Chundatt created YARN-5491:
--
Summary: Random Failure TestCapacityScheduler#testCSQueueBlocked
Key: YARN-5491
URL: https://issues.apache.org/jira/browse/YARN-5491
Project: Hadoop YARN
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/128/
[Aug 8, 2016 4:19:54 PM] (varunsaxena) MAPREDUCE-6748. Enhance logging for
Cluster.java around
[Aug 8, 2016 4:42:53 PM] (varunsaxena) YARN-4910. Fix incomplete log info in
ResourceLocalizationService (Jun
Another reason I like the 3.0.0-alphaX approach is the ease of
communicating compatibility guarantees.
A lot of our compatibility guarantees (e.g. API/wire compat) mention
"within a major release". For the user, thinking of 3.0.0 as the beginning
of a major release seems easier than 3.2.0 being
Most people I talked to found 3.0.0-alpha, 3.1.0-alpha/beta confusing. I am
not aware of any other software shipped that way. While being used by other
software does not make an approach right, I think we should adopt an
approach that is easy for our users to understand.
The notion of
Sunil G created YARN-5490:
-
Summary: Fix various alignment issues in Node page and the broken
breadcrumb link
Key: YARN-5490
URL: https://issues.apache.org/jira/browse/YARN-5490
Project: Hadoop YARN
RaghuMitra created YARN-5489:
Summary: Improvement on doughnut subcharts
Key: YARN-5489
URL: https://issues.apache.org/jira/browse/YARN-5489
Project: Hadoop YARN
Issue Type: Sub-task
Harish Jaiprakash created YARN-5488:
---
Summary: Table in Application tab overflows beyond page boundary.
Key: YARN-5488
URL: https://issues.apache.org/jira/browse/YARN-5488
Project: Hadoop YARN
Hello community,
I have a question about container resource calculation in nodemanager.
Some time ago a filed JIRA
https://issues.apache.org/jira/browse/YARN-4681, which I though might
address our problems with container being killed because of read-only
mmaping memory block. The JIRA has
21 matches
Mail list logo