[jira] [Resolved] (HADOOP-14284) Shade Guava everywhere

2017-09-11 Thread Tsuyoshi Ozawa (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsuyoshi Ozawa resolved HADOOP-14284.
-
Resolution: Invalid

> Shade Guava everywhere
> --
>
> Key: HADOOP-14284
> URL: https://issues.apache.org/jira/browse/HADOOP-14284
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: build
>Affects Versions: 3.0.0-alpha4
>Reporter: Andrew Wang
>Priority: Blocker
> Attachments: HADOOP-14238.pre001.patch, HADOOP-14284.002.patch, 
> HADOOP-14284.004.patch, HADOOP-14284.007.patch, HADOOP-14284.010.patch, 
> HADOOP-14284.012.patch
>
>
> HADOOP-10101 upgraded the guava version for 3.x to 21.
> Guava is broadly used by Java projects that consume our artifacts. 
> Unfortunately, these projects also consume our private artifacts like 
> {{hadoop-hdfs}}. They also are unlikely on the new shaded client introduced 
> by HADOOP-11804, currently only available in 3.0.0-alpha2.
> We should shade Guava everywhere to proactively avoid breaking downstreams. 
> This isn't a requirement for all dependency upgrades, but it's necessary for 
> known-bad dependencies like Guava.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

2017-09-11 Thread Junping Du 
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 work out 
a patch soon, I am open to accept it. 

Thanks,

Junping

From: Junping Du 
Sent: Monday, September 11, 2017 5:32 PM
To: Daniel Templeton; Chris Douglas
Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

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.8 no matter intentioned or not. So far, I haven't heard anyone claimed 
that they are deploying/testing 2.8 release without cherry pick additional 
patches for enabling new docker executor runtime.
IMO, it is better to treat this feature in 2.8 as incomplete feature instead of 
an alpha/experimental feature, especially it is out of our previous 2.8 scope. 
If so, instead of documenting something misleading, we should keep new 
settings/configurations private (as it is now) to get rid of getting enabled by 
users occasionally.
Thoughts?


Thanks,

Junping

From: Daniel Templeton 
Sent: Monday, September 11, 2017 4:45 PM
To: Chris Douglas; Junping Du
Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

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 try do it later this week.  Anyone else want to volunteer?

Daniel

On 9/11/17 3:01 PM, Chris Douglas wrote:
> 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.8.2 never exists.
> ...we're not going to document security implications- which include
> escalations to root- because we don't have _any_ documentation? Why
> don't we backport the documentation?
>
>> - New docker container support (replace of old DockerContainerExectutor) is 
>> still an alpha feature now which doesn't highlight in 2.8 major 
>> features/improvement (http://hadoop.apache.org/docs/r2.8.0/index.html). So 
>> adding documentation here is also not a blocker.
> YARN-6622 is *documenting* the fact that this is an alpha feature and
> that it shouldn't be enabled in secure environments. How are users
> supposed to make this determination without it?
>
>> Vote still continue until a real blocker comes.
> Soright. I remain -1. -C
>
>> 
>> From: Chris Douglas 
>> Sent: Monday, September 11, 2017 12:00 PM
>> To: Junping Du
>> Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev; 
>> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
>> Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)
>>
>> -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 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/DockerContainerExecutor.html)
>>>  without mentioning docker support is experimental. We may need to fix that 
>>> as well in following releases.
>>>
>>> I can also add it (mentioning docker container support feature is 
>>> experimental) to release message in public website just like previous 
>>> release we call 2.7.0/2.8.0 as non-production release.
>>>
>>> I think vote should continue until we could find a real blocker.
>>>
>>>
>>> Thanks,
>>>
>>>
>>> Junping
>>>
>>>
>>> 
>>> From: Miklos Szegedi 
>>> Sent: Monday, September 11, 2017 10:07 AM
>>> To: Mingliang Liu
>>> Cc: Hadoop Common;

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

2017-09-11 Thread Junping Du 
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.8 no matter intentioned or not. So far, I haven't heard anyone claimed 
that they are deploying/testing 2.8 release without cherry pick additional 
patches for enabling new docker executor runtime.
IMO, it is better to treat this feature in 2.8 as incomplete feature instead of 
an alpha/experimental feature, especially it is out of our previous 2.8 scope. 
If so, instead of documenting something misleading, we should keep new 
settings/configurations private (as it is now) to get rid of getting enabled by 
users occasionally.
Thoughts?


Thanks,

Junping

From: Daniel Templeton 
Sent: Monday, September 11, 2017 4:45 PM
To: Chris Douglas; Junping Du
Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

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 try do it later this week.  Anyone else want to volunteer?

Daniel

On 9/11/17 3:01 PM, Chris Douglas wrote:
> 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.8.2 never exists.
> ...we're not going to document security implications- which include
> escalations to root- because we don't have _any_ documentation? Why
> don't we backport the documentation?
>
>> - New docker container support (replace of old DockerContainerExectutor) is 
>> still an alpha feature now which doesn't highlight in 2.8 major 
>> features/improvement (http://hadoop.apache.org/docs/r2.8.0/index.html). So 
>> adding documentation here is also not a blocker.
> YARN-6622 is *documenting* the fact that this is an alpha feature and
> that it shouldn't be enabled in secure environments. How are users
> supposed to make this determination without it?
>
>> Vote still continue until a real blocker comes.
> Soright. I remain -1. -C
>
>> 
>> From: Chris Douglas 
>> Sent: Monday, September 11, 2017 12:00 PM
>> To: Junping Du
>> Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev; 
>> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
>> Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)
>>
>> -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 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/DockerContainerExecutor.html)
>>>  without mentioning docker support is experimental. We may need to fix that 
>>> as well in following releases.
>>>
>>> I can also add it (mentioning docker container support feature is 
>>> experimental) to release message in public website just like previous 
>>> release we call 2.7.0/2.8.0 as non-production release.
>>>
>>> I think vote should continue until we could find a real blocker.
>>>
>>>
>>> Thanks,
>>>
>>>
>>> Junping
>>>
>>>
>>> 
>>> From: Miklos Szegedi 
>>> Sent: Monday, September 11, 2017 10:07 AM
>>> To: Mingliang Liu
>>> Cc: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org; 
>>> yarn-...@hadoop.apache.org; junping_du; Junping Du
>>> Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)
>>>
>>> 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-src.tar.gz file and checked the md5 value
>>> - Build package using maven (skipping tests) with Java 8
>>> - Spin up a test cluster in Docker containers having

[jira] [Created] (HADOOP-14861) Fix reencryptEncryptedKey error in TestKMS

2017-09-11 Thread Ray Chiang (JIRA) 
Ray Chiang created HADOOP-14861:
---

 Summary: Fix reencryptEncryptedKey error in TestKMS
 Key: HADOOP-14861
 URL: https://issues.apache.org/jira/browse/HADOOP-14861
 Project: Hadoop Common
  Issue Type: Bug
Affects Versions: 3.0.0-beta1
Reporter: Ray Chiang


I'm seeing this error occur about 30-60% of the time in TestKMS

Tests run: 29, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 104.098 sec 
<<< FAILURE! - in org.apache.hadoop.crypto.key.kms.server.TestKMS
testACLs(org.apache.hadoop.crypto.key.kms.server.TestKMS)  Time elapsed: 2.691 
sec  <<< FAILURE!
java.lang.AssertionError: Should not have been able to reencryptEncryptedKey
at org.junit.Assert.fail(Assert.java:88)
at 
org.apache.hadoop.crypto.key.kms.server.TestKMS$11$15.run(TestKMS.java:1697)
at 
org.apache.hadoop.crypto.key.kms.server.TestKMS$11$15.run(TestKMS.java:1689)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
at 
org.apache.hadoop.crypto.key.kms.server.TestKMS.doAs(TestKMS.java:325)
at 
org.apache.hadoop.crypto.key.kms.server.TestKMS.access$200(TestKMS.java:103)




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: Release 2.9.0 update

2017-09-11 Thread Wangda Tan 
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, detailed informations. Keep them in a separated
page. (Like
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates
)
3) Regarding to order of releases, I suggest to sort them by planned
release date in ascending order.

- Wangda


On Mon, Sep 11, 2017 at 3:10 PM, Arun Suresh  wrote:

> 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 of YARN features currently in the roadmap and based on
> offline discussions with Vinod et. al, We have decided to add a production
> sponsor criteria for the features listed. Essentially, what it means is
> that we will favor inclusion of a feature in the 2.9.0 release if it is
> associated with an immediate production deployment requirement, failing
> which we would recommend moving it to the next major release. For eg., as
> decided by the community for HDFS Erasure coding. This is also in
> consideration with advanced stages of 3.0.0 and 3.1.0 planning.
>
> In summary. We would like to invite sponsors for each of the features in
> the roadmap wiki. Kindly do so by filling in the "Production Sponsor"
> column on the table:
> https://cwiki.apache.org/confluence/display/HADOOP/Roadmap#Roadmap-
> Plannedfeatures:.2
>
>
> Thanks
> Arun / Subru
>

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

2017-09-11 Thread Daniel Templeton 
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 try do it later this week.  Anyone else want to volunteer?


Daniel

On 9/11/17 3:01 PM, Chris Douglas wrote:

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.8.2 never exists.

...we're not going to document security implications- which include
escalations to root- because we don't have _any_ documentation? Why
don't we backport the documentation?


- New docker container support (replace of old DockerContainerExectutor) is 
still an alpha feature now which doesn't highlight in 2.8 major 
features/improvement (http://hadoop.apache.org/docs/r2.8.0/index.html). So 
adding documentation here is also not a blocker.

YARN-6622 is *documenting* the fact that this is an alpha feature and
that it shouldn't be enabled in secure environments. How are users
supposed to make this determination without it?


Vote still continue until a real blocker comes.

Soright. I remain -1. -C



From: Chris Douglas 
Sent: Monday, September 11, 2017 12:00 PM
To: Junping Du
Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

-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 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/DockerContainerExecutor.html)
 without mentioning docker support is experimental. We may need to fix that as 
well in following releases.

I can also add it (mentioning docker container support feature is experimental) 
to release message in public website just like previous release we call 
2.7.0/2.8.0 as non-production release.

I think vote should continue until we could find a real blocker.


Thanks,


Junping



From: Miklos Szegedi 
Sent: Monday, September 11, 2017 10:07 AM
To: Mingliang Liu
Cc: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org; 
yarn-...@hadoop.apache.org; junping_du; Junping Du
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

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-src.tar.gz file and checked the md5 value
- Build package using maven (skipping tests) with Java 8
- Spin up a test cluster in Docker containers having 1 master node (NN/RM) and 
3 slave nodes (DN/NM)
- Operate the basic HDFS/YARN operations from command line, both client and 
admin
- Check NN/RM Web UI
- Run distcp to copy files from/to local and HDFS
- Run hadoop mapreduce examples: grep and wordcount
- Check the HDFS service logs

All looked good to me.

Mingliang


On Sep 10, 2017, at 5:00 PM, Junping Du 
> wrote:

Hi folks,
 With fix of HADOOP-14842 get in, I've created our first release candidate 
(RC0) for Apache Hadoop 2.8.2.

 Apache Hadoop 2.8.2 is the first stable release of Hadoop 2.8 line and 
will be the latest stable/production release for Apache Hadoop - it includes 
305 new fixed issues since 2.8.1 and 63 fixes are marked as blocker/critical 
issues.

  More information about the 2.8.2 release plan can be found here: 
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release

  New RC is available at: 
http://home.apache.org/~junping_du/hadoop-2.8.2-RC0

  The RC tag in git is: release-2.8.2-RC0, and the latest commit id is: 
e6597fe3000b06847d2bf55f2bab81770f4b2505

  The maven artifacts are available via 
repository.apache.org at: 
https://repository.apache.org/content/repositories/orgapachehadoop-1062

  Please try the release and vote; the vote will run for the usual 5 days, 
ending on 09/15/2017 5pm PST time.

Thanks,

Junping

Re: Access to confluence wiki

2017-09-11 Thread Anu Engineer 
Can I please get access too, Confluence user name : anu

Thanks
Anu





On 9/11/17, 4:08 PM, "Arun Suresh"  wrote:

>I've added Subru and Chris.
>
>@Vrushali, I could not find your username. I think you need to sign up to
>confluence first with your apache id.
>
>Cheers
>-Arun
>
>
>
>On Mon, Sep 11, 2017 at 3:36 PM, Vrushali C  wrote:
>
>> I would like to get access to the Hadoop Wiki as well. My apache id is
>> "vrushali".
>>
>> thanks
>> Vrushali
>>
>>
>> On Mon, Sep 11, 2017 at 3:33 PM, Subru Krishnan  wrote:
>>
>> > Hi,
>> >
>> > Can I get access to the Hadoop wiki. My confluence is "subru".
>> >
>> > TIA.
>> >
>> > -Subru
>> >
>>

Re: Access to confluence wiki

2017-09-11 Thread Arun Suresh 
I've added Subru and Chris.

@Vrushali, I could not find your username. I think you need to sign up to
confluence first with your apache id.

Cheers
-Arun



On Mon, Sep 11, 2017 at 3:36 PM, Vrushali C  wrote:

> I would like to get access to the Hadoop Wiki as well. My apache id is
> "vrushali".
>
> thanks
> Vrushali
>
>
> On Mon, Sep 11, 2017 at 3:33 PM, Subru Krishnan  wrote:
>
> > Hi,
> >
> > Can I get access to the Hadoop wiki. My confluence is "subru".
> >
> > TIA.
> >
> > -Subru
> >
>

Re: Access to confluence wiki

2017-09-11 Thread Vrushali C 
I would like to get access to the Hadoop Wiki as well. My apache id is
"vrushali".

thanks
Vrushali


On Mon, Sep 11, 2017 at 3:33 PM, Subru Krishnan  wrote:

> Hi,
>
> Can I get access to the Hadoop wiki. My confluence is "subru".
>
> TIA.
>
> -Subru
>

Access to confluence wiki

2017-09-11 Thread Subru Krishnan 
Hi,

Can I get access to the Hadoop wiki. My confluence is "subru".

TIA.

-Subru

Release 2.9.0 update

2017-09-11 Thread Arun Suresh 
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 of YARN features currently in the roadmap and based on
offline discussions with Vinod et. al, We have decided to add a production
sponsor criteria for the features listed. Essentially, what it means is
that we will favor inclusion of a feature in the 2.9.0 release if it is
associated with an immediate production deployment requirement, failing
which we would recommend moving it to the next major release. For eg., as
decided by the community for HDFS Erasure coding. This is also in
consideration with advanced stages of 3.0.0 and 3.1.0 planning.

In summary. We would like to invite sponsors for each of the features in
the roadmap wiki. Kindly do so by filling in the "Production Sponsor"
column on the table:
https://cwiki.apache.org/confluence/display/HADOOP/Roadmap#Roadmap-Plannedfeatures:.2


Thanks
Arun / Subru

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

2017-09-11 Thread Chris Douglas 
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.8.2 never exists.

...we're not going to document security implications- which include
escalations to root- because we don't have _any_ documentation? Why
don't we backport the documentation?

> - New docker container support (replace of old DockerContainerExectutor) is 
> still an alpha feature now which doesn't highlight in 2.8 major 
> features/improvement (http://hadoop.apache.org/docs/r2.8.0/index.html). So 
> adding documentation here is also not a blocker.

YARN-6622 is *documenting* the fact that this is an alpha feature and
that it shouldn't be enabled in secure environments. How are users
supposed to make this determination without it?

> Vote still continue until a real blocker comes.

Soright. I remain -1. -C

> 
> From: Chris Douglas 
> Sent: Monday, September 11, 2017 12:00 PM
> To: Junping Du
> Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev; 
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
> Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)
>
> -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 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/DockerContainerExecutor.html)
>>  without mentioning docker support is experimental. We may need to fix that 
>> as well in following releases.
>>
>> I can also add it (mentioning docker container support feature is 
>> experimental) to release message in public website just like previous 
>> release we call 2.7.0/2.8.0 as non-production release.
>>
>> I think vote should continue until we could find a real blocker.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> 
>> From: Miklos Szegedi 
>> Sent: Monday, September 11, 2017 10:07 AM
>> To: Mingliang Liu
>> Cc: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org; 
>> yarn-...@hadoop.apache.org; junping_du; Junping Du
>> Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)
>>
>> 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-src.tar.gz file and checked the md5 value
>> - Build package using maven (skipping tests) with Java 8
>> - Spin up a test cluster in Docker containers having 1 master node (NN/RM) 
>> and 3 slave nodes (DN/NM)
>> - Operate the basic HDFS/YARN operations from command line, both client and 
>> admin
>> - Check NN/RM Web UI
>> - Run distcp to copy files from/to local and HDFS
>> - Run hadoop mapreduce examples: grep and wordcount
>> - Check the HDFS service logs
>>
>> All looked good to me.
>>
>> Mingliang
>>
>>> On Sep 10, 2017, at 5:00 PM, Junping Du 
>>> > wrote:
>>>
>>> Hi folks,
>>> With fix of HADOOP-14842 get in, I've created our first release 
>>> candidate (RC0) for Apache Hadoop 2.8.2.
>>>
>>> Apache Hadoop 2.8.2 is the first stable release of Hadoop 2.8 line and 
>>> will be the latest stable/production release for Apache Hadoop - it 
>>> includes 305 new fixed issues since 2.8.1 and 63 fixes are marked as 
>>> blocker/critical issues.
>>>
>>>  More information about the 2.8.2 release plan can be found here: 
>>> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release
>>>
>>>  New RC is available at: 
>>> http://home.apache.org/~junping_du/hadoop-2.8.2-RC0
>>>
>>>  The RC tag in git is: release-2.8.2-RC0, and the latest commit id is: 
>>> e6597fe3000b06847d2bf55f2bab81770f4b2505
>>>
>>>  The maven artifacts are available via 
>>> repository.apache.org at: 
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1062
>>>
>>>  Please try the release and vote; the vote will run for the usual 5 
>>> days, ending on 09/15/2017 5pm PST time.
>>>
>>> Thanks,
>>>
>>> Junping
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: 
>>

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

2017-09-11 Thread Junping Du 
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 of old DockerContainerExectutor) is 
still an alpha feature now which doesn't highlight in 2.8 major 
features/improvement (http://hadoop.apache.org/docs/r2.8.0/index.html). So 
adding documentation here is also not a blocker.

Vote still continue until a real blocker comes.

Thanks,

Junping


From: Chris Douglas 
Sent: Monday, September 11, 2017 12:00 PM
To: Junping Du
Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

-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 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/DockerContainerExecutor.html)
>  without mentioning docker support is experimental. We may need to fix that 
> as well in following releases.
>
> I can also add it (mentioning docker container support feature is 
> experimental) to release message in public website just like previous release 
> we call 2.7.0/2.8.0 as non-production release.
>
> I think vote should continue until we could find a real blocker.
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: Miklos Szegedi 
> Sent: Monday, September 11, 2017 10:07 AM
> To: Mingliang Liu
> Cc: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org; 
> yarn-...@hadoop.apache.org; junping_du; Junping Du
> Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)
>
> 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-src.tar.gz file and checked the md5 value
> - Build package using maven (skipping tests) with Java 8
> - Spin up a test cluster in Docker containers having 1 master node (NN/RM) 
> and 3 slave nodes (DN/NM)
> - Operate the basic HDFS/YARN operations from command line, both client and 
> admin
> - Check NN/RM Web UI
> - Run distcp to copy files from/to local and HDFS
> - Run hadoop mapreduce examples: grep and wordcount
> - Check the HDFS service logs
>
> All looked good to me.
>
> Mingliang
>
>> On Sep 10, 2017, at 5:00 PM, Junping Du 
>> > wrote:
>>
>> Hi folks,
>> With fix of HADOOP-14842 get in, I've created our first release 
>> candidate (RC0) for Apache Hadoop 2.8.2.
>>
>> Apache Hadoop 2.8.2 is the first stable release of Hadoop 2.8 line and 
>> will be the latest stable/production release for Apache Hadoop - it includes 
>> 305 new fixed issues since 2.8.1 and 63 fixes are marked as blocker/critical 
>> issues.
>>
>>  More information about the 2.8.2 release plan can be found here: 
>> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release
>>
>>  New RC is available at: 
>> http://home.apache.org/~junping_du/hadoop-2.8.2-RC0
>>
>>  The RC tag in git is: release-2.8.2-RC0, and the latest commit id is: 
>> e6597fe3000b06847d2bf55f2bab81770f4b2505
>>
>>  The maven artifacts are available via 
>> repository.apache.org at: 
>> https://repository.apache.org/content/repositories/orgapachehadoop-1062
>>
>>  Please try the release and vote; the vote will run for the usual 5 
>> days, ending on 09/15/2017 5pm PST time.
>>
>> Thanks,
>>
>> Junping
>>
>
>
> -
> To unsubscribe, e-mail: 
> mapreduce-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: 
> mapreduce-dev-h...@hadoop.apache.org
>
>

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands,

Re: [VOTE] Merge yarn-native-services branch into trunk

2017-09-11 Thread Andrew Wang 
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, after talking with other team
> members, we are fine to drop  this from beta,
>
> And we want to target this for GA.
> I’m withdrawing this vote and will start afresh vote later for GA.
> Thanks all who voted this effort !
>
> Thanks,
> Jian
>
>
> > On Sep 7, 2017, at 3:59 PM, Andrew Wang 
> wrote:
> >
> > Hi folks,
> >
> > This vote closes today. I see a -1 from Allen on inclusion in beta1. I
> see
> > there's active fixing going on, but given that we're one week out from
> RC0,
> > I think we should drop this from beta1.
> >
> > Allen, Jian, others, is this reasonable? What release should we retarget
> > this for? I don't have a sense for how much work there is left to do, but
> > as a reminder, we're planning GA for Nov 1st, and 3.1.0 for January.
> >
> > Best,
> > Andrew
> >
> > On Wed, Sep 6, 2017 at 10:19 AM, Jian He  wrote:
> >
> >>>  Please correct me if I’m wrong, but the current summary of the
> >> branch, post these changes, looks like:
> >> Sorry for confusion, I was actively writing the formal documentation for
> >> how to use/how it works etc. and will post soon in a few hours.
> >>
> >>
> >>> On Sep 6, 2017, at 10:15 AM, Allen Wittenauer <
> a...@effectivemachines.com>
> >> wrote:
> >>>
> >>>
>  On Sep 5, 2017, at 6:23 PM, Jian He  wrote:
> 
> >If it doesn’t have all the bells and whistles, then it shouldn’t
> >> be on port 53 by default.
>  Sure, I’ll change the default port to not use 53 and document it.
> >*how* is it getting launched on a privileged port? It sounds like
> >> the expectation is to run “command” as root.   *ALL* of the previous
> >> daemons in Hadoop that needed a privileged port used jsvc.  Why isn’t
> this
> >> one? These questions matter from a security standpoint.
>  Yes, it is running as “root” to be able to use the privileged port.
> The
> >> DNS server is not yet integrated with the hadoop script.
> 
> > Check the output.  It’s pretty obviously borked:
>  Thanks for pointing out. Missed this when rebasing onto trunk.
> >>>
> >>>
> >>>  Please correct me if I’m wrong, but the current summary of the
> >> branch, post these changes, looks like:
> >>>
> >>>  * A bunch of mostly new Java code that may or may not have
> >> javadocs (post-revert YARN-6877, still working out HADOOP-14835)
> >>>  * ~1/3 of the docs are roadmap/TBD
> >>>  * ~1/3 of the docs are for an optional DNS daemon that has
> >> no end user hook to start it
> >>>  * ~1/3 of the docs are for a REST API that comes from some
> >> undefined daemon (apiserver?)
> >>>  * Two new, but undocumented, subcommands to yarn
> >>>  * There are no docs for admins or users on how to actually
> >> start or use this completely new/separate/optional feature
> >>>
> >>>  How are outside people (e.g., non-branch committers) supposed to
> >> test this new feature under these conditions?
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
> >> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
> >>
> >>
>
>

[jira] [Resolved] (HADOOP-14697) Analyze the properties files which need to be included/excluded from hadoop-client-runtime and hadoop-client-minicluster

2017-09-11 Thread Bharat Viswanadham (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-14697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharat Viswanadham resolved HADOOP-14697.
-
Resolution: Duplicate

This is being taken care in 
Thanks [~busbey] for handling 
this.[https://issues.apache.org/jira/browse/HADOOP-14089]

> Analyze the properties files which need to be included/excluded from 
> hadoop-client-runtime and hadoop-client-minicluster
> 
>
> Key: HADOOP-14697
> URL: https://issues.apache.org/jira/browse/HADOOP-14697
> Project: Hadoop Common
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>
> about.html
> capacity-scheduler.xml
> catalog.cat
> container-log4j.properties
> hdfs-default.xml
> java.policy
> javaee_5.xsd
> javaee_6.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> jdtCompilerAdapter.jar
> jsp_2_1.xsd
> jsp_2_2.xsd
> krb5.conf
> log4j.properties
> plugin.properties
> plugin.xml
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-common_3_0.xsd
> xml.xsd
> This issue is raised from [https://issues.apache.org/jira/browse/HADOOP-14685]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

2017-09-11 Thread Chris Douglas 
-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 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/DockerContainerExecutor.html)
>  without mentioning docker support is experimental. We may need to fix that 
> as well in following releases.
>
> I can also add it (mentioning docker container support feature is 
> experimental) to release message in public website just like previous release 
> we call 2.7.0/2.8.0 as non-production release.
>
> I think vote should continue until we could find a real blocker.
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: Miklos Szegedi 
> Sent: Monday, September 11, 2017 10:07 AM
> To: Mingliang Liu
> Cc: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org; 
> yarn-...@hadoop.apache.org; junping_du; Junping Du
> Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)
>
> 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-src.tar.gz file and checked the md5 value
> - Build package using maven (skipping tests) with Java 8
> - Spin up a test cluster in Docker containers having 1 master node (NN/RM) 
> and 3 slave nodes (DN/NM)
> - Operate the basic HDFS/YARN operations from command line, both client and 
> admin
> - Check NN/RM Web UI
> - Run distcp to copy files from/to local and HDFS
> - Run hadoop mapreduce examples: grep and wordcount
> - Check the HDFS service logs
>
> All looked good to me.
>
> Mingliang
>
>> On Sep 10, 2017, at 5:00 PM, Junping Du 
>> > wrote:
>>
>> Hi folks,
>> With fix of HADOOP-14842 get in, I've created our first release 
>> candidate (RC0) for Apache Hadoop 2.8.2.
>>
>> Apache Hadoop 2.8.2 is the first stable release of Hadoop 2.8 line and 
>> will be the latest stable/production release for Apache Hadoop - it includes 
>> 305 new fixed issues since 2.8.1 and 63 fixes are marked as blocker/critical 
>> issues.
>>
>>  More information about the 2.8.2 release plan can be found here: 
>> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release
>>
>>  New RC is available at: 
>> http://home.apache.org/~junping_du/hadoop-2.8.2-RC0
>>
>>  The RC tag in git is: release-2.8.2-RC0, and the latest commit id is: 
>> e6597fe3000b06847d2bf55f2bab81770f4b2505
>>
>>  The maven artifacts are available via 
>> repository.apache.org at: 
>> https://repository.apache.org/content/repositories/orgapachehadoop-1062
>>
>>  Please try the release and vote; the vote will run for the usual 5 
>> days, ending on 09/15/2017 5pm PST time.
>>
>> Thanks,
>>
>> Junping
>>
>
>
> -
> To unsubscribe, e-mail: 
> mapreduce-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: 
> mapreduce-dev-h...@hadoop.apache.org
>
>

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

2017-09-11 Thread Junping Du 
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/DockerContainerExecutor.html)
 without mentioning docker support is experimental. We may need to fix that as 
well in following releases.

I can also add it (mentioning docker container support feature is experimental) 
to release message in public website just like previous release we call 
2.7.0/2.8.0 as non-production release.

I think vote should continue until we could find a real blocker.


Thanks,


Junping



From: Miklos Szegedi 
Sent: Monday, September 11, 2017 10:07 AM
To: Mingliang Liu
Cc: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org; 
yarn-...@hadoop.apache.org; junping_du; Junping Du
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

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-src.tar.gz file and checked the md5 value
- Build package using maven (skipping tests) with Java 8
- Spin up a test cluster in Docker containers having 1 master node (NN/RM) and 
3 slave nodes (DN/NM)
- Operate the basic HDFS/YARN operations from command line, both client and 
admin
- Check NN/RM Web UI
- Run distcp to copy files from/to local and HDFS
- Run hadoop mapreduce examples: grep and wordcount
- Check the HDFS service logs

All looked good to me.

Mingliang

> On Sep 10, 2017, at 5:00 PM, Junping Du 
> > wrote:
>
> Hi folks,
> With fix of HADOOP-14842 get in, I've created our first release candidate 
> (RC0) for Apache Hadoop 2.8.2.
>
> Apache Hadoop 2.8.2 is the first stable release of Hadoop 2.8 line and 
> will be the latest stable/production release for Apache Hadoop - it includes 
> 305 new fixed issues since 2.8.1 and 63 fixes are marked as blocker/critical 
> issues.
>
>  More information about the 2.8.2 release plan can be found here: 
> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release
>
>  New RC is available at: 
> http://home.apache.org/~junping_du/hadoop-2.8.2-RC0
>
>  The RC tag in git is: release-2.8.2-RC0, and the latest commit id is: 
> e6597fe3000b06847d2bf55f2bab81770f4b2505
>
>  The maven artifacts are available via 
> repository.apache.org at: 
> https://repository.apache.org/content/repositories/orgapachehadoop-1062
>
>  Please try the release and vote; the vote will run for the usual 5 days, 
> ending on 09/15/2017 5pm PST time.
>
> Thanks,
>
> Junping
>


-
To unsubscribe, e-mail: 
mapreduce-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: 
mapreduce-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

2017-09-11 Thread Brahma Reddy Battula 
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 first release
> candidate (RC0) for Apache Hadoop 2.8.2.
>
>  Apache Hadoop 2.8.2 is the first stable release of Hadoop 2.8 line
> and will be the latest stable/production release for Apache Hadoop - it
> includes 305 new fixed issues since 2.8.1 and 63 fixes are marked as
> blocker/critical issues.
>
>   More information about the 2.8.2 release plan can be found here:
> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release
>
>   New RC is available at:
> http://home.apache.org/~junping_du/hadoop-2.8.2-RC0
>
>   The RC tag in git is: release-2.8.2-RC0, and the latest commit id
> is: e6597fe3000b06847d2bf55f2bab81770f4b2505
>
>   The maven artifacts are available via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1062
>
>   Please try the release and vote; the vote will run for the usual 5
> days, ending on 09/15/2017 5pm PST time.
>
> Thanks,
>
> Junping
>
> --



--Brahma Reddy Battula

[jira] [Created] (HADOOP-14859) Shaded AWS library stops s3a recognising ConnectTimeoutException

2017-09-11 Thread Steve Loughran (JIRA) 
Steve Loughran created HADOOP-14859:
---

 Summary: Shaded AWS library stops s3a recognising 
ConnectTimeoutException
 Key: HADOOP-14859
 URL: https://issues.apache.org/jira/browse/HADOOP-14859
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Steve Loughran
Priority: Minor


S3AUtils.translateException() has special  handling for {{ConnectException}} 
and {{SocketTimeoutException}}, as they are both subclasses of 
InterruptedIOException, but for which special handling is useful for tuning how 
to react to the failures.

With the move to the shaded AWS SDK, the exception unwinding code doesn't work 
properly any more: it needs to look for a shaded 
com.amazonaws.thirdparty.apache.http packaged entry.

To restore that behaviour, either the code needs to look for the specific 
shaded class, or just look for any subclass of IOE called 
{{ConnectTimeoutException}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

2017-09-11 Thread Apache Jenkins Server 
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.




-1 overall


The following subsystems voted -1:
findbugs unit


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

FindBugs :

   module:hadoop-hdfs-project/hadoop-hdfs 
   Format-string method String.format(String, Object[]) called with format 
string "File %s could only be written to %d of the %d %s. There are %d 
datanode(s) running and %s node(s) are excluded in this operation." wants 6 
arguments but is given 7 in 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(String,
 int, Node, Set, long, List, byte, BlockType, ErasureCodingPolicy, EnumSet) At 
BlockManager.java:with format string "File %s could only be written to %d of 
the %d %s. There are %d datanode(s) running and %s node(s) are excluded in this 
operation." wants 6 arguments but is given 7 in 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(String,
 int, Node, Set, long, List, byte, BlockType, ErasureCodingPolicy, EnumSet) At 
BlockManager.java:[line 2076] 

FindBugs :

   
module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
 
   Hard coded reference to an absolute pathname in 
org.apache.hadoop.yarn.server.nodemanager.containermanager.linux.runtime.DockerLinuxContainerRuntime.launchContainer(ContainerRuntimeContext)
 At DockerLinuxContainerRuntime.java:absolute pathname in 
org.apache.hadoop.yarn.server.nodemanager.containermanager.linux.runtime.DockerLinuxContainerRuntime.launchContainer(ContainerRuntimeContext)
 At DockerLinuxContainerRuntime.java:[line 490] 

Failed junit tests :

   hadoop.ha.TestZKFailoverController 
   hadoop.hdfs.TestReconstructStripedFile 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure150 
   hadoop.hdfs.TestLeaseRecoveryStriped 
   hadoop.hdfs.TestClientProtocolForPipelineRecovery 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure050 
   hadoop.hdfs.server.blockmanagement.TestReplicationPolicyWithNodeGroup 
   hadoop.hdfs.server.datanode.TestDataNodeVolumeFailure 
   hadoop.hdfs.server.blockmanagement.TestBlockStatsMXBean 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure180 
   hadoop.hdfs.TestFileAppendRestart 
   hadoop.hdfs.server.namenode.TestNamenodeCapacityReport 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure030 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure160 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure080 
   hadoop.hdfs.TestReadStripedFileWithMissingBlocks 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure140 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure090 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure040 
   hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure010 
   hadoop.hdfs.server.blockmanagement.TestBlockManager 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure120 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure020 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure200 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure110 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure100 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure070 
   hadoop.hdfs.protocol.datatransfer.sasl.TestSaslDataTransfer 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure190 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure000 
   hadoop.fs.http.client.TestHttpFSFWithWebhdfsFileSystem 
   
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation 
   hadoop.yarn.server.resourcemanager.scheduler.TestAbstractYarnScheduler 
   hadoop.yarn.server.router.webapp.TestRouterWebServiceUtil 
   hadoop.mapreduce.v2.hs.webapp.TestHSWebApp 
   hadoop.yarn.sls.TestReservationSystemInvariants 
   hadoop.yarn.sls.TestSLSRunner 

Timed out junit tests :

   org.apache.hadoop.hdfs.TestWriteReadStripedFile 
  

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/520/artifact/out/diff-compile-cc-root.txt
  [4.0K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/520/artifact/out/diff-compile-javac-root.txt
  [292K]

   checkstyle:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/520/artifact/out/diff-checkstyle-root.txt
  [17M]

   pylint:

[jira] [Created] (HADOOP-14858) Why Yarn crashes ?

2017-09-11 Thread anikad ayman (JIRA) 
anikad ayman created HADOOP-14858:
-

 Summary: Why Yarn crashes ?
 Key: HADOOP-14858
 URL: https://issues.apache.org/jira/browse/HADOOP-14858
 Project: Hadoop Common
  Issue Type: Bug
 Environment: Production 
Reporter: anikad ayman
 Fix For: 2.7.0


During MapReduce processing, Yarn did crash and the processing of jobs had 
stopped. I successed to back the processing after killing the first job which 
was running, but after some minutes, another crach thatI solved by killing the 
second job wich was running.

We are looking for reasons of this crach that we had several times before 
(between one to two times in a month)

In ressource manager logs , I find this messages repeated from the beggining of 
the crach until the killing of the jobs:

2017-08-25 03:51:58,815 WARN org.apache.hadoop.ipc.Server: Large response size 
4739374 for call 
org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplications from 
10.135.8.101:38352 Call#33361 Retry#0
2017-08-25 03:53:39,255 WARN org.apache.hadoop.ipc.Server: Large response size 
4739374 for call 
org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplications from 
10.135.8.101:38456 Call#33364 Retry#0
2017-08-25 03:55:19,700 WARN org.apache.hadoop.ipc.Server: Large response size 
4739374 for call 
org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplications from 
10.135.8.101:38556 Call#33367 Retry#0
2017-08-25 03:57:00,262 WARN org.apache.hadoop.ipc.Server: Large response size 
4739374 for call 
org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplications from 
10.135.8.101:38674 Call#33370 Retry#0
2017-08-25 03:58:40,687 WARN org.apache.hadoop.ipc.Server: Large response size 
4739374 for call 
org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplications from 
10.135.8.101:38804 Call#33373 Retry#0
.
.
.
2017-08-25 11:02:44,086 WARN org.apache.hadoop.ipc.Server: Large response size 
4751251 for call 
org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplications from 
10.135.8.101:39778 Call#34159 Retry#0
2017-08-25 11:02:47,933 WARN org.apache.hadoop.ipc.Server: Large response size 
4751251 for call 
org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplications from 
10.135.8.101:39778 Call#34162 Retry#0
2017-08-25 11:03:06,800 WARN org.apache.hadoop.ipc.Server: Large response size 
4751251 for call 
org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplications from 
10.135.8.101:39814 Call#34165 Retry#0

NB: We still get this warning from time to another, we still wondring if it 
concerns a connexion between the node manager (10.135.8.101) and the ressource 
manager, or something else ?

For the node manager logs, I find theses messages :

2017-08-25 03:51:54,396 INFO 
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl:
 Memory usage of ProcessTree 98201 for container-id 
container_e41_1500982512144_36679_01_000382: 1.4 GB of 10 GB physical memory 
used; 10.1 GB of 21 GB virtual memory used
2017-08-25 03:51:54,791 INFO 
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl:
 Memory usage of ProcessTree 112912 for container-id 
container_e41_1500982512144_36679_01_000387: 2.3 GB of 10 GB physical memory 
used; 10.1 GB of 21 GB virtual memory used
2017-08-25 03:51:55,177 INFO 
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl:
 Memory usage of ProcessTree 105848 for container-id 
container_e41_1500982512144_36627_01_001644: 619.4 MB of 10 GB physical memory 
used; 10.1 GB of 21 GB virtual memory used
2017-08-25 03:51:58,938 INFO 
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl:
 Memory usage of ProcessTree 98201 for container-id 
container_e41_1500982512144_36679_01_000382: 1.4 GB of 10 GB physical memory 
used; 10.1 GB of 21 GB virtual memory used
.
.
.
2017-08-25 11:05:40,104 INFO 
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl:
 Memory usage of ProcessTree 112912 for container-id 
container_e41_1500982512144_36679_01_000387: 1.1 GB of 10 GB physical memory 
used; 10.1 GB of 21 GB virtual memory used
2017-08-25 11:05:40,493 INFO 
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl:
 Memory usage of ProcessTree 105848 for container-id 
container_e41_1500982512144_36627_01_001644: 648.4 MB of 10 GB physical memory 
used; 10.1 GB of 21 GB virtual memory used
2017-08-25 11:05:43,867 INFO 
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl:
 Memory usage of ProcessTree 98201 for container-id 
container_e41_1500982512144_36679_01_000382: 1.1 GB of 10 GB physical memory 
used; 10.1 GB of 21 GB virtual memory used
2017-08-25 11:05:45,040 INFO

[jira] [Resolved] (HADOOP-7269) S3 Native should allow customizable file meta-data (headers)

2017-09-11 Thread Steve Loughran (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran resolved HADOOP-7269.

Resolution: Won't Fix

Resolving as a WONTFIX as we are going to cull s3n. however, being able to set 
headers is something I think I'd like to do, somehow. Maybe we could do it with 
the new builder API for opening fileswe could let callers declare the 
headers as options when the file is opened. 

> S3 Native should allow customizable file meta-data (headers)
> 
>
> Key: HADOOP-7269
> URL: https://issues.apache.org/jira/browse/HADOOP-7269
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: fs/s3
>Reporter: Nicholas Telford
>Assignee: Nicholas Telford
>Priority: Minor
> Attachments: 
> 0001-Added-support-for-metadata-to-be-applied-to-objects-.patch, 
> 0002-Added-check-that-metadata-was-set-to-unit-test.patch, 
> 7269-combined-002.patch, 7269-combined.patch, 7269-combined-proper.patch, 
> HADOOP-7269-S3-metadata-001.diff, HADOOP-7269-S3-metadata-002.diff, 
> HADOOP-7269-S3-metadata-003.diff
>
>
> The S3 Native FileSystem currently writes all files with a set of default 
> headers:
>  * Content-Type: binary/octet-stream
>  * Content-Length: 
>  * Content-MD5: 
> This is a good start, however many applications would benefit from the 
> ability to customize (for example) the Content-Type and Expires headers for 
> the file. Ideally the implementation should be abstract enough to customize 
> all of the available S3 headers and provide a facility for other FileSystems 
> to specify optional file metadata.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org