core-dev  

Messages by Thread

• • [jira] Commented: (HADOOP-4864) -libjars with multiple jars broken when client and cluster reside on different OSs Todd Lipcon (JIRA)
  • [jira] Commented: (HADOOP-4864) -libjars with multiple jars broken when client and cluster reside on different OSs Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-4864) -libjars with multiple jars broken when client and cluster reside on different OSs Todd Lipcon (JIRA)
  • [jira] Commented: (HADOOP-4864) -libjars with multiple jars broken when client and cluster reside on different OSs Iyappan Srinivasan (JIRA)
  • [jira] Commented: (HADOOP-4864) -libjars with multiple jars broken when client and cluster reside on different OSs Amareshwari Sriramadasu (JIRA)
• [jira] Updated: (HADOOP-5175) Option to prohibit jars unpacking Todd Lipcon (JIRA)
  • [jira] Updated: (HADOOP-5175) Option to prohibit jars unpacking Todd Lipcon (JIRA)
  • [jira] Updated: (HADOOP-5175) Option to prohibit jars unpacking Tom White (JIRA)
  • [jira] Updated: (HADOOP-5175) Option to prohibit jars unpacking Todd Lipcon (JIRA)
• [jira] Created: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Hemanth Yamijala (JIRA)
  • [jira] Assigned: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Vinod K V (JIRA)
  • [jira] Updated: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Vinod K V (JIRA)
  • [jira] Commented: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Hemanth Yamijala (JIRA)
  • [jira] Commented: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Arun C Murthy (JIRA)
  • [jira] Commented: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Arun C Murthy (JIRA)
  • [jira] Commented: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Hemanth Yamijala (JIRA)
  • [jira] Updated: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Vinod K V (JIRA)
  • [jira] Commented: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Arun C Murthy (JIRA)
  • [jira] Updated: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Vinod K V (JIRA)
  • [jira] Updated: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Vinod K V (JIRA)
  • [jira] Updated: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Hemanth Yamijala (JIRA)
  • [jira] Commented: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Hemanth Yamijala (JIRA)
  • [jira] Commented: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Hemanth Yamijala (JIRA)
  • [jira] Updated: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Vinod K V (JIRA)
  • [jira] Updated: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Hemanth Yamijala (JIRA)
  • [jira] Commented: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Hudson (JIRA)
  • [jira] Updated: (HADOOP-5884) Capacity scheduler should account high memory jobs as using more capacity of the queue Hemanth Yamijala (JIRA)
• [jira] Commented: (HADOOP-5200) NPE when the datanode comes up but the filesystem is set to file:// Steve Loughran (JIRA)
  • [jira] Commented: (HADOOP-5200) NPE when the datanode comes up but the filesystem is set to file:// Philip Zeyliger (JIRA)
  • [jira] Commented: (HADOOP-5200) NPE when the datanode comes up but the filesystem is set to file:// Konstantin Shvachko (JIRA)
• [jira] Work started: (HADOOP-5200) NPE when the datanode comes up but the filesystem is set to file:// Steve Loughran (JIRA)
• [jira] Assigned: (HADOOP-5175) Option to prohibit jars unpacking Tom White (JIRA)
• [jira] Updated: (HADOOP-4829) Allow FileSystem shutdown hook to be disabled Tom White (JIRA)
  • [jira] Updated: (HADOOP-4829) Allow FileSystem shutdown hook to be disabled Todd Lipcon (JIRA)
• [jira] Commented: (HADOOP-5805) problem using top level s3 buckets as input/output directories Tom White (JIRA)
  • [jira] Commented: (HADOOP-5805) problem using top level s3 buckets as input/output directories Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-5805) problem using top level s3 buckets as input/output directories Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-5805) problem using top level s3 buckets as input/output directories Hudson (JIRA)
• [jira] Assigned: (HADOOP-5805) problem using top level s3 buckets as input/output directories Tom White (JIRA)
• [jira] Updated: (HADOOP-5839) fixes to ec2 scripts to allow remote job submission Tom White (JIRA)
• [jira] Commented: (HADOOP-5620) discp can preserve modification times of files dhruba borthakur (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files dhruba borthakur (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Rodrigo Schmidt (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Raghu Angadi (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Rodrigo Schmidt (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Rodrigo Schmidt (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Tsz Wo (Nicholas), SZE (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Tsz Wo (Nicholas), SZE (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Rodrigo Schmidt (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Tsz Wo (Nicholas), SZE (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Rodrigo Schmidt (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Tsz Wo (Nicholas), SZE (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Rodrigo Schmidt (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Rodrigo Schmidt (JIRA)
  • [jira] Commented: (HADOOP-5620) discp can preserve modification times of files Hadoop QA (JIRA)
• [jira] Updated: (HADOOP-5879) GzipCodec should read compression level etc from configuration He Yongqiang (JIRA)
  • [jira] Updated: (HADOOP-5879) GzipCodec should read compression level etc from configuration He Yongqiang (JIRA)
  • [jira] Updated: (HADOOP-5879) GzipCodec should read compression level etc from configuration Chris Douglas (JIRA)
• [jira] Commented: (HADOOP-5438) Merge FileSystem.create and FileSystem.append Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-5438) Merge FileSystem.create and FileSystem.append dhruba borthakur (JIRA)
  • [jira] Commented: (HADOOP-5438) Merge FileSystem.create and FileSystem.append Hudson (JIRA)
• [jira] Created: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Commented: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Updated: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Updated: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Updated: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Updated: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Commented: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Vinod K V (JIRA)
  • [jira] Updated: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Commented: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Updated: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Updated: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Commented: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Resolved: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hemanth Yamijala (JIRA)
  • [jira] Commented: (HADOOP-5883) TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory Hudson (JIRA)
• [jira] Commented: (HADOOP-5539) o.a.h.mapred.Merger not maintaining map out compression on intermediate files Ravi Gummadi (JIRA)
  • [jira] Commented: (HADOOP-5539) o.a.h.mapred.Merger not maintaining map out compression on intermediate files Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-5539) o.a.h.mapred.Merger not maintaining map out compression on intermediate files Nigel Daley (JIRA)
  • [jira] Commented: (HADOOP-5539) o.a.h.mapred.Merger not maintaining map out compression on intermediate files Billy Pearson (JIRA)
  • [jira] Commented: (HADOOP-5539) o.a.h.mapred.Merger not maintaining map out compression on intermediate files Jothi Padmanabhan (JIRA)
  • [jira] Commented: (HADOOP-5539) o.a.h.mapred.Merger not maintaining map out compression on intermediate files Billy Pearson (JIRA)
  • [jira] Commented: (HADOOP-5539) o.a.h.mapred.Merger not maintaining map out compression on intermediate files Hudson (JIRA)
• [jira] Updated: (HADOOP-4864) -libjars with multiple jars broken when client and cluster reside on different OSs Amareshwari Sriramadasu (JIRA)
  • [jira] Updated: (HADOOP-4864) -libjars with multiple jars broken when client and cluster reside on different OSs Devaraj Das (JIRA)
• Re: doubt regarding multiprocessing in hadoop Steve Loughran
• [jira] Updated: (HADOOP-5710) Counter MAP_INPUT_BYTES missing from new mapreduce api. Amareshwari Sriramadasu (JIRA)
  • [jira] Updated: (HADOOP-5710) Counter MAP_INPUT_BYTES missing from new mapreduce api. Amareshwari Sriramadasu (JIRA)
  • [jira] Updated: (HADOOP-5710) Counter MAP_INPUT_BYTES missing from new mapreduce api. Amareshwari Sriramadasu (JIRA)
  • [jira] Updated: (HADOOP-5710) Counter MAP_INPUT_BYTES missing from new mapreduce api. Sharad Agarwal (JIRA)
• [jira] Commented: (HADOOP-4372) Improve the way the job history files are managed during job recovery Devaraj Das (JIRA)
  • [jira] Commented: (HADOOP-4372) Improve the way the job history files are managed during job recovery Hudson (JIRA)
• [jira] Commented: (HADOOP-5850) map/reduce doesn't run jobs with 0 maps Amareshwari Sriramadasu (JIRA)
  • [jira] Commented: (HADOOP-5850) map/reduce doesn't run jobs with 0 maps Ramya R (JIRA)
  • [jira] Commented: (HADOOP-5850) map/reduce doesn't run jobs with 0 maps Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-5850) map/reduce doesn't run jobs with 0 maps Vinod K V (JIRA)
  • [jira] Commented: (HADOOP-5850) map/reduce doesn't run jobs with 0 maps Amareshwari Sriramadasu (JIRA)
  • [jira] Commented: (HADOOP-5850) map/reduce doesn't run jobs with 0 maps Vinod K V (JIRA)
  • [jira] Commented: (HADOOP-5850) map/reduce doesn't run jobs with 0 maps Ramya R (JIRA)
  • [jira] Commented: (HADOOP-5850) map/reduce doesn't run jobs with 0 maps Vinod K V (JIRA)
  • [jira] Commented: (HADOOP-5850) map/reduce doesn't run jobs with 0 maps Vinod K V (JIRA)
• [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Todd Lipcon (JIRA)
  • [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Todd Lipcon (JIRA)
  • [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Devaraj Das (JIRA)
  • [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Matei Zaharia (JIRA)
  • [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Matei Zaharia (JIRA)
  • [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Hadoop QA (JIRA)
  • [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Matei Zaharia (JIRA)
  • [jira] Commented: (HADOOP-5170) Set max map/reduce tasks on a per-job basis, either per-node or cluster-wide Matei Zaharia (JIRA)
• Build failed in Hudson: Hadoop-Patch-vesta.apache.org #367 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #368 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #369 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #370 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #371 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #372 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #373 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #374 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #375 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #376 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #377 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #378 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #379 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #380 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #381 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #382 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #383 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #384 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #385 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #386 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #387 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #388 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #389 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #390 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #391 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #392 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #393 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #394 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #395 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #396 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #397 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #398 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #399 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #400 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #401 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #402 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #403 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #404 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #405 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #406 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #407 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #408 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #409 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #410 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #411 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #412 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #413 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #414 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #415 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #416 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #417 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #418 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #419 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #420 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #421 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #422 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #423 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #424 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #425 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #426 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #427 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #428 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #429 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #430 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #431 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #432 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #433 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #434 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #435 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #436 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #437 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #438 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #439 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #440 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #441 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #442 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #443 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #444 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #445 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #446 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #447 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #448 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #449 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #450 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #451 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #452 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #453 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #454 Apache Hudson Server
  • Build failed in Hudson: Hadoop-Patch-vesta.apache.org #455 Apache Hudson Server

• Earlier messages
• Later messages