For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/520/
[Sep 11, 2017 4:58:10 AM] (sunilg) YARN-7163. RMContext need not to be injected
to webapp and other Always
[Sep 11, 2017 6:17:59 AM] (yufei) YARN-6799. Remove the duplicated code in
CGroupsHandlerImp.java.
Hello Junping,
Thank you for working on this. Should not YARN-6622 be addressed
first? "Summary:
Document Docker work as experimental".
Thank you,
Miklos
On Sun, Sep 10, 2017 at 6:39 PM, Mingliang Liu wrote:
> Thanks Junping for doing this!
>
> +1 (non-binding)
>
> - Download the hadoop-2.8.2
Thanks Junping Du.
+1 (non-binding)
-Built from source
-Installed HA cluster
-Executed basic shell commands
-Ran sample jobs
-Verified HDFS/YARN UI.
--Brahma Reddy Battula
On Mon, 11 Sep 2017 at 5:30 AM, Junping Du wrote:
> Hi folks,
> With fix of HADOOP-14842 get in, I've created our
Jooseong Kim created MAPREDUCE-6957:
---
Summary: shuffle hangs after a node manager connection timeout
Key: MAPREDUCE-6957
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6957
Project: Hadoop Map/
Thanks Mikols for notifying on this. I think docker support is general known as
alpha feature so document it as experimental is nice to have but not a blocker
for 2.8.2. I also noticed that our 2.7.x document
(https://hadoop.apache.org/docs/r2.7.4/hadoop-yarn/hadoop-yarn-site/DockerContainerExec
-1 (binding)
I don't think we should release this without YARN-6622.
Since this doesn't happen often: a -1 in this case is NOT a veto.
Releases are approved by majority vote of the PMC. -C
On Mon, Sep 11, 2017 at 11:45 AM, Junping Du wrote:
> Thanks Mikols for notifying on this. I think docker
Thanks for your consideration Jian, let's track this for GA then.
Best,
Andrew
On Fri, Sep 8, 2017 at 3:02 PM, Jian He wrote:
> Hi Andrew,
>
> At this point, there are no more release blockers including documentations
> from our side - all work done.
> But I agree it is too close to the release
I don't think this -1 is reasonable, because:
- If you look at YARN-6622 closely, it targets to fix a problematic
documentation work on YARN-5258 which get checked into 2.9 and 3.0 branch only.
It means it targets to fix a problem that 2.8.2 never exists.
- New docker container support (replace o
On Mon, Sep 11, 2017 at 2:52 PM, Junping Du wrote:
> I don't think this -1 is reasonable, because:
> - If you look at YARN-6622 closely, it targets to fix a problematic
> documentation work on YARN-5258 which get checked into 2.9 and 3.0 branch
> only. It means it targets to fix a problem that 2
Hello Folks
Thanks to everyone who chimed in in the discussion thread:
https://www.mail-archive.com/yarn-dev@hadoop.apache.org/msg27104.html
We have updated the roadmap wiki based on the feedback:
https://cwiki.apache.org/confluence/display/HADOOP/Roadmap#Roadmap-Version2.9
Given the explosion o
YARN-6622 is now committed to 2.9. We could backport YARN-5258 and
YARN-6622 for 2.8, but it'll take some editing. We'll have to check to
see what features are unsupported in 2.8 and remove those from the
docs. Not a huge effort overall, though. Probably a hour's work. I
may have time to t
Thanks Arun Suresh for creating the page.
+1 to have a page to track all planned releases, I also updated 3.1 release
plans.
Several suggestions:
1) Only put large features / changes which needed to be included by the
release, otherwise we will have too long list of JIRAs.
2) For release updates,
Thanks Daniel for volunteering for documentation effort.
I suspect the problem we are facing here is not a simply documentation truncate
effort, but indeed a incomplete feature problem. The umbrella JIRA YARN-3611
has 31 issues are marked as resolved but only 9 patches get backport to
branch-2.
Miklos just ping me offline that a security fix should get landed to resolve a
docker runtime issue. I will retrieval RC0 for security fixes landing.
In the mean while, if people here really think a document here is necessary
(although not enough verification to work as an alpha feature) and can
14 matches
Mail list logo
