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

[Apache Jenkins Server]

See https://builds.apache.org/job/Hadoop-Common-0.23-Build/1107/

--
[...truncated 8263 lines...]
Running org.apache.hadoop.net.TestDNS
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.17 sec
Running org.apache.hadoop.net.TestNetUtils
Tests run: 36, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.484 sec
Running org.apache.hadoop.net.TestStaticMapping
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.909 sec
Running org.apache.hadoop.net.TestSwitchMapping
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.31 sec
Running org.apache.hadoop.net.TestSocketIOWithTimeout
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.191 sec
Running org.apache.hadoop.ipc.TestRPCCompatibility
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.845 sec
Running org.apache.hadoop.ipc.TestAvroRpc
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.353 sec
Running org.apache.hadoop.ipc.TestServer
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.375 sec
Running org.apache.hadoop.ipc.TestIPC
Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 69.567 sec
Running org.apache.hadoop.ipc.TestMiniRPCBenchmark
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.742 sec
Running org.apache.hadoop.ipc.TestSaslRPC
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.722 sec
Running org.apache.hadoop.ipc.TestRPC
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.881 sec
Running org.apache.hadoop.ipc.TestSocketFactory
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.266 sec
Running org.apache.hadoop.ipc.TestIPCServerResponder
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.552 sec
Running org.apache.hadoop.jmx.TestJMXJsonServlet
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.857 sec
Running org.apache.hadoop.record.TestRecordVersioning
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.162 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.182 sec
Running org.apache.hadoop.cli.TestCLI
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.941 sec
Running org.apache.hadoop.log.TestLog4Json
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.361 sec
Running org.apache.hadoop.log.TestLogLevel
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.588 sec
Running org.apache.hadoop.http.TestHttpServer
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.47 sec
Running org.apache.hadoop.http.TestHtmlQuoting
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.269 sec
Running org.apache.hadoop.http.TestHttpRequestLogAppender
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running org.apache.hadoop.http.TestGlobalFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.76 sec
Running org.apache.hadoop.http.TestHttpServerWebapps
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.429 sec
Running org.apache.hadoop.http.lib.TestStaticUserWebFilter
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.518 sec
Running org.apache.hadoop.http.TestServletFilter
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.004 sec
Running org.apache.hadoop.http.TestPathFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.741 sec
Running org.apache.hadoop.http.TestHttpRequestLog
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.153 sec
Running org.apache.hadoop.http.TestHttpServerLifecycle
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.189 sec
Running org.apache.hadoop.conf.TestReconfiguration
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.981 sec
Running org.apache.hadoop.conf.TestConfServlet
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.402 sec
Running org.apache.hadoop.conf.TestDeprecatedKeys
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.349 sec
Running org.apache.hadoop.conf.TestConfiguration
Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.631 sec
Running org.apache.hadoop.conf.TestConfigurationDeprecation
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.432 sec
Running org.apache.hadoop.conf.TestGetInstances
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.242 sec
Running org.apache.hadoop.conf.TestConfigurationSubclass
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.3 sec
Running org.apache.hadoop.fs.kfs.TestKosmosFileSystem
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.576 sec
Running org.apache.hadoop.fs.s3.TestInMemoryS3FileSystemContract
Tests run: 29, Failures: 0, 

Re: Thinking ahead to hadoop-2.6

[Yongjun Zhang]

Thanks Arun for the info and reminder.

Hi Alejandro,

HADOOP-10895 is a blocker in the list Arun sent out and it's currently
owned by you. I wonder whether you will have time to work on. If not, would
you mind reassigning it to me and I will spend time on it?

Thanks.

--Yongjun


On Tue, Oct 14, 2014 at 11:25 AM, Arun C Murthy a...@hortonworks.com wrote:

 2.6.0 is close now.

 Here are the remaining blockers, I'm hoping cut an RC in the next week or
 so:
 http://s.apache.org/hadoop-2.6.0-blockers

 thanks,
 Arun

 On Sep 30, 2014, at 10:42 AM, Arun C Murthy a...@hortonworks.com wrote:

  Folks,
 
   I've created branch-2.6 to stabilize the release.
 
   Committers, please exercise caution henceforth on commits other than
 the ones we've discussed on this thread already.
 
   By default new features should now be targeted to the version 2.7
 henceforth - I've ensure all the projects have that version on jira.
 
  thanks,
  Arun
 
  On Sep 26, 2014, at 1:08 AM, Arun Murthy a...@hortonworks.com wrote:
 
  Sounds good. I'll branch this weekend and we can merge the jiras we
  discussed in this thread as they they get wrapped next week.
 
  Thanks everyone.
 
  Arun
 
 
  On Sep 24, 2014, at 7:39 PM, Vinod Kumar Vavilapalli 
 vino...@apache.org wrote:
 
  We can branch off in a week or two so that work on branch-2 itself can
 go
  ahead with other features that can't fit in 2.6. Independent of that,
 we
  can then decide on the timeline of the release candidates once
 branch-2.6
  is close to being done w.r.t the planned features.
 
  Branching it off can let us focus on specific features that we want in
 for
  2.6 and then eventually blockers for the release, nothing else. There
 is a
  trivial pain of committing to one more branch, but it's worth it in
 this
  case IMO.
 
  A lot of efforts are happening in parallel from the YARN side from
 where I
  see. 2.6 is a little bulky if only on the YARN side and I'm afraid if
 we
  don't branch off and selectively try to get stuff in, it is likely to
 be in
  a perpetual delay.
 
  My 2 cents.
 
  +Vinod
 
  On Wed, Sep 24, 2014 at 3:28 PM, Suresh Srinivas 
 sur...@hortonworks.com
  wrote:
 
  Given some of the features are in final stages of stabilization,
  Arun, we should hold off creating 2.6 branch or building an RC by a
 week?
  All the features in flux are important ones and worth delaying the
 release
  by a week.
 
  On Wed, Sep 24, 2014 at 11:36 AM, Andrew Wang 
 andrew.w...@cloudera.com
  wrote:
 
  Hey Nicholas,
 
  My concern about Archival Storage isn't related to the code quality
 or
  the
  size of the feature. I think that you and Jing did good work. My
 concern
  is
  that once we ship, we're locked into that set of archival storage
 APIs,
  and
  these APIs are not yet finalized. Simply being able to turn off the
  feature
  does not change the compatibility story.
 
  I'm willing to devote time to help review these JIRAs and kick the
 tires
  on
  the APIs, but my point above was that I'm not sure it'd all be done
 by
  the
  end of the week. Testing might also reveal additional changes that
 need
  to
  be made, which also might not happen by end-of-week.
 
  I guess the question before us is if we're comfortable putting
 something
  in
  branch-2.6 and then potentially adding API changes after. I'm okay
 with
  that as long as we're all aware that this might happen.
 
  Arun, as RM is this cool with you? Again, I like this feature and I'm
  fine
  with it's inclusion, just a heads up that we might need some extra
 time
  to
  finalize things before an RC can be cut.
 
  Thanks,
  Andrew
 
  On Tue, Sep 23, 2014 at 7:30 PM, Tsz Wo (Nicholas), Sze 
  s29752-hadoop...@yahoo.com.invalid wrote:
 
  Hi,
 
  I am worry about KMS and transparent encryption since there are
 quite
  many
  bugs discovered after it got merged to branch-2.  It gives us an
  impression
  that the feature is not yet well tested.  Indeed, transparent
  encryption
  is
  a complicated feature which changes the core part of HDFS.  It is
 not
  easy
  to get everything right.
 
 
  For HDFS-6584: Archival Storage, it is a relatively simple and low
 risk
  feature.  It introduces a new storage type ARCHIVE and the concept
 of
  block
  storage policy to HDFS.  When a cluster is configured with ARCHIVE
  storage,
  the blocks will be stored using the appropriate storage types
 specified
  by
  storage policies assigned to the files/directories.  Cluster admin
  could
  disable the feature by simply not configuring any storage type and
 not
  setting any storage policy as before.   As Suresh mentioned,
 HDFS-6584
  is
  in the final stages to be merged to branch-2.
 
  Regards,
  Tsz-Wo
 
 
 
  On Wednesday, September 24, 2014 7:00 AM, Suresh Srinivas 
  sur...@hortonworks.com wrote:
 
 
 
 
  I actually would like to see both archival storage and single
 replica
  memory writes to be in 2.6 release. Archival storage is in the
 final
  stages
  of getting ready for branch-2