Build failed in Jenkins: Hadoop-Common-0.23-Build #1066

[Apache Jenkins Server]

See 

--
[...truncated 8263 lines...]
Running org.apache.hadoop.io.TestBloomMapFile
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.878 sec
Running org.apache.hadoop.io.TestObjectWritableProtos
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.329 sec
Running org.apache.hadoop.io.TestTextNonUTF8
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec
Running org.apache.hadoop.io.nativeio.TestNativeIO
Tests run: 9, Failures: 0, Errors: 0, Skipped: 9, Time elapsed: 0.159 sec
Running org.apache.hadoop.io.TestSortedMapWritable
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.198 sec
Running org.apache.hadoop.io.TestMapFile
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec
Running org.apache.hadoop.io.TestUTF8
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.312 sec
Running org.apache.hadoop.io.TestBoundedByteArrayOutputStream
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 sec
Running org.apache.hadoop.io.retry.TestRetryProxy
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.207 sec
Running org.apache.hadoop.io.retry.TestFailoverProxy
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.195 sec
Running org.apache.hadoop.io.TestSetFile
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.941 sec
Running org.apache.hadoop.io.serializer.TestWritableSerialization
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.318 sec
Running org.apache.hadoop.io.serializer.TestSerializationFactory
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.285 sec
Running org.apache.hadoop.io.serializer.avro.TestAvroSerialization
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.539 sec
Running org.apache.hadoop.util.TestGenericOptionsParser
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.684 sec
Running org.apache.hadoop.util.TestReflectionUtils
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.502 sec
Running org.apache.hadoop.util.TestJarFinder
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.763 sec
Running org.apache.hadoop.util.TestPureJavaCrc32
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.276 sec
Running org.apache.hadoop.util.TestHostsFileReader
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.187 sec
Running org.apache.hadoop.util.TestShutdownHookManager
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.144 sec
Running org.apache.hadoop.util.TestDiskChecker
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.493 sec
Running org.apache.hadoop.util.TestStringUtils
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.135 sec
Running org.apache.hadoop.util.TestGenericsUtil
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.261 sec
Running org.apache.hadoop.util.TestAsyncDiskService
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.122 sec
Running org.apache.hadoop.util.TestProtoUtil
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running org.apache.hadoop.util.TestDataChecksum
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.186 sec
Running org.apache.hadoop.util.TestRunJar
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.127 sec
Running org.apache.hadoop.util.TestOptions
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running org.apache.hadoop.util.TestShell
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.2 sec
Running org.apache.hadoop.util.TestIndexedSort
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.595 sec
Running org.apache.hadoop.util.TestStringInterner
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.115 sec
Running org.apache.hadoop.record.TestRecordVersioning
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.15 sec
Running org.apache.hadoop.record.TestBuffer
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 sec
Running org.apache.hadoop.record.TestRecordIO
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.171 sec
Running org.apache.hadoop.security.TestGroupFallback
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.425 sec
Running org.apache.hadoop.security.TestGroupsCaching
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.274 sec
Running org.apache.hadoop.security.TestProxyUserFromEnv
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.361 sec
Running org.apache.hadoop.security.TestUserGroupInformation
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.676 sec
Running org.apache.hadoop.security.TestJNIGroupsMapping
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.141 sec
Runnin

Re: [VOTE] Release Apache Hadoop 2.5.1 RC0

[Karthik Kambatla]

+1 (non-binding)

Built the source tarball, brought up a pseudo-distributed cluster and ran a
few MR jobs. Verified documentation and size of the binary tarball.

On Fri, Sep 5, 2014 at 5:18 PM, Karthik Kambatla  wrote:

> Hi folks,
>
> I have put together a release candidate (RC0) for Hadoop 2.5.1.
>
> The RC is available at: http://people.apache.org/~kasha/hadoop-2.5.1-RC0/
> The RC git tag is release-2.5.1-RC0
> The maven artifacts are staged at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1010/
>
> You can find my public key at:
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS
>
> Please try the release and vote. The vote will run for the now usual 5
> days.
>
> Thanks
> Karthik
>

Re: migrating private branches to the new git repo

[Colin McCabe]

+1 for using git log instead of CHANGES.txt.

Colin

On Wed, Sep 3, 2014 at 11:07 AM, Chris Douglas  wrote:
> On Tue, Sep 2, 2014 at 2:38 PM, Andrew Wang  wrote:
>> Not to derail the conversation, but if CHANGES.txt is making backports more
>> annoying, why don't we get rid of it? It seems like we should be able to
>> generate it via a JIRA query, and "git log" can also be used for a quick
>> check (way faster than svn log).
>
> +1
>
> As long as release notes and incompatible changes are recorded in each
> branch, we gain no accuracy by maintaining this manually. Commit
> messages that record the merge revisions instead of the change are
> similarly hateful. -C

[jira] [Created] (HADOOP-11074) Move s3-related FS connector code to hadoop-aws

[David S. Wang (JIRA)]

David S. Wang created HADOOP-11074:
--

 Summary: Move s3-related FS connector code to hadoop-aws
 Key: HADOOP-11074
 URL: https://issues.apache.org/jira/browse/HADOOP-11074
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: fs/s3
Affects Versions: 3.0.0
Reporter: David S. Wang
Assignee: David S. Wang


Now that hadoop-aws has been created, we should actually move the relevant code 
into that module, similar to what was done with hadoop-openstack, etc.



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

[jira] [Created] (HADOOP-11075) hadoop-kms is not being published to maven

[Anthony Young-Garner (JIRA)]

Anthony Young-Garner created HADOOP-11075:
-

 Summary: hadoop-kms is not being published to maven
 Key: HADOOP-11075
 URL: https://issues.apache.org/jira/browse/HADOOP-11075
 Project: Hadoop Common
  Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Anthony Young-Garner
Priority: Minor






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

[jira] [Created] (HADOOP-11076) SbNN Web UI shows #Under replicated blocks and #pending deletion blocks

[Juan Yu (JIRA)]

Juan Yu created HADOOP-11076:


 Summary: SbNN Web UI shows #Under replicated blocks and #pending 
deletion blocks
 Key: HADOOP-11076
 URL: https://issues.apache.org/jira/browse/HADOOP-11076
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Juan Yu


I believe that's an regression of HDFS-5333 
According to HDFS-2901 and HDFS-6178
The Standby Namenode doesn't compute replication queues, we shouldn't show 
under-replicated/missing blocks or corrupt files.



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

Re: Git repo ready to use

[Andrew Wang]

We're still not seeing findbugs results show up on precommit runs. I see
that we're archiving "../patchprocess/*", and Ted thinks that since it's
not in $WORKSPACE it's not getting picked up. Can we get confirmation of
this issue? If so, we could just add "patchprocess" to the toplevel
.gitignore.

On Thu, Sep 4, 2014 at 8:54 AM, Sangjin Lee  wrote:

> That's good to know. Thanks.
>
>
> On Wed, Sep 3, 2014 at 11:15 PM, Vinayakumar B 
> wrote:
>
> > I think its still pointing to old svn repository which is just read only
> > now.
> >
> > You can use latest mirror:
> > https://github.com/apache/hadoop
> >
> > Regards,
> > Vinay
> > On Sep 4, 2014 11:37 AM, "Sangjin Lee"  wrote:
> >
> > > It seems like the github mirror at
> > https://github.com/apache/hadoop-common
> > > has stopped getting updates as of 8/22. Could this mirror have been
> > broken
> > > by the git transition?
> > >
> > > Thanks,
> > > Sangjin
> > >
> > >
> > > On Fri, Aug 29, 2014 at 11:51 AM, Ted Yu  wrote:
> > >
> > > > From https://builds.apache.org/job/Hadoop-hdfs-trunk/1854/console :
> > > >
> > > > ERROR: No artifacts found that match the file pattern
> > > > "trunk/hadoop-hdfs-project/*/target/*.tar.gz". Configuration
> > > > error?ERROR :
> > > > ?trunk/hadoop-hdfs-project/*/target/*.tar.gz? doesn?t match anything,
> > > > but ?hadoop-hdfs-project/*/target/*.tar.gz? does. Perhaps that?s what
> > > > you mean?
> > > >
> > > >
> > > > I corrected the path to hdfs tar ball.
> > > >
> > > >
> > > > FYI
> > > >
> > > >
> > > >
> > > > On Fri, Aug 29, 2014 at 8:48 AM, Alejandro Abdelnur <
> t...@cloudera.com
> > >
> > > > wrote:
> > > >
> > > > > it seems we missed updating the HADOOP precommit job to use Git, it
> > was
> > > > > still using SVN. I've just updated it.
> > > > >
> > > > > thx
> > > > >
> > > > >
> > > > > On Thu, Aug 28, 2014 at 9:26 PM, Ted Yu 
> wrote:
> > > > >
> > > > > > Currently patchprocess/ (contents shown below) is one level
> higher
> > > than
> > > > > > ${WORKSPACE}
> > > > > >
> > > > > > diffJavadocWarnings.txt
> > > >  newPatchFindbugsWarningshadoop-hdfs.html
> > > > > >  patchFindBugsOutputhadoop-hdfs.txt
> patchReleaseAuditOutput.txt
> > > > > >  trunkJavadocWarnings.txt
> > > > > > filteredPatchJavacWarnings.txt
> > > newPatchFindbugsWarningshadoop-hdfs.xml
> > > > > > patchFindbugsWarningshadoop-hdfs.xml
> patchReleaseAuditWarnings.txt
> > > > > > filteredTrunkJavacWarnings.txt  patch
> > > > > > patchJavacWarnings.txttestrun_hadoop-hdfs.txt
> > > > > > jirapatchEclipseOutput.txt
> > > > > >  patchJavadocWarnings.txt  trunkJavacWarnings.txt
> > > > > >
> > > > > > Under Files to archive input box of
> > PreCommit-HDFS-Build/configure, I
> > > > > saw:
> > > > > >
> > > > > > '../patchprocess/*' doesn't match anything, but '*' does. Perhaps
> > > > that's
> > > > > > what you mean?
> > > > > >
> > > > > > I guess once patchprocess is moved back under ${WORKSPACE}, a lot
> > of
> > > > > things
> > > > > > would be back to normal.
> > > > > >
> > > > > > Cheers
> > > > > >
> > > > > > On Thu, Aug 28, 2014 at 9:16 PM, Alejandro Abdelnur <
> > > t...@cloudera.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > i'm also seeing broken links for javadocs warnings.
> > > > > > >
> > > > > > > Alejandro
> > > > > > > (phone typing)
> > > > > > >
> > > > > > > > On Aug 28, 2014, at 20:00, Andrew Wang <
> > andrew.w...@cloudera.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > I noticed that the JUnit test results aren't getting picked
> up
> > > > > > anymore. I
> > > > > > > > suspect we just need to update the path to the surefire
> output,
> > > but
> > > > > > based
> > > > > > > > on a quick examination I'm not sure what that is.
> > > > > > > >
> > > > > > > > Does someone mind taking another look?
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, Aug 28, 2014 at 4:21 PM, Karthik Kambatla <
> > > > > ka...@cloudera.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Thanks Giri and Ted for fixing the builds.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <
> yuzhih...@gmail.com
> > >
> > > > > wrote:
> > > > > > > >>>
> > > > > > > >>> Charles:
> > > > > > > >>> QA build is running for your JIRA:
> > > > > > > >>>
> > > > >
> https://builds.apache.org/job/PreCommit-hdfs-Build/7828/parameters/
> > > > > > > >>>
> > > > > > > >>> Cheers
> > > > > > > >>>
> > > > > > > >>>
> > > > > > >  On Thu, Aug 28, 2014 at 9:41 AM, Charles Lamb <
> > > > cl...@cloudera.com
> > > > > >
> > > > > > > >>> wrote:
> > > > > > > >>>
> > > > > > > > On 8/28/2014 12:07 PM, Giridharan Kesavan wrote:
> > > > > > > >
> > > > > > > > Fixed all the 3 pre-commit buids. test-patch's git reset
> > > --hard
> > > > > is
> > > > > > > > removing
> > > > > > > > the patchprocess dir, so moved it off the workspace.
> > > > > > > >>

[jira] [Created] (HADOOP-11077) NPE if hosts not specified in ProxyUsers

[Gregory Chanan (JIRA)]

Gregory Chanan created HADOOP-11077:
---

 Summary: NPE if hosts not specified in ProxyUsers
 Key: HADOOP-11077
 URL: https://issues.apache.org/jira/browse/HADOOP-11077
 Project: Hadoop Common
  Issue Type: Bug
  Components: security
Affects Versions: 2.6.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan


When using the TokenDelegationAuthenticationFilter, I noticed if I don't 
specify the hosts for a user/groups proxy user and then try to authenticate, I 
get an NPE rather than an AuthorizationException.



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

[jira] [Created] (HADOOP-11078) Create a release note for 2.5.1 release

[Akira AJISAKA (JIRA)]

Akira AJISAKA created HADOOP-11078:
--

 Summary: Create a release note for 2.5.1 release
 Key: HADOOP-11078
 URL: https://issues.apache.org/jira/browse/HADOOP-11078
 Project: Hadoop Common
  Issue Type: Bug
  Components: documentation
Affects Versions: 2.5.1
Reporter: Akira AJISAKA
Priority: Blocker


There's a sentence "Apache Hadoop 2.5.1 is a minor release in the 2.x.y release 
line, buliding upon the previous stable release 2.4.1." in the document of 
2.5.1-RC0.
Apparently, 2.5.1 is not a minor release. We should create a new release note.



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

Re: [VOTE] Release Apache Hadoop 2.5.1 RC0

[Akira AJISAKA]

-0 (non-binding)

In the document, "Apache Hadoop 2.5.1 is a minor release in the 2.x.y 
release line, buliding upon the previous stable release 2.4.1."


Hadoop 2.5.1 is a point release. Filed HADOOP-11078 to track this.

Regards,
Akira

(2014/09/09 0:51), Karthik Kambatla wrote:

+1 (non-binding)

Built the source tarball, brought up a pseudo-distributed cluster and ran a
few MR jobs. Verified documentation and size of the binary tarball.

On Fri, Sep 5, 2014 at 5:18 PM, Karthik Kambatla  wrote:


Hi folks,

I have put together a release candidate (RC0) for Hadoop 2.5.1.

The RC is available at: http://people.apache.org/~kasha/hadoop-2.5.1-RC0/
The RC git tag is release-2.5.1-RC0
The maven artifacts are staged at:
https://repository.apache.org/content/repositories/orgapachehadoop-1010/

You can find my public key at:
http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS

Please try the release and vote. The vote will run for the now usual 5
days.

Thanks
Karthik