|
[jira] Updated: (HADOOP-3810) NameNode seems unstable on a cluster with little space left |
|
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-3810) NameNode seems unstable on a cluster with little space left |
Wed, 01 Apr, 00:11 |
| Raghu Angadi (JIRA) |
[jira] Updated: (HADOOP-3810) NameNode seems unstable on a cluster with little space left |
Mon, 06 Apr, 22:54 |
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-3810) NameNode seems unstable on a cluster with little space left |
Mon, 06 Apr, 23:14 |
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-3810) NameNode seems unstable on a cluster with little space left |
Tue, 07 Apr, 18:04 |
| Raghu Angadi (JIRA) |
[jira] Created: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Wed, 01 Apr, 00:21 |
|
[jira] Commented: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
|
| Raghu Angadi (JIRA) |
[jira] Commented: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Wed, 01 Apr, 00:35 |
| Raghu Angadi (JIRA) |
[jira] Commented: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Thu, 02 Apr, 18:31 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Thu, 02 Apr, 20:59 |
| Hairong Kuang (JIRA) |
[jira] Commented: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Thu, 02 Apr, 23:09 |
| Hairong Kuang (JIRA) |
[jira] Commented: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Thu, 02 Apr, 23:51 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Fri, 03 Apr, 15:24 |
|
[jira] Updated: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
|
| Raghu Angadi (JIRA) |
[jira] Updated: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Wed, 01 Apr, 00:39 |
| Raghu Angadi (JIRA) |
[jira] Updated: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Wed, 01 Apr, 00:41 |
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Wed, 01 Apr, 18:06 |
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Wed, 01 Apr, 23:14 |
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Thu, 02 Apr, 20:23 |
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Thu, 02 Apr, 20:23 |
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Thu, 02 Apr, 23:59 |
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Wed, 15 Apr, 17:16 |
|
[jira] Commented: (HADOOP-4652) RAgzip: multiple map tasks for a large gzipped file |
|
| Chris Douglas (JIRA) |
[jira] Commented: (HADOOP-4652) RAgzip: multiple map tasks for a large gzipped file |
Wed, 01 Apr, 01:29 |
| Chris Douglas (JIRA) |
[jira] Commented: (HADOOP-4652) RAgzip: multiple map tasks for a large gzipped file |
Wed, 01 Apr, 01:31 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-4652) RAgzip: multiple map tasks for a large gzipped file |
Wed, 01 Apr, 08:35 |
| Daehyun Kim (JIRA) |
[jira] Commented: (HADOOP-4652) RAgzip: multiple map tasks for a large gzipped file |
Wed, 01 Apr, 10:22 |
|
[jira] Commented: (HADOOP-5469) Exposing Hadoop metrics via HTTP |
|
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5469) Exposing Hadoop metrics via HTTP |
Wed, 01 Apr, 01:33 |
| Philip Zeyliger (JIRA) |
[jira] Commented: (HADOOP-5469) Exposing Hadoop metrics via HTTP |
Wed, 01 Apr, 01:39 |
| Chris Douglas (JIRA) |
[jira] Commented: (HADOOP-5469) Exposing Hadoop metrics via HTTP |
Tue, 07 Apr, 21:58 |
| Allen Wittenauer (JIRA) |
[jira] Commented: (HADOOP-5469) Exposing Hadoop metrics via HTTP |
Wed, 22 Apr, 16:42 |
| Philip Zeyliger (JIRA) |
[jira] Commented: (HADOOP-5469) Exposing Hadoop metrics via HTTP |
Wed, 22 Apr, 16:52 |
| Marco Nicosia (JIRA) |
[jira] Commented: (HADOOP-5469) Exposing Hadoop metrics via HTTP |
Wed, 22 Apr, 16:56 |
|
[jira] Commented: (HADOOP-5604) TestBinaryPartitioner javac warnings. |
|
| Konstantin Shvachko (JIRA) |
[jira] Commented: (HADOOP-5604) TestBinaryPartitioner javac warnings. |
Wed, 01 Apr, 01:41 |
| Chris Douglas (JIRA) |
[jira] Commented: (HADOOP-5604) TestBinaryPartitioner javac warnings. |
Wed, 01 Apr, 02:08 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5604) TestBinaryPartitioner javac warnings. |
Wed, 01 Apr, 12:01 |
| Konstantin Shvachko (JIRA) |
[jira] Commented: (HADOOP-5604) TestBinaryPartitioner javac warnings. |
Wed, 01 Apr, 19:04 |
| Klaas Bosteels (JIRA) |
[jira] Commented: (HADOOP-5604) TestBinaryPartitioner javac warnings. |
Wed, 01 Apr, 21:35 |
|
[jira] Commented: (HADOOP-5585) FileSystem statistic counters are too high when JVM reuse is enabled. |
|
| Chris Douglas (JIRA) |
[jira] Commented: (HADOOP-5585) FileSystem statistic counters are too high when JVM reuse is enabled. |
Wed, 01 Apr, 02:20 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5585) FileSystem statistic counters are too high when JVM reuse is enabled. |
Tue, 07 Apr, 09:33 |
| Chris Douglas (JIRA) |
[jira] Commented: (HADOOP-5585) FileSystem statistic counters are too high when JVM reuse is enabled. |
Tue, 07 Apr, 21:02 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5585) FileSystem statistic counters are too high when JVM reuse is enabled. |
Wed, 08 Apr, 06:14 |
|
[jira] Commented: (HADOOP-5337) JobTracker greedily schedules tasks without running tasks to join |
|
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5337) JobTracker greedily schedules tasks without running tasks to join |
Wed, 01 Apr, 03:46 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5337) JobTracker greedily schedules tasks without running tasks to join |
Wed, 01 Apr, 11:35 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-5337) JobTracker greedily schedules tasks without running tasks to join |
Fri, 03 Apr, 15:24 |
|
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
|
| Vinod K V (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Wed, 01 Apr, 03:48 |
| Vinod K V (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Wed, 01 Apr, 03:48 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Tue, 07 Apr, 09:03 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Tue, 07 Apr, 09:07 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Tue, 07 Apr, 09:17 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Thu, 09 Apr, 10:14 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Mon, 13 Apr, 09:38 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Tue, 14 Apr, 04:11 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Tue, 14 Apr, 09:44 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Tue, 14 Apr, 09:44 |
| Hemanth Yamijala (JIRA) |
[jira] Updated: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Thu, 16 Apr, 18:00 |
|
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
|
| Sreekanth Ramakrishnan (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Wed, 01 Apr, 04:43 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Wed, 01 Apr, 18:22 |
| Hemanth Yamijala (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Wed, 08 Apr, 17:14 |
| Hemanth Yamijala (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Thu, 09 Apr, 03:40 |
| Vinod K V (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Thu, 09 Apr, 06:42 |
| Hemanth Yamijala (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Mon, 13 Apr, 06:15 |
| Hemanth Yamijala (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Mon, 13 Apr, 17:56 |
| Hemanth Yamijala (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Tue, 14 Apr, 09:39 |
| Vinod K V (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Thu, 16 Apr, 07:00 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Thu, 16 Apr, 08:13 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Thu, 16 Apr, 09:30 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Mon, 20 Apr, 09:42 |
|
[jira] Commented: (HADOOP-5595) NameNode does not need to run a replicator to choose a random DataNode |
|
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5595) NameNode does not need to run a replicator to choose a random DataNode |
Wed, 01 Apr, 05:03 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-5595) NameNode does not need to run a replicator to choose a random DataNode |
Fri, 03 Apr, 15:24 |
| Devaraj Das (JIRA) |
[jira] Updated: (HADOOP-4374) JVM should not be killed but given an opportunity to exit gracefully |
Wed, 01 Apr, 05:22 |
|
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
|
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Wed, 01 Apr, 09:31 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Wed, 01 Apr, 09:51 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 06 Apr, 09:52 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 06 Apr, 10:08 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 06 Apr, 10:54 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Wed, 08 Apr, 03:47 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Wed, 08 Apr, 03:47 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 13 Apr, 04:20 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 13 Apr, 04:22 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 13 Apr, 04:22 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 13 Apr, 05:45 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 13 Apr, 05:47 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Tue, 14 Apr, 06:41 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Wed, 15 Apr, 05:16 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Wed, 15 Apr, 06:06 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Wed, 15 Apr, 06:06 |
| Hemanth Yamijala (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Thu, 16 Apr, 18:32 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5606) Final parameters in Configuration doesnt get serialized |
Wed, 01 Apr, 09:41 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5606) Final parameters in Configuration doesnt get serialized |
Wed, 01 Apr, 09:43 |
|
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
|
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 01 Apr, 11:37 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 01 Apr, 11:37 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 01 Apr, 11:59 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 01 Apr, 12:01 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Thu, 02 Apr, 09:40 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Fri, 03 Apr, 10:56 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 08 Apr, 08:13 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 08 Apr, 08:20 |
| Sharad Agarwal (JIRA) |
[jira] Updated: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 08 Apr, 12:57 |
|
[jira] Updated: (HADOOP-5252) Streaming overrides -inputformat option |
|
| Klaas Bosteels (JIRA) |
[jira] Updated: (HADOOP-5252) Streaming overrides -inputformat option |
Wed, 01 Apr, 11:53 |
| Klaas Bosteels (JIRA) |
[jira] Updated: (HADOOP-5252) Streaming overrides -inputformat option |
Wed, 01 Apr, 11:55 |
|
Build failed in Hudson: Hadoop-trunk #794 |
|
| Apache Hudson Server |
Build failed in Hudson: Hadoop-trunk #794 |
Wed, 01 Apr, 12:02 |
| Apache Hudson Server |
Build failed in Hudson: Hadoop-trunk #795 |
Thu, 02 Apr, 12:13 |
| Apache Hudson Server |
Hudson build is back to normal: Hadoop-trunk #796 |
Fri, 03 Apr, 15:24 |
|
[jira] Commented: (HADOOP-4665) Add preemption to the fair scheduler |
|
| Vinod K V (JIRA) |
[jira] Commented: (HADOOP-4665) Add preemption to the fair scheduler |
Wed, 01 Apr, 13:33 |
| Vinod K V (JIRA) |
[jira] Commented: (HADOOP-4665) Add preemption to the fair scheduler |
Wed, 01 Apr, 13:37 |
| Vinod K V (JIRA) |
[jira] Commented: (HADOOP-4665) Add preemption to the fair scheduler |
Wed, 01 Apr, 13:43 |
| Matei Zaharia (JIRA) |
[jira] Commented: (HADOOP-4665) Add preemption to the fair scheduler |
Wed, 01 Apr, 18:20 |
| Matei Zaharia (JIRA) |
[jira] Commented: (HADOOP-4665) Add preemption to the fair scheduler |
Thu, 09 Apr, 20:04 |
| Hemanth Yamijala (JIRA) |
[jira] Commented: (HADOOP-4665) Add preemption to the fair scheduler |
Sun, 12 Apr, 08:13 |
| Vinod K V (JIRA) |
[jira] Commented: (HADOOP-4665) Add preemption to the fair scheduler |
Wed, 15 Apr, 04:20 |
|
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
|
| Jothi Padmanabhan (JIRA) |
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Wed, 01 Apr, 14:29 |
| Jothi Padmanabhan (JIRA) |
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Fri, 24 Apr, 10:48 |
| Jothi Padmanabhan (JIRA) |
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Fri, 24 Apr, 10:50 |
| Jothi Padmanabhan (JIRA) |
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Tue, 28 Apr, 02:58 |
| Jothi Padmanabhan (JIRA) |
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Tue, 28 Apr, 03:00 |
| Jothi Padmanabhan (JIRA) |
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Tue, 28 Apr, 03:00 |
| Jothi Padmanabhan (JIRA) |
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Wed, 29 Apr, 08:36 |
| Jothi Padmanabhan (JIRA) |
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Wed, 29 Apr, 08:36 |
| Jothi Padmanabhan (JIRA) |
[jira] Updated: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Wed, 29 Apr, 08:38 |
|
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
|
| Jothi Padmanabhan (JIRA) |
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Wed, 01 Apr, 14:29 |
| Doug Cutting (JIRA) |
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Tue, 07 Apr, 22:58 |
| Jothi Padmanabhan (JIRA) |
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Wed, 08 Apr, 08:07 |
| Devaraj Das (JIRA) |
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Wed, 15 Apr, 13:51 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Sun, 26 Apr, 04:25 |
| Devaraj Das (JIRA) |
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Mon, 27 Apr, 11:18 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Tue, 28 Apr, 13:59 |
| Jothi Padmanabhan (JIRA) |
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Wed, 29 Apr, 03:37 |
| Jothi Padmanabhan (JIRA) |
[jira] Commented: (HADOOP-5266) Values Iterator should support "mark" and "reset" |
Wed, 29 Apr, 15:38 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5460) Job recovery should fail or kill a job that fails ACL checks upon restart, if the job was running previously |
Wed, 01 Apr, 14:39 |
|
[jira] Commented: (HADOOP-2413) Is FSNamesystem.fsNamesystemObject unique? |
|
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-2413) Is FSNamesystem.fsNamesystemObject unique? |
Wed, 01 Apr, 15:13 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-2413) Is FSNamesystem.fsNamesystemObject unique? |
Fri, 03 Apr, 15:24 |
| Chris Douglas (JIRA) |
[jira] Created: (HADOOP-5607) TestCapacityScheduler fails with NPE |
Wed, 01 Apr, 16:11 |
| sam rash (JIRA) |
[jira] Created: (HADOOP-5608) NullPointerException when retrieving task reports |
Wed, 01 Apr, 17:42 |
|
[jira] Commented: (HADOOP-5608) NullPointerException when retrieving task reports |
|
| sam rash (JIRA) |
[jira] Commented: (HADOOP-5608) NullPointerException when retrieving task reports |
Wed, 01 Apr, 17:44 |
| sam rash (JIRA) |
[jira] Commented: (HADOOP-5608) NullPointerException when retrieving task reports |
Wed, 01 Apr, 17:44 |
| sam rash (JIRA) |
[jira] Commented: (HADOOP-5608) NullPointerException when retrieving task reports |
Wed, 01 Apr, 17:48 |
| Devaraj Das (JIRA) |
[jira] Updated: (HADOOP-5608) NullPointerException when retrieving task reports |
Wed, 01 Apr, 17:56 |
| Hairong Kuang (JIRA) |
[jira] Assigned: (HADOOP-5605) All the replicas incorrectly got marked as corrupt. |
Wed, 01 Apr, 18:06 |
|
[jira] Updated: (HADOOP-5607) TestCapacityScheduler fails with NPE |
|
| Chris Douglas (JIRA) |
[jira] Updated: (HADOOP-5607) TestCapacityScheduler fails with NPE |
Wed, 01 Apr, 18:18 |
| Chris Douglas (JIRA) |
[jira] Updated: (HADOOP-5607) TestCapacityScheduler fails with NPE |
Wed, 01 Apr, 18:20 |
| Chris Douglas (JIRA) |
[jira] Updated: (HADOOP-5607) TestCapacityScheduler fails with NPE |
Wed, 01 Apr, 22:03 |
| Qi Liu (JIRA) |
[jira] Created: (HADOOP-5609) Reducers continue to run even if a job failed. |
Wed, 01 Apr, 18:22 |
| Matei Zaharia (JIRA) |
[jira] Issue Comment Edited: (HADOOP-4665) Add preemption to the fair scheduler |
Wed, 01 Apr, 18:22 |
|
[jira] Commented: (HADOOP-5607) TestCapacityScheduler fails with NPE |
|
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Commented: (HADOOP-5607) TestCapacityScheduler fails with NPE |
Wed, 01 Apr, 18:24 |
| Chris Douglas (JIRA) |
[jira] Commented: (HADOOP-5607) TestCapacityScheduler fails with NPE |
Wed, 01 Apr, 21:55 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-5607) TestCapacityScheduler fails with NPE |
Fri, 03 Apr, 15:24 |
| Suman Sehgal (JIRA) |
[jira] Commented: (HADOOP-5597) create_write operation of nnbench is failing. |
Wed, 01 Apr, 18:26 |
|
[jira] Updated: (HADOOP-2413) Is FSNamesystem.fsNamesystemObject unique? |
|
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Updated: (HADOOP-2413) Is FSNamesystem.fsNamesystemObject unique? |
Wed, 01 Apr, 18:40 |
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Updated: (HADOOP-2413) Is FSNamesystem.fsNamesystemObject unique? |
Wed, 01 Apr, 18:46 |
|
[jira] Commented: (HADOOP-5191) After creation and startup of the hadoop namenode on AIX or Solaris, you will only be allowed to connect to the namenode via hostname but not IP. |
|
| Bill Habermaas (JIRA) |
[jira] Commented: (HADOOP-5191) After creation and startup of the hadoop namenode on AIX or Solaris, you will only be allowed to connect to the namenode via hostname but not IP. |
Wed, 01 Apr, 18:40 |
| Raghu Angadi (JIRA) |
[jira] Commented: (HADOOP-5191) After creation and startup of the hadoop namenode on AIX or Solaris, you will only be allowed to connect to the namenode via hostname but not IP. |
Wed, 01 Apr, 18:44 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-5191) After creation and startup of the hadoop namenode on AIX or Solaris, you will only be allowed to connect to the namenode via hostname but not IP. |
Fri, 03 Apr, 15:24 |
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Resolved: (HADOOP-5119) FSEditLog should not use FSNamesystem.getFSNamesystem() |
Wed, 01 Apr, 18:48 |
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Resolved: (HADOOP-5559) BackupStorage should not use FSNamesystem.getFSNamesystem() |
Wed, 01 Apr, 18:48 |
| Bill Habermaas (JIRA) |
[jira] Created: (HADOOP-5610) When connecting to HDFS using an IP Task MapRed gets confused when checking the output path. |
Wed, 01 Apr, 19:06 |
| Konstantin Shvachko (JIRA) |
[jira] Reopened: (HADOOP-5528) Binary partitioner |
Wed, 01 Apr, 19:29 |