[jira] [Resolved] (HADOOP-11745) Incorporate ShellCheck static analysis into Jenkins pre-commit builds.

2015-04-07 Thread aaaliu (JIRA)

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

aaaliu resolved HADOOP-11745.
-
  Resolution: Fixed
Assignee: aaaliu
Hadoop Flags: Reviewed

 Incorporate ShellCheck static analysis into Jenkins pre-commit builds.
 --

 Key: HADOOP-11745
 URL: https://issues.apache.org/jira/browse/HADOOP-11745
 Project: Hadoop Common
  Issue Type: Improvement
  Components: build, scripts
Reporter: Chris Nauroth
Assignee: aaaliu
Priority: Minor

 During the shell script rewrite on trunk, we've been using ShellCheck as a 
 static analysis tool to catch common errors.  We can incorporate this 
 directly into Jenkins pre-commit builds.  Jenkins can reply with a -1 on 
 shell script patches that introduce new ShellCheck warnings.



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


[jira] [Resolved] (HADOOP-11805) Better to rename some raw erasure coders

2015-04-07 Thread Kai Zheng (JIRA)

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

Kai Zheng resolved HADOOP-11805.

   Resolution: Fixed
Fix Version/s: HDFS-7285

 Better to rename some raw erasure coders
 

 Key: HADOOP-11805
 URL: https://issues.apache.org/jira/browse/HADOOP-11805
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: io
Reporter: Kai Zheng
Assignee: Kai Zheng
 Fix For: HDFS-7285

 Attachments: HADOOP-11805-v1.patch


 When work on more coders, it was found better to rename some existing raw 
 coders for consistency, and more meaningful. As a result, we may have:
 XORRawErasureCoder, in Java
 NativeXORRawErasureCoder, in native
 RSRawErasureCoder, in Java
 NativeRSRawErasureCoder, in native and using ISA-L



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


[jira] [Resolved] (HADOOP-11645) Erasure Codec API covering the essential aspects for an erasure code

2015-04-07 Thread Vinayakumar B (JIRA)

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

Vinayakumar B resolved HADOOP-11645.

   Resolution: Fixed
Fix Version/s: HDFS-7285
 Hadoop Flags: Reviewed

Thanks [~drankye].

 Erasure Codec API covering the essential aspects for an erasure code
 

 Key: HADOOP-11645
 URL: https://issues.apache.org/jira/browse/HADOOP-11645
 Project: Hadoop Common
  Issue Type: Sub-task
Reporter: Kai Zheng
Assignee: Kai Zheng
 Fix For: HDFS-7285

 Attachments: HADOOP-11645-v1.patch, HADOOP-11645-v2.patch, 
 HADOOP-11645-v3.patch


 This is to define the even higher level API *ErasureCodec* to possiblly 
 consider all the essential aspects for an erasure code, as discussed in in 
 HDFS-7337 in details. Generally, it will cover the necessary configurations 
 about which *RawErasureCoder* to use for the code scheme, how to form and 
 layout the BlockGroup, and etc. It will also discuss how an *ErasureCodec* 
 will be used in both client and DataNode, in all the supported modes related 
 to EC.



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


Re: Why I don't trust the git log: a fun git log challenge

2015-04-07 Thread Allen Wittenauer

On Apr 7, 2015, at 8:56 AM, Allen Wittenauer a...@altiscale.com wrote:

   
 Find and fix the mistake made in the past 24 hours to the git log (and 
 changes.txt as well, so no help there!).
 
 

… and no, it isn’t that YARN-2666 is missing it’s JIRA in the changes.txt.  
That’s too easy and besides, I said the changes.txt file would be no help here …






Re: Why I don't trust the git log: a fun git log challenge

2015-04-07 Thread Chris Nauroth
Is this a trick question, because you really can't fix prior commits in
the git log without a forced push, which then invalidates everyone's
cloned copy of the repo?  :-)

Chris Nauroth
Hortonworks
http://hortonworks.com/






On 4/7/15, 9:55 AM, Allen Wittenauer a...@altiscale.com wrote:


On Apr 7, 2015, at 8:56 AM, Allen Wittenauer a...@altiscale.com wrote:

  
 Find and fix the mistake made in the past 24 hours to the git log (and
changes.txt as well, so no help there!).
 
 

Š and no, it isn¹t that YARN-2666 is missing it¹s JIRA in the
changes.txt.  That¹s too easy and besides, I said the changes.txt file
would be no help here Š







Why I don't trust the git log: a fun git log challenge

2015-04-07 Thread Allen Wittenauer

Find and fix the mistake made in the past 24 hours to the git log (and 
changes.txt as well, so no help there!).




[jira] [Reopened] (HADOOP-11745) Incorporate ShellCheck static analysis into Jenkins pre-commit builds.

2015-04-07 Thread Allen Wittenauer (JIRA)

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

Allen Wittenauer reopened HADOOP-11745:
---
  Assignee: Allen Wittenauer  (was: aaaliu)

 Incorporate ShellCheck static analysis into Jenkins pre-commit builds.
 --

 Key: HADOOP-11745
 URL: https://issues.apache.org/jira/browse/HADOOP-11745
 Project: Hadoop Common
  Issue Type: Improvement
  Components: build, scripts
Reporter: Chris Nauroth
Assignee: Allen Wittenauer
Priority: Minor

 During the shell script rewrite on trunk, we've been using ShellCheck as a 
 static analysis tool to catch common errors.  We can incorporate this 
 directly into Jenkins pre-commit builds.  Jenkins can reply with a -1 on 
 shell script patches that introduce new ShellCheck warnings.



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


Re: Why I don't trust the git log: a fun git log challenge

2015-04-07 Thread Allen Wittenauer

On Apr 7, 2015, at 10:03 AM, Chris Nauroth cnaur...@hortonworks.com wrote:

 Is this a trick question, because you really can't fix prior commits in
 the git log without a forced push, which then invalidates everyone's
 cloned copy of the repo?  :-)

There is an error that would require such a thing, yes. :D




[jira] [Created] (HADOOP-11810) Test TestSecureRMRegistryOperations failed with IBM_JAVA JVM

2015-04-07 Thread pascal oliva (JIRA)
pascal oliva created HADOOP-11810:
-

 Summary: Test TestSecureRMRegistryOperations failed with IBM_JAVA 
JVM
 Key: HADOOP-11810
 URL: https://issues.apache.org/jira/browse/HADOOP-11810
 Project: Hadoop Common
  Issue Type: Test
 Environment: $ mvn -version
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 
2014-02-14T11:37:52-06:00)
Maven home: /opt/apache-maven-3.2.1
Java version: 1.7.0, vendor: IBM Corporation
Java home: /usr/lib/jvm/ibm-java-ppc64le-71/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.10.0-229.ael7b.ppc64le, arch: ppc64le, family: 
unix

Reporter: pascal oliva


TestSecureRMRegistryOperations failed with JBM IBM JAVA

mvn test -X 
-Dtest=org.apache.hadoop.registry.secure.TestSecureRMRegistryOperations

ModuleTotal Failure Error Skipped
-
hadoop-yarn-registry 12  0   12 0
-
 Total  12  0   12 0

With 
javax.security.auth.login.LoginException: Bad JAAS configuration: unrecognized 
option: isInitiator

and 

Bad JAAS configuration: unrecognized option: storeKey










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


[jira] [Resolved] (HADOOP-11809) Building hadoop on windows 64 bit, windows 7.1 SDK : \hadoop-common\target\findbugsXml.xml does not exist

2015-04-07 Thread Arpit Agarwal (JIRA)

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

Arpit Agarwal resolved HADOOP-11809.

Resolution: Invalid

Hi [~kantum...@yahoo.com], please use the dev mailing list for questions.

Resolving as Invalid.

 Building hadoop on windows 64 bit, windows 7.1 SDK : 
 \hadoop-common\target\findbugsXml.xml does not exist
 -

 Key: HADOOP-11809
 URL: https://issues.apache.org/jira/browse/HADOOP-11809
 Project: Hadoop Common
  Issue Type: Bug
  Components: build
Affects Versions: 2.6.0
Reporter: Umesh Kant

 I am trying to build hadoop 2.6.0 on Windows 7 64 bit, Windows 7.1 SDK. I 
 have gone through Build.txt file and have did follow all the pre-requisites 
 for build on windows. Still when I try to build, I am getting following error:
 Maven command: mvn package -X -Pdist -Pdocs -Psrc -Dtar -DskipTests 
 -Pnative-win findbugs:findbugs
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 04:35 min
 [INFO] Finished at: 2015-04-03T23:16:57-04:00
 [INFO] Final Memory: 123M/1435M
 [INFO] 
 
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-antrun-plugin:1.7:
 run (site) on project hadoop-common: An Ant BuildException has occured: input 
 fi
 le 
 C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-common\target\findbugsXml.
 xml does not exist
 [ERROR] around Ant part ...xslt 
 in=C:\H\hadoop-2.6.0-src\hadoop-common-project
 \hadoop-common\target/findbugsXml.xml 
 style=C:\findbugs-3.0.1/src/xsl/default.
 xsl 
 out=C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-common\target/site/
 findbugs.html/... @ 44:232 in 
 C:\H\hadoop-2.6.0-src\hadoop-common-project\hado
 op-common\target\antrun\build-main.xml
 [ERROR] - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal o
 rg.apache.maven.plugins:maven-antrun-plugin:1.7:run (site) on project 
 hadoop-com
 mon: An Ant BuildException has occured: input file 
 C:\H\hadoop-2.6.0-src\hadoop-
 common-project\hadoop-common\target\findbugsXml.xml does not exist
 around Ant part ...xslt 
 in=C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-
 common\target/findbugsXml.xml style=C:\findbugs-3.0.1/src/xsl/default.xsl 
 out
 =C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-common\target/site/findbugs
 .html/... @ 44:232 in 
 C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-commo
 n\target\antrun\build-main.xml
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
 .java:216)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
 .java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
 .java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
 ct(LifecycleModuleBuilder.java:116)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
 ct(LifecycleModuleBuilder.java:80)
 at 
 org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThre
 adedBuilder.build(SingleThreadedBuilder.java:51)
 at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
 eStarter.java:128)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
 java:62)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:483)
 at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
 cher.java:289)
 at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
 a:229)
 at 
 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
 uncher.java:415)
 at 
 org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
 356)
 Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant 
 BuildException
  has occured: input file 
 C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-comm
 on\target\findbugsXml.xml does not exist
 around Ant part ...xslt 
 in=C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-
 

[jira] [Created] (HADOOP-11811) Fix typos in hadoop-project/pom.xml

2015-04-07 Thread Chen He (JIRA)
Chen He created HADOOP-11811:


 Summary: Fix typos in hadoop-project/pom.xml
 Key: HADOOP-11811
 URL: https://issues.apache.org/jira/browse/HADOOP-11811
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Chen He
Priority: Trivial


!-- These 2 versions are defined here becuase they are used --
!-- JDIFF generation from embedded ant in the antrun plugin --

etc. 



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


Re: Why I don't trust the git log: a fun git log challenge

2015-04-07 Thread Konstantin Shvachko
A proper precommit hook could have prevented YARN-2666 mishap.

On Tue, Apr 7, 2015 at 9:55 AM, Allen Wittenauer a...@altiscale.com wrote:


 On Apr 7, 2015, at 8:56 AM, Allen Wittenauer a...@altiscale.com wrote:

 
  Find and fix the mistake made in the past 24 hours to the git log (and
 changes.txt as well, so no help there!).
 
 

 … and no, it isn’t that YARN-2666 is missing it’s JIRA in the
 changes.txt.  That’s too easy and besides, I said the changes.txt file
 would be no help here …







Re: Why I don't trust the git log: a fun git log challenge

2015-04-07 Thread Allen Wittenauer

For those wondering, YARN-2429 is the wrong JIRA for that commit.  Simple typo, 
but deadly if one is using to use the git log to determine what’s actually 
committed...



Windows 64 bit, Windows 7.1 SDK, Build Error, An Ant BuildException has occured: input file \hadoop-common\target\findbugsXml.xml does not exist

2015-04-07 Thread Umesh Kant
  All,
I am trying to build hadoop 2.6.0 on Windows 7 64 bit, Windows 7.1 SDK. I have 
gone through Build.txt file and have did follow all the pre-requisites for 
build on windows. Still when I try to build, I am getting following error:
Maven command: mvn package -X -Pdist -Pdocs -Psrc -Dtar -DskipTests 
-Pnative-win findbugs:findbugs
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 04:35 min
[INFO] Finished at: 2015-04-03T23:16:57-04:00
[INFO] Final Memory: 123M/1435M
[INFO] 
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:
run (site) on project hadoop-common: An Ant BuildException has occured: input fi
le C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-common\target\findbugsXml.
xml does not exist
[ERROR] around Ant part ...xslt in=C:\H\hadoop-2.6.0-src\hadoop-common-project
\hadoop-common\target/findbugsXml.xml style=C:\findbugs-3.0.1/src/xsl/default.
xsl out=C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-common\target/site/
findbugs.html/... @ 44:232 in C:\H\hadoop-2.6.0-src\hadoop-common-project\hado
op-common\target\antrun\build-main.xml
[ERROR] - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
rg.apache.maven.plugins:maven-antrun-plugin:1.7:run (site) on project hadoop-com
mon: An Ant BuildException has occured: input file C:\H\hadoop-2.6.0-src\hadoop-
common-project\hadoop-common\target\findbugsXml.xml does not exist
around Ant part ...xslt in=C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-
common\target/findbugsXml.xml style=C:\findbugs-3.0.1/src/xsl/default.xsl out
=C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-common\target/site/findbugs
.html/... @ 44:232 in C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-commo
n\target\antrun\build-main.xml
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:216)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:116)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:80)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThre
adedBuilder.build(SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:483)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
356)
Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant BuildException
 has occured: input file C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-comm
on\target\findbugsXml.xml does not exist
around Ant part ...xslt in=C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-
common\target/findbugsXml.xml style=C:\findbugs-3.0.1/src/xsl/default.xsl out
=C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-common\target/site/findbugs
.html/... @ 44:232 in C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-commo
n\target\antrun\build-main.xml
    at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:355
)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:208)
    ... 20 more
Caused by: C:\H\hadoop-2.6.0-src\hadoop-common-project\hadoop-common\target\antr
un\build-main.xml:44: input file C:\H\hadoop-2.6.0-src\hadoop-common-project\had
oop-common\target\findbugsXml.xml does not exist
    at org.apache.tools.ant.taskdefs.XSLTProcess.handleError(XSLTProcess.jav
a:1243)
    at