Failed: YARN-2818 PreCommit Build #5751

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2818
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5751/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3127 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679805/YARN-2818.1.patch
  against trunk revision 80d7d18.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5751//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5751//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
e5200cc84534f047a259c968c1400b6d54f0def1 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8769723 bytes
Compression is 0.0%
Took 3.1 sec
Description set: YARN-2818
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2753 PreCommit Build #5752

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2753
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5752/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3500 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679811/YARN-2753.006.patch
  against trunk revision 80d7d18.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5752//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5752//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
439e45d3552be784f944ec6a6ea7db1940b5232a logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 20 artifacts
Archive block size is 32768
Received 0 blocks and 9271984 bytes
Compression is 0.0%
Took 2.8 sec
Description set: YARN-2753
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2818 PreCommit Build #5754

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2818
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5754/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3127 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679878/YARN-2818.2.patch
  against trunk revision 10f9f51.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5754//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5754//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
9b320a70cf48719912e0dbdb520627ffc24e9fd8 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8762150 bytes
Compression is 0.0%
Took 2.9 sec
Description set: YARN-2818
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2780 PreCommit Build #5753

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2780
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5753/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3307 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12679871/YARN-2780.v2.201411061601.txt
  against trunk revision 10f9f51.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5753//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5753//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
b81f401b1e6d428359788594c4b9ded1ee5f40e1 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8968802 bytes
Compression is 0.0%
Took 4.2 sec
Description set: YARN-2780
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Some information required related to Hadoop documentation developement

[Naganarasimha G R (Naga)]

Hi All,
I wanted to know the following related to Hadoop Documentation

  1.  what and how are these *.vm files(format) used in Hadoop [Hdfs and Yarn] 
documentation ?
  2.  Does vm files stand for velocity macro?
  3.  Do we use some kind of editor to create/update these files ?
  4.  Are there any guidelines for writing Hadoop/YARN documentation ?
  5.  Are these documentation pages built if " -Pdocs " parameters are provided 
during "mvn install" ? If so which Pom is responsible for building the html 
files ? Basically how to modify and test the generated html files?
  6.  From earlier patches  (ex : yarn 1696) i figured out that to add new 
page(in yarn documentation) we can add a *.vm file in 
"hadoop-yarn-project\hadoop-yarn\hadoop-yarn-site\src\site\apt" and make entry 
in "hadoop-project\src\site\site.xml"  for the new page? Is that sufficient or 
anything else needs to be taken care?


Regards,

Naga



Huawei Technologies Co., Ltd.
Phone:
Fax:
Mobile:  +91 9980040283
Email: naganarasimh...@huawei.com
Huawei Technologies Co., Ltd.
Bantian, Longgang District,Shenzhen 518129, P.R.China
http://www.huawei.com

Failed: YARN-2647 PreCommit Build #5755

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2647
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5755/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 19 lines...]
[PreCommit-YARN-Build] $ /bin/bash /tmp/hudson6483090422474010002.sh
Running in Jenkins mode


==
==
Testing patch for YARN-2647.
==
==


HEAD is now at 10f9f51 MAPREDUCE-5960. JobSubmitter's check whether job.jar is 
local is incorrect with no authority in job jar path. Contributed by Gera 
Shegalov
Switched to branch 'trunk'
Your branch is up-to-date with 'origin/trunk'.
Current branch trunk is up to date.
YARN-2647 patch is being downloaded at Thu Nov  6 18:01:01 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12679850/0008-YARN-2647.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679850/0008-YARN-2647.patch
  against trunk revision 10f9f51.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5755//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
8679e4df928189094d0cac9d86101f18ce007898 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Description set: MAPREDUCE-5960
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2819) NPE in ATS Timeline Domains when upgrading from 2.4 to 2.6

[Gopal V (JIRA)]

Gopal V created YARN-2819:
-

 Summary: NPE in ATS Timeline Domains when upgrading from 2.4 to 2.6
 Key: YARN-2819
 URL: https://issues.apache.org/jira/browse/YARN-2819
 Project: Hadoop YARN
  Issue Type: Bug
  Components: timelineserver
Affects Versions: 2.6.0
Reporter: Gopal V


{code}
Caused by: java.lang.NullPointerException
at java.lang.String.(String.java:554)
at 
org.apache.hadoop.yarn.server.timeline.LeveldbTimelineStore.put(LeveldbTimelineStore.java:873)
at 
org.apache.hadoop.yarn.server.timeline.LeveldbTimelineStore.put(LeveldbTimelineStore.java:1014)
at 
org.apache.hadoop.yarn.server.timeline.TimelineDataManager.postEntities(TimelineDataManager.java:330)
at 
org.apache.hadoop.yarn.server.timeline.webapp.TimelineWebServices.postEntities(TimelineWebServices.java:260)
{code}

triggered by 

{code}
entity.getRelatedEntities();
...
} else {
  byte[] domainIdBytes = db.get(createDomainIdKey(
  relatedEntityId, relatedEntityType, relatedEntityStartTime));
  // This is the existing entity
  String domainId = new String(domainIdBytes);
  if (!domainId.equals(entity.getDomainId())) {
{code}

The new String(domainIdBytes); throws an NPE.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Some information required related to Hadoop documentation developement

[Masatake Iwasaki]

Hi Naga,


>   1.  what and how are these *.vm files(format) used in Hadoop [Hdfs and 
Yarn] documentation ?
>   2.  Does vm files stand for velocity macro?

Velocity macro is used for variable substitution as far as I know.
For example::

  ---
  YARN Timeline Server
  ---
  ---
  ${maven.build.timestamp}

Though many of dosc uses APT format ( 
http://maven.apache.org/doxia/references/apt-format.html ),
you can also use markdown.
See 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/markdown
for example.


>  5.  Are these documentation pages built if " -Pdocs " parameters are provided during 
"mvn install" ? If so which Pom is responsible for building the html files ? Basically how 
to modify and test the generated html files?

Run "mvn site" to build site docs.
Running "mvn site site:stage -DstagingDirectory=/var/www/html/hadoop-site"
puts built docs to specifiled path.


>  6.  From earlier patches  (ex : yarn 1696) i figured out that to add new page(in yarn 
documentation) we can add a *.vm file in 
"hadoop-yarn-project\hadoop-yarn\hadoop-yarn-site\src\site\apt" and make entry in 
"hadoop-project\src\site\site.xml"  for the new page? Is that sufficient or anything else 
needs to be taken care?

I think it is sufficient.


Masatake Iwasaki


(11/6/14, 9:51), Naganarasimha G R (Naga) wrote:

Hi All,
I wanted to know the following related to Hadoop Documentation

   1.  what and how are these *.vm files(format) used in Hadoop [Hdfs and Yarn] 
documentation ?
   2.  Does vm files stand for velocity macro?
   3.  Do we use some kind of editor to create/update these files ?
   4.  Are there any guidelines for writing Hadoop/YARN documentation ?
   5.  Are these documentation pages built if " -Pdocs " parameters are provided during 
"mvn install" ? If so which Pom is responsible for building the html files ? Basically 
how to modify and test the generated html files?
   6.  From earlier patches  (ex : yarn 1696) i figured out that to add new page(in yarn 
documentation) we can add a *.vm file in 
"hadoop-yarn-project\hadoop-yarn\hadoop-yarn-site\src\site\apt" and make entry in 
"hadoop-project\src\site\site.xml"  for the new page? Is that sufficient or anything else 
needs to be taken care?


Regards,

Naga



Huawei Technologies Co., Ltd.
Phone:
Fax:
Mobile:  +91 9980040283
Email: naganarasimh...@huawei.com
Huawei Technologies Co., Ltd.
Bantian, Longgang District,Shenzhen 518129, P.R.China
http://www.huawei.com

Re: Some information required related to Hadoop documentation developement

[Masatake Iwasaki]

Hi Naga,


>   1.  what and how are these *.vm files(format) used in Hadoop [Hdfs and 
Yarn] documentation ?
>   2.  Does vm files stand for velocity macro?

Velocity macro is used for variable substitution as far as I know.
For example::

  ---
  YARN Timeline Server
  ---
  ---
  ${maven.build.timestamp}

Though many of dosc uses APT format ( 
http://maven.apache.org/doxia/references/apt-format.html ),
you can also use markdown.
See 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/markdown
for example.


>  5.  Are these documentation pages built if " -Pdocs " parameters are provided during 
"mvn install" ? If so which Pom is responsible for building the html files ? Basically how 
to modify and test the generated html files?

Run "mvn site" to build site docs.
Running "mvn site site:stage -DstagingDirectory=/var/www/html/hadoop-site"
puts built docs to specifiled path.


>  6.  From earlier patches  (ex : yarn 1696) i figured out that to add new page(in yarn 
documentation) we can add a *.vm file in 
"hadoop-yarn-project\hadoop-yarn\hadoop-yarn-site\src\site\apt" and make entry in 
"hadoop-project\src\site\site.xml"  for the new page? Is that sufficient or anything else 
needs to be taken care?

I think it is sufficient.


Masatake Iwasaki


(11/6/14, 9:51), Naganarasimha G R (Naga) wrote:> Hi All,
> I wanted to know the following related to Hadoop Documentation
>
>1.  what and how are these *.vm files(format) used in Hadoop [Hdfs and 
Yarn] documentation ?
>2.  Does vm files stand for velocity macro?
>3.  Do we use some kind of editor to create/update these files ?
>4.  Are there any guidelines for writing Hadoop/YARN documentation ?
>5.  Are these documentation pages built if " -Pdocs " parameters are provided during 
"mvn install" ? If so which Pom is responsible for building the html files ? Basically how 
to modify and test the generated html files?
>6.  From earlier patches  (ex : yarn 1696) i figured out that to add new page(in yarn 
documentation) we can add a *.vm file in 
"hadoop-yarn-project\hadoop-yarn\hadoop-yarn-site\src\site\apt" and make entry in 
"hadoop-project\src\site\site.xml"  for the new page? Is that sufficient or anything else 
needs to be taken care?
>
>
> Regards,
>
> Naga
>
>
>
> Huawei Technologies Co., Ltd.
> Phone:
> Fax:
> Mobile:  +91 9980040283
> Email: naganarasimh...@huawei.com
> Huawei Technologies Co., Ltd.
> Bantian, Longgang District,Shenzhen 518129, P.R.China
> http://www.huawei.com
>

[jira] [Created] (YARN-2820) Improve FileSystemRMStateStore update failure exception handling to not shutdown RM.

[zhihai xu (JIRA)]

zhihai xu created YARN-2820:
---

 Summary: Improve FileSystemRMStateStore update failure exception 
handling to not  shutdown RM.
 Key: YARN-2820
 URL: https://issues.apache.org/jira/browse/YARN-2820
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: resourcemanager
Affects Versions: 2.5.0
Reporter: zhihai xu
Assignee: zhihai xu


When we use FileSystemRMStateStore as yarn.resourcemanager.store.class, We saw 
the following IOexception cause the RM shutdown.

{code}
FATAL
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Received a 
org.apache.hadoop.yarn.server.resourcemanager.RMFatalEvent of type 
STATE_STORE_OP_FAILED. Cause: 
java.io.IOException: Unable to close file because the last block does not have 
enough number of replicas. 
at 
org.apache.hadoop.hdfs.DFSOutputStream.completeFile(DFSOutputStream.java:2132) 
at org.apache.hadoop.hdfs.DFSOutputStream.close(DFSOutputStream.java:2100) 
at 
org.apache.hadoop.fs.FSDataOutputStream$PositionCache.close(FSDataOutputStream.java:70)
 
at org.apache.hadoop.fs.FSDataOutputStream.close(FSDataOutputStream.java:103) 
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.writeFile(FileSystemRMStateStore.java:522)
 
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.updateFile(FileSystemRMStateStore.java:534)
 
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.updateApplicationAttemptStateInternal(FileSystemRMStateStore.java:389)
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.RMStateStore.handleStoreEvent(RMStateStore.java:675)
 
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.RMStateStore$ForwardingEventHandler.handle(RMStateStore.java:766)
 
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.RMStateStore$ForwardingEventHandler.handle(RMStateStore.java:761)
 
at 
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:173) 
at org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:106) 
at java.lang.Thread.run(Thread.java:744) 
{code}

It will be better to  Improve FileSystemRMStateStore update failure exception 
handling to not  shutdown RM. So that a single state write out failure can't 
stop all jobs .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2811 PreCommit Build #5756

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2811
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5756/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3304 lines...]
  http://issues.apache.org/jira/secure/attachment/12679905/YARN-2811.v3.patch
  against trunk revision 10f9f51.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5756//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5756//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
4f9aac50883fe429565ae1623076e14508c09a0d logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8968804 bytes
Compression is 0.0%
Took 2.8 sec
Description set: MAPREDUCE-5960
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Re: Some information required related to Hadoop documentation developement

[Andrew Wang]

These are APT doc files, see this page (*.apt.vm):

http://maven.apache.org/doxia/references/apt-format.html

On Thu, Nov 6, 2014 at 10:42 AM, Masatake Iwasaki <
iwasak...@oss.nttdata.co.jp> wrote:

> Hi Naga,
>
>
> >   1.  what and how are these *.vm files(format) used in Hadoop [Hdfs and
> Yarn] documentation ?
> >   2.  Does vm files stand for velocity macro?
>
> Velocity macro is used for variable substitution as far as I know.
> For example::
>
>   ---
>   YARN Timeline Server
>   ---
>   ---
>   ${maven.build.timestamp}
>
> Though many of dosc uses APT format ( http://maven.apache.org/doxia/
> references/apt-format.html ),
> you can also use markdown.
> See hadoop-mapreduce-project/hadoop-mapreduce-client/
> hadoop-mapreduce-client-core/src/site/markdown
> for example.
>
>
> >  5.  Are these documentation pages built if " -Pdocs " parameters are
> provided during "mvn install" ? If so which Pom is responsible for building
> the html files ? Basically how to modify and test the generated html files?
>
> Run "mvn site" to build site docs.
> Running "mvn site site:stage -DstagingDirectory=/var/www/html/hadoop-site"
> puts built docs to specifiled path.
>
>
> >  6.  From earlier patches  (ex : yarn 1696) i figured out that to add
> new page(in yarn documentation) we can add a *.vm file in
> "hadoop-yarn-project\hadoop-yarn\hadoop-yarn-site\src\site\apt" and make
> entry in "hadoop-project\src\site\site.xml"  for the new page? Is that
> sufficient or anything else needs to be taken care?
>
> I think it is sufficient.
>
>
> Masatake Iwasaki
>
>
> (11/6/14, 9:51), Naganarasimha G R (Naga) wrote:> Hi All,
> > I wanted to know the following related to Hadoop Documentation
> >
> >1.  what and how are these *.vm files(format) used in Hadoop [Hdfs
> and Yarn] documentation ?
> >2.  Does vm files stand for velocity macro?
> >3.  Do we use some kind of editor to create/update these files ?
> >4.  Are there any guidelines for writing Hadoop/YARN documentation ?
> >5.  Are these documentation pages built if " -Pdocs " parameters are
> provided during "mvn install" ? If so which Pom is responsible for building
> the html files ? Basically how to modify and test the generated html files?
> >6.  From earlier patches  (ex : yarn 1696) i figured out that to add
> new page(in yarn documentation) we can add a *.vm file in
> "hadoop-yarn-project\hadoop-yarn\hadoop-yarn-site\src\site\apt" and make
> entry in "hadoop-project\src\site\site.xml"  for the new page? Is that
> sufficient or anything else needs to be taken care?
> >
> >
> > Regards,
> >
> > Naga
> >
> >
> >
> > Huawei Technologies Co., Ltd.
> > Phone:
> > Fax:
> > Mobile:  +91 9980040283
> > Email: naganarasimh...@huawei.com
> > Huawei Technologies Co., Ltd.
> > Bantian, Longgang District,Shenzhen 518129, P.R.China
> > http://www.huawei.com
> >
>
>
>

[jira] [Created] (YARN-2821) Distributed shell app master becomes unresponsive sometimes

[Varun Vasudev (JIRA)]

Varun Vasudev created YARN-2821:
---

 Summary: Distributed shell app master becomes unresponsive 
sometimes
 Key: YARN-2821
 URL: https://issues.apache.org/jira/browse/YARN-2821
 Project: Hadoop YARN
  Issue Type: Bug
  Components: applications/distributed-shell
Affects Versions: 2.5.1
Reporter: Varun Vasudev
Assignee: Varun Vasudev


We've noticed that once in a while the distributed shell app master becomes 
unresponsive and is eventually killed by the RM. snippet of the logs -
{noformat}
14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: 
appattempt_1415123350094_0017_01 received 0 previous attempts' running 
containers on AM registration.
14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested container 
ask: Capability[]Priority[0]
14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested container 
ask: Capability[]Priority[0]
14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested container 
ask: Capability[]Priority[0]
14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested container 
ask: Capability[]Priority[0]
14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested container 
ask: Capability[]Priority[0]
14/11/04 18:21:38 INFO impl.AMRMClientImpl: Received new token for : 
onprem-tez2:45454
14/11/04 18:21:38 INFO distributedshell.ApplicationMaster: Got response from RM 
for container ask, allocatedCnt=1
14/11/04 18:21:38 INFO distributedshell.ApplicationMaster: Launching shell 
command on a new container., 
containerId=container_1415123350094_0017_01_02, 
containerNode=onprem-tez2:45454, containerNodeURI=onprem-tez2:50060, 
containerResourceMemory1024, containerResourceVirtualCores1
14/11/04 18:21:38 INFO distributedshell.ApplicationMaster: Setting up container 
launch container for containerid=container_1415123350094_0017_01_02
14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: 
START_CONTAINER for Container container_1415123350094_0017_01_02
14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : 
onprem-tez2:45454
14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: 
QUERY_CONTAINER for Container container_1415123350094_0017_01_02
14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : 
onprem-tez2:45454
14/11/04 18:21:39 INFO impl.AMRMClientImpl: Received new token for : 
onprem-tez3:45454
14/11/04 18:21:39 INFO impl.AMRMClientImpl: Received new token for : 
onprem-tez4:45454
14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Got response from RM 
for container ask, allocatedCnt=3
14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Launching shell 
command on a new container., 
containerId=container_1415123350094_0017_01_03, 
containerNode=onprem-tez2:45454, containerNodeURI=onprem-tez2:50060, 
containerResourceMemory1024, containerResourceVirtualCores1
14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Launching shell 
command on a new container., 
containerId=container_1415123350094_0017_01_04, 
containerNode=onprem-tez3:45454, containerNodeURI=onprem-tez3:50060, 
containerResourceMemory1024, containerResourceVirtualCores1
14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Launching shell 
command on a new container., 
containerId=container_1415123350094_0017_01_05, 
containerNode=onprem-tez4:45454, containerNodeURI=onprem-tez4:50060, 
containerResourceMemory1024, containerResourceVirtualCores1
14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Setting up container 
launch container for containerid=container_1415123350094_0017_01_03
14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Setting up container 
launch container for containerid=container_1415123350094_0017_01_05
14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Setting up container 
launch container for containerid=container_1415123350094_0017_01_04
14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: 
START_CONTAINER for Container container_1415123350094_0017_01_05
14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: 
START_CONTAINER for Container container_1415123350094_0017_01_03
14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : 
onprem-tez4:45454
14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : 
onprem-tez2:45454
14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: 
START_CONTAINER for Container container_1415123350094_0017_01_04
14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : 
onprem-tez3:45454
14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: 
QUERY_CONTAINER for Container container_1415123350094_0017_01_05
14/11/04 18:21:39 INFO impl.ContainerMana

[jira] [Created] (YARN-2822) NPE when RM tries to transfer state from previous attempt on recovery

[Jian He (JIRA)]

Jian He created YARN-2822:
-

 Summary: NPE when RM tries to transfer state from previous attempt 
on recovery
 Key: YARN-2822
 URL: https://issues.apache.org/jira/browse/YARN-2822
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Jian He
Assignee: Jian He


{code}
2014-09-16 01:36:28,037 FATAL resourcemanager.ResourceManager 
(ResourceManager.java:run(612)) - Error in handling event type 
APP_ATTEMPT_ADDED to the scheduler
java.lang.NullPointerException
at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApplicationAttempt.transferStateFromPreviousAttempt(SchedulerApplicationAttempt.java:530)
at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.addApplicationAttempt(CapacityScheduler.java:678)
at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:1015)
at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:98)
at 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:603)
at java.lang.Thread.run(Thread.java:744)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (YARN-2823) NullPointerException in RM HA enabled 3-node cluster

[Gour Saha (JIRA)]

Gour Saha created YARN-2823:
---

 Summary: NullPointerException in RM HA enabled 3-node cluster
 Key: YARN-2823
 URL: https://issues.apache.org/jira/browse/YARN-2823
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Gour Saha


Branch:
2.6.0

Environment: 
A 3-node cluster with RM HA enabled. The HA setup went pretty smooth (used 
Ambari) and then installed HBase using Slider. After some time the RMs went 
down and would not come back up anymore. Following is the NPE we see in both 
the RM logs.

{noformat}
2014-09-16 01:36:28,037 FATAL resourcemanager.ResourceManager 
(ResourceManager.java:run(612)) - Error in handling event type 
APP_ATTEMPT_ADDED to the scheduler
java.lang.NullPointerException
at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApplicationAttempt.transferStateFromPreviousAttempt(SchedulerApplicationAttempt.java:530)
at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.addApplicationAttempt(CapacityScheduler.java:678)
at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:1015)
at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:98)
at 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:603)
at java.lang.Thread.run(Thread.java:744)
2014-09-16 01:36:28,042 INFO  resourcemanager.ResourceManager 
(ResourceManager.java:run(616)) - Exiting, bbye..
{noformat}

All the logs for this 3-node cluster has been uploaded.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2821 PreCommit Build #5757

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2821
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5757/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3098 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12679948/apache-yarn-2821.0.patch
  against trunk revision 1670578.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5757//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5757//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
ffedc752f7722be2f9da6cd21218a9b7661da918 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8730065 bytes
Compression is 0.0%
Took 2.7 sec
Description set: YARN-2821
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2824) Capacity of labels should be zero by default

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2824:


 Summary: Capacity of labels should be zero by default
 Key: YARN-2824
 URL: https://issues.apache.org/jira/browse/YARN-2824
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Wangda Tan
Priority: Critical


In existing Capacity Scheduler behavior, if user doesn't specify capacity of 
label, queue initialization will be failed. That will cause queue refreshment 
failed when add a new label to node labels collection and doesn't modify 
capacity-scheduler.xml.

With this patch, capacity of labels should be explicitly set if user want to 
use it. If user doesn't set capacity of some labels, we will treat such labels 
are unused labels.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

What is point of using Factory Pattern in Yarn Samples?

[Daryoush Mehrtash]

I am looking at the tutorial examples of Yarn application and see the
pattern:

// Resource requirements for worker containers
> Resource capability = Records.newRecord(Resource.class);
> capability.setMemory(128);
> capability.setVirtualCores(1);


I am trying to understand the reasoning for using a Factory Records class
to construct an instance of Resource (same pattern is repeated for every
other Yarn object creation).

Is the extra indirection being used currently for any particular use case?
 Or is it for future extension?

Thanks

Daryoush

Failed: YARN-2816 PreCommit Build #5758

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2816
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5758/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 25 lines...]
Testing patch for YARN-2816.
==
==


HEAD is now at 75b820c HDFS-7365. Remove 
hdfs.server.blockmanagement.MutableBlockCollection. Contributed by Li Lu.
Previous HEAD position was 75b820c... HDFS-7365. Remove 
hdfs.server.blockmanagement.MutableBlockCollection. Contributed by Li Lu.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 2 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 75b820cca9d4e709b9e8d40635ff0406528ad4ba.
YARN-2816 patch is being downloaded at Thu Nov  6 22:00:34 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12679963/leveldb_records.txt
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
patch:  Only garbage was found in the patch input.
patch:  Only garbage was found in the patch input.
patch:  Only garbage was found in the patch input.
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679963/leveldb_records.txt
  against trunk revision 75b820c.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5758//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
63a2f0d5bc59d9bae293c1079e403f44362fc54b logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2822 PreCommit Build #5759

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2822
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5759/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3307 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679964/YARN-2822.1.patch
  against trunk revision 75b820c.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5759//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5759//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
efe71c59bc0654abba045ad34034d329285038b0 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8966968 bytes
Compression is 0.0%
Took 2.8 sec
Description set: YARN-2822
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2823 PreCommit Build #5760

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2823
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5760/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3304 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679967/YARN-2823.1.patch
  against trunk revision 75b820c.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5760//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5760//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
98c7f50e614e2d72142d0d5e8f70c9a3115ec2c1 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8966972 bytes
Compression is 0.0%
Took 2.9 sec
Description set: YARN-2823
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2819 PreCommit Build #5761

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2819
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5761/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3129 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679989/YARN-2819.1.patch
  against trunk revision 75b820c.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5761//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5761//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
a1d4b6f6fef308fdc579563c42e78eec60c928ac logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8760771 bytes
Compression is 0.0%
Took 2.9 sec
Description set: YARN-2819
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2825) Container leak on NM

[Jian He (JIRA)]

Jian He created YARN-2825:
-

 Summary: Container leak on NM
 Key: YARN-2825
 URL: https://issues.apache.org/jira/browse/YARN-2825
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Jian He
Assignee: Jian He
Priority: Critical


Caused by YARN-1372. thanks [~vinodkv] for pointing  this out.

The problem is that in YARN-1372 we changed the behavior to remove containers 
from NMContext only after the containers are acknowledged  by AM. But in the 
{{NodeStatusUpdaterImpl#removeCompletedContainersFromContext}} call, we didn't 
check whether the container is really completed or not.  If the container is 
stilll running, we shouldn't remove the container from the context



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2824 PreCommit Build #5762

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2824
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5762/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3385 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679998/YARN-2824-1.patch
  against trunk revision 75b820c.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:red}-1 findbugs{color}.  The patch appears to introduce 1 new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5762//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5762//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5762//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
3f65ee5babdd1ff6ea3da861d2d9a5a25d9ae46c logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 20 artifacts
Archive block size is 32768
Received 0 blocks and 9031138 bytes
Compression is 0.0%
Took 2.9 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2803 PreCommit Build #5763

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2803
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5763/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3326 lines...]
  http://issues.apache.org/jira/secure/attachment/12680024/YARN-2803.0.patch
  against trunk revision 75b820c.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5763//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5763//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
64e70875b7c5a6cef5c28e18cf613c1505cca884 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8894312 bytes
Compression is 0.0%
Took 3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2826) User-Group mappings not updated by RM when a user is removed from a group.

[sidharta seethana (JIRA)]

sidharta seethana created YARN-2826:
---

 Summary: User-Group mappings not updated by RM when a user is 
removed from a group.
 Key: YARN-2826
 URL: https://issues.apache.org/jira/browse/YARN-2826
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: sidharta seethana
Priority: Critical


Removing a user from a group isn't reflected in getGroups even after a refresh. 
The following sequence fails in step 7. 

1) add test_user to a machine with group1 
2) add test_user to group2 on the machine 
3) yarn rmadmin -refreshUserToGroupsMappings (expected to refresh user to group 
mappings) 
4) yarn rmadmin -getGroups test_user (and ensure that user is in group2) 
5) remove user from group2 on the machine 
6) yarn rmadmin -refreshUserToGroupsMappings (expected to refresh user to group 
mappings) 
7) yarn rmadmin -getGroups test_user (and ensure that user NOT in group2) 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2632 PreCommit Build #5767

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2632
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5767/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3024 lines...]
  http://issues.apache.org/jira/secure/attachment/12680050/YARN-2632-v3.patch
  against trunk revision ae71a67.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5767//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5767//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
8a952115b6d78cfbb364b15efb6b1043f6dc76cd logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 10 artifacts
Archive block size is 32768
Received 0 blocks and 8674906 bytes
Compression is 0.0%
Took 2.5 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2505 PreCommit Build #5764

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2505
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5764/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3312 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12680035/YARN-2505.16.patch
  against trunk revision a3839a9.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5764//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5764//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
6a599878676059055667cf05a720932fc762a649 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8969678 bytes
Compression is 0.0%
Took 3 sec
Description set: YARN-2505
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2825 PreCommit Build #5768

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2825
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5768/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3329 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12680054/YARN-2825.1.patch
  against trunk revision ae71a67.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5768//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5768//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
077ce15aed5cbd1711da81c898e0acbc627dd4ff logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8893672 bytes
Compression is 0.0%
Took 5.2 sec
Description set: YARN-2825
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2824 PreCommit Build #5766

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2824
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5766/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3686 lines...]
  http://issues.apache.org/jira/secure/attachment/12680048/YARN-2824-2.patch
  against trunk revision ae71a67.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5766//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5766//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
1479b3ad74656ee69bcab4423f9e0b9d74504b03 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 20 artifacts
Archive block size is 32768
Received 0 blocks and 9052274 bytes
Compression is 0.0%
Took 2.1 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2505 PreCommit Build #5765

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2505
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5765/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3520 lines...]
  http://issues.apache.org/jira/secure/attachment/12680044/YARN-2505.18.patch
  against trunk revision ae71a67.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesNodes

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5765//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5765//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
0a055b10e850a43ff977f672c622ed2f52aebb00 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 20 artifacts
Archive block size is 32768
Received 0 blocks and 9264985 bytes
Compression is 0.0%
Took 2.2 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2825 PreCommit Build #5769

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2825
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5769/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3326 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12680068/YARN-2825.1.patch
  against trunk revision ba0a42c.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5769//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5769//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
af1c296c4e27aa64f4d43a54e237c7758e7460d3 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8893690 bytes
Compression is 0.0%
Took 2.3 sec
Description set: YARN-2825
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2826 PreCommit Build #5770

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2826
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5770/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3322 lines...]

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5770//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5770//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
2bb7ba19e05b7b619cd574941be2599298e6b275 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8967432 bytes
Compression is 0.0%
Took 5 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2647 PreCommit Build #5772

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2647
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5772/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3132 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12680079/0008-YARN-2647-1.patch
  against trunk revision ba0a42c.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5772//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5772//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
a96815f885c4fc769bb4db49b9b2788abd24619b logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8745803 bytes
Compression is 0.0%
Took 2.7 sec
Description set: YARN-2647
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2505 PreCommit Build #5771

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2505
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5771/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3511 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12680075/YARN-2505.19.patch
  against trunk revision ba0a42c.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5771//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5771//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
08557eebcf50587a1cdc7dc69dd79aaf02cf85ca logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 20 artifacts
Archive block size is 32768
Received 0 blocks and 9265328 bytes
Compression is 0.0%
Took 2.9 sec
Description set: YARN-2505
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2647 PreCommit Build #5773

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2647
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5773/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 22 lines...]

==
==
Testing patch for YARN-2647.
==
==


HEAD is now at 61effcb YARN-2647. Added a queue CLI for getting queue 
information. Contributed by Sunil Govind.
Previous HEAD position was 61effcb... YARN-2647. Added a queue CLI for getting 
queue information. Contributed by Sunil Govind.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 61effcbebc819ee1bd3d60f5444c39c972494a32.
YARN-2647 patch is being downloaded at Fri Nov  7 05:00:37 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12680090/0008-YARN-2647-full-branch-2.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12680090/0008-YARN-2647-full-branch-2.patch
  against trunk revision 61effcb.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5773//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
d16992bc51f0bd36c00588009a59c6f58f6c253c logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2647 PreCommit Build #5774

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2647
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5774/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 22 lines...]

==
==
Testing patch for YARN-2647.
==
==


HEAD is now at 61effcb YARN-2647. Added a queue CLI for getting queue 
information. Contributed by Sunil Govind.
Previous HEAD position was 61effcb... YARN-2647. Added a queue CLI for getting 
queue information. Contributed by Sunil Govind.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 2 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 61effcbebc819ee1bd3d60f5444c39c972494a32.
YARN-2647 patch is being downloaded at Fri Nov  7 05:40:37 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12680094/0009-YARN-2647-trunk-full.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12680094/0009-YARN-2647-trunk-full.patch
  against trunk revision 61effcb.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5774//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
df352553346cf8025ce88767e4210a1d5ebc74be logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2647 PreCommit Build #5775

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2647
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5775/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 19 lines...]
[PreCommit-YARN-Build] $ /bin/bash /tmp/hudson894036274180207245.sh
Running in Jenkins mode


==
==
Testing patch for YARN-2647.
==
==


HEAD is now at 61effcb YARN-2647. Added a queue CLI for getting queue 
information. Contributed by Sunil Govind.
Switched to branch 'trunk'
Your branch is up-to-date with 'origin/trunk'.
Current branch trunk is up to date.
YARN-2647 patch is being downloaded at Fri Nov  7 05:50:31 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12680095/0009-YARN-2647-trunk-without-yarn.cmd.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12680095/0009-YARN-2647-trunk-without-yarn.cmd.patch
  against trunk revision 61effcb.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5775//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
4240b6709339d96e244933368f0520c255df501e logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2647 PreCommit Build #5776

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2647
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5776/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 19 lines...]
[PreCommit-YARN-Build] $ /bin/bash /tmp/hudson7421108105399509349.sh
Running in Jenkins mode


==
==
Testing patch for YARN-2647.
==
==


HEAD is now at 61effcb YARN-2647. Added a queue CLI for getting queue 
information. Contributed by Sunil Govind.
Switched to branch 'trunk'
Your branch is up-to-date with 'origin/trunk'.
Current branch trunk is up to date.
YARN-2647 patch is being downloaded at Fri Nov  7 06:00:39 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12680099/0009-YARN-2647-branch2-full.pach
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12680099/0009-YARN-2647-branch2-full.pach
  against trunk revision 61effcb.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5776//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
7d45e28cc9b9438b831d4ac544256379b187f555 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2827) Fix bugs of yarn queue CLI

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2827:


 Summary: Fix bugs of yarn queue CLI
 Key: YARN-2827
 URL: https://issues.apache.org/jira/browse/YARN-2827
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Reporter: Wangda Tan
Assignee: Wangda Tan
Priority: Critical


Need fix bugs:
1) args of queue CLI is without "queue" even if you run with "yarn queue 
-status ..", the args is ["-status", "..."]. The assumption is incorrect.
2) It is possible that there's no related QueueInfo with specified queue name, 
and null will be returned from YarnClient, so NPE will raise. Added a check for 
it, and will print proper message
3) When failed to get QueueInfo, should return non-zero exit code.
4) Add tests for above.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2821 PreCommit Build #5777

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2821
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5777/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3395 lines...]
  
http://issues.apache.org/jira/secure/attachment/12680098/apache-yarn-2821.1.patch
  against trunk revision 61effcb.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell:

  
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5777//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5777//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
5fb9dc5087ba18ad5ea7f52102653f75da157e89 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8760739 bytes
Compression is 0.0%
Took 3.3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2794 PreCommit Build #5778

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2794
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5778/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3329 lines...]
  http://issues.apache.org/jira/secure/attachment/12679032/YARN-2794.patch
  against trunk revision d026f36.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5778//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5778//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
048794fbd29bb7483fde0210eaa017f90a13a30c logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8894661 bytes
Compression is 0.0%
Took 2.9 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.