Hi Chris,
Thanks for your response!
I think I could miss the thread discussion of "[DISCUSS] 2.6.x line
releases" for something reason. I checked the discussion - Sean claimed that
HBase community needs 2.6.5, Zhe said they are using 2.6.x releases and Akira
said that are over new
Allen, to be clear, I am not against any branch release effort here. However,
as RM for previous releases 2.6.3 and 2.6.4, I feel to have responsibility to
take care branch-2.6 together with other RMs (Vinod and Sangjin) on this branch
and understand current gap - especially, to get consensus
> On Aug 11, 2016, at 5:59 AM, Junping Du wrote:
>
> These comments are more like wishes but not giving more clarifications
> on the needs. I would like to hear more specific reasons to not move to 2.7.x
> releases but prefer to upgrade to 2.6.5. If the only reason
Hi folks
You are all cordially invited to the YARN contributor meetup at Cloudera on
8/25. There will be a webex for folks who can't make it in person.
Please RSVP - http://www.meetup.com/Hadoop-Contributors/events/233285258/
Thanks
Karthik
Hi Ravi,
I don't think cgroups will help us, because, we don't want to impose a
hard limit on the memory usage, we just want to allow for short time
periods, when container can consume more memory than its limit. We don't
want to put the limit too high, because that causes underutilization of
Rohith Sharma K S created YARN-5512:
---
Summary: Finished containers for running application should be
displayed on container table
Key: YARN-5512
URL: https://issues.apache.org/jira/browse/YARN-5512
Nemo Chen created YARN-5511:
---
Summary: Log refactoring: method invocation should be replaced by
variable in yarn server
Key: YARN-5511
URL: https://issues.apache.org/jira/browse/YARN-5511
Project: Hadoop
Gour Saha created YARN-5513:
---
Summary: Move Java only tests from slider develop to
yarn-native-services
Key: YARN-5513
URL: https://issues.apache.org/jira/browse/YARN-5513
Project: Hadoop YARN
> On Aug 11, 2016, at 8:10 AM, Junping Du wrote:
>
> Allen, to be clear, I am not against any branch release effort here. However,
"I'm not an X but "
> as RM for previous releases 2.6.3 and 2.6.4, I feel to have responsibility to
> take care
Since there is sufficient interest in 2.6.5, we should probably do it. All
the reasons Allen outlines make sense.
That said, Junping brings up a very important point that we should think of
for future releases. For a new user or a user that does not directly
contribute to the project, more stable
Robert Kanter created YARN-5515:
---
Summary: Compatibility Docs should clarify the policy for what
takes precedence when a conflict is found
Key: YARN-5515
URL: https://issues.apache.org/jira/browse/YARN-5515
Sangeetha Abdu Jyothi created YARN-5516:
---
Summary: REST API changes for periodicity
Key: YARN-5516
URL: https://issues.apache.org/jira/browse/YARN-5516
Project: Hadoop YARN
Issue Type:
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/130/
[Aug 10, 2016 4:54:31 PM] (cnauroth) HADOOP-13476. CredentialProviderFactory
fails at class loading from
[Aug 10, 2016 6:04:18 PM] (jlowe) YARN-5483. Optimize
RMAppAttempt#pullJustFinishedContainers.
13 matches
Mail list logo