For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/601/
[Nov 21, 2017 5:09:16 PM] (haibochen) YARN-7531. ResourceRequest.equal does not
check
[Nov 21, 2017 6:33:34 PM] (yufei) YARN-7513. Remove the scheduler lock in
FSAppAttempt.getWeight()
[Nov 22, 2017
Thanks for the links, Arun. I see I missed this part.
Glad the decision was conscious.
Thanks for the release.
--Konstantin
On Wed, Nov 22, 2017 at 11:39 AM, Arun Suresh wrote:
> Hello Konstantin
>
> We actually did discuss a bit about this:
>
Thanks Konstantin and Weiwei for calling attention. These two HDFS issues looks
to be important to be fixed which are on my radar now.
I will hold on RC cut until we figure them out.
Thanks,
Junping
From: Weiwei Yang
Sent: Tuesday,
Hello Konstantin
We actually did discuss a bit about this:
https://www.mail-archive.com/yarn-dev@hadoop.apache.org/msg28407.html
https://www.mail-archive.com/yarn-dev@hadoop.apache.org/msg28403.html
We finally decided to add the following disclaimer on the release page (
Hey guys,
I don't think this has been discussed, pardon if it was.
As it stands today hadoop 2.9.0 is marked as stable release. Isn't that
deceptive for users?
Not to diminish the quality and not to understate the effort, which was
huge and very much appreciated.
But it is the first in the
bq. (a) The behavior of this command. Clearly, it will conflict with the
MapReduce JHS - only one of them can be started on the same node.
Yes,Since the PID file will be same.
This problem will not present in branch-2.9 + as pid file will be suffix
with mapred(for JHS)
Chris Douglas created MAPREDUCE-7013:
Summary: Tests of internal logic should not use the local FS as
scratch space
Key: MAPREDUCE-7013
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7013
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/47/
[Nov 20, 2017 4:01:50 PM] (bibinchundatt) YARN-7489.
ConcurrentModificationException in RMAppImpl#getRMAppMetrics.
[Nov 20, 2017 7:01:15 PM] (bibinchundatt) YARN-7525. Incorrect query parameters
in