| ÖÜ»Ô |
I can run hadoop, |
Sat, 03 Jan, 06:44 |
| Nicolas Lalevée |
Hadoop-Patch-Admin job on Hudson |
Sun, 25 Jan, 12:06 |
| Nicolas Lalevée |
Re: Hadoop-Patch-Admin job on Hudson |
Mon, 26 Jan, 10:05 |
| Doğacan Güney (JIRA) |
[jira] Created: (HADOOP-5142) MapWritable#putAll does not store classes |
Thu, 29 Jan, 19:39 |
| Doğacan Güney (JIRA) |
[jira] Updated: (HADOOP-5142) MapWritable#putAll does not store classes |
Thu, 29 Jan, 19:41 |
| Aaron Kimball |
Re: I can run hadoop, |
Mon, 05 Jan, 04:16 |
| Abdul Qadeer (JIRA) |
[jira] Commented: (HADOOP-4012) Providing splitting support for bzip2 compressed files |
Fri, 09 Jan, 15:41 |
| Abdul Qadeer (JIRA) |
[jira] Commented: (HADOOP-4918) Make bzip2 work with SequenceFile |
Thu, 15 Jan, 06:19 |
| Alan Ho (JIRA) |
[jira] Commented: (HADOOP-2439) Hadoop needs a better XML Input |
Fri, 30 Jan, 22:46 |
| Alan Ho (JIRA) |
[jira] Updated: (HADOOP-2439) Hadoop needs a better XML Input |
Fri, 30 Jan, 22:48 |
| Alejandro Abdelnur (JIRA) |
[jira] Created: (HADOOP-5000) A Configuration instance cannot be reloaded if the configuration has InputStream resources |
Fri, 09 Jan, 07:20 |
| Alejandro Abdelnur (JIRA) |
[jira] Commented: (HADOOP-5000) A Configuration instance cannot be reloaded if the configuration has InputStream resources |
Fri, 09 Jan, 07:24 |
| Alejandro Abdelnur (JIRA) |
[jira] Commented: (HADOOP-5000) A Configuration instance cannot be reloaded if the configuration has InputStream resources |
Mon, 12 Jan, 07:58 |
| Alex Loddengaard (JIRA) |
[jira] Commented: (HADOOP-4675) Current Ganglia metrics implementation is incompatible with Ganglia 3.1 |
Tue, 27 Jan, 14:59 |
| Allen Wittenauer (JIRA) |
[jira] Commented: (HADOOP-4656) Add a user to groups mapping service |
Mon, 12 Jan, 19:52 |
| Allen Wittenauer (JIRA) |
[jira] Commented: (HADOOP-4998) Implement a native OS runtime for Hadoop |
Mon, 12 Jan, 19:56 |
| Allen Wittenauer (JIRA) |
[jira] Commented: (HADOOP-4656) Add a user to groups mapping service |
Tue, 13 Jan, 17:38 |
| Allen Wittenauer (JIRA) |
[jira] Commented: (HADOOP-5059) 'whoami', 'topologyscript' calls failing with java.io.IOException: error=12, Cannot allocate memory |
Thu, 15 Jan, 23:36 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4933) ConcurrentModificationException in JobHistory.java |
Fri, 02 Jan, 04:13 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4966) Setup tasks are not removed from JobTracker's taskIdToTIPMap even after the job completes |
Fri, 02 Jan, 04:17 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4933) ConcurrentModificationException in JobHistory.java |
Fri, 02 Jan, 04:25 |
| Amar Kamat (JIRA) |
[jira] Assigned: (HADOOP-4933) ConcurrentModificationException in JobHistory.java |
Fri, 02 Jan, 04:25 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Fri, 02 Jan, 07:37 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-4973) Allow jobtracker to be configured with zero completed jobs in memory |
Fri, 02 Jan, 08:19 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-4974) Make jobtracker resilient to memory issues |
Fri, 02 Jan, 08:29 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4974) Make jobtracker resilient to memory issues |
Fri, 02 Jan, 08:51 |
| Amar Kamat (JIRA) |
[jira] Assigned: (HADOOP-4638) Exception thrown in/from RecoveryManager.recover() should be caught and handled |
Fri, 02 Jan, 09:19 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Fri, 02 Jan, 12:19 |
| Amar Kamat (JIRA) |
[jira] Assigned: (HADOOP-4977) Deadlock between reclaimCapacity and assignTasks |
Mon, 05 Jan, 08:41 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4933) ConcurrentModificationException in JobHistory.java |
Mon, 05 Jan, 11:49 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4933) ConcurrentModificationException in JobHistory.java |
Tue, 06 Jan, 07:39 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4977) Deadlock between reclaimCapacity and assignTasks |
Wed, 07 Jan, 07:52 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Wed, 07 Jan, 11:58 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-4992) TestCustomOutputCommitter fails on hadoop-0.19 |
Thu, 08 Jan, 07:08 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Thu, 08 Jan, 09:01 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Thu, 08 Jan, 14:14 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Fri, 09 Jan, 03:02 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Fri, 09 Jan, 10:07 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5004) 'job -kill' from command line should inform if the job doesn't exit |
Fri, 09 Jan, 15:22 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5004) 'job -kill' from command line should inform if the job doesn't exist |
Fri, 09 Jan, 15:24 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Sat, 10 Jan, 06:45 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Sun, 11 Jan, 15:08 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5013) JobTracker should not expand jobs if its running low on memory |
Mon, 12 Jan, 07:56 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4977) Deadlock between reclaimCapacity and assignTasks |
Mon, 12 Jan, 11:39 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Tue, 13 Jan, 05:59 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4977) Deadlock between reclaimCapacity and assignTasks |
Tue, 13 Jan, 06:23 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5020) JobStatus of killed JobInProgress does carry forward start time of the Job |
Tue, 13 Jan, 10:31 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5049) Jobs with 0 maps will never get removed from the default scheduler |
Thu, 15 Jan, 08:57 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Thu, 15 Jan, 10:51 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5020) JobStatus of killed JobInProgress does not carry forward start time of the Job |
Thu, 15 Jan, 11:36 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5048) Sometimes job is still displayed in jobqueue_details page for long time after job was killed. |
Thu, 15 Jan, 11:55 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5048) Sometimes job is still displayed in jobqueue_details page for long time after job was killed. |
Fri, 16 Jan, 04:11 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5020) JobStatus of killed JobInProgress does not carry forward start time of the Job |
Fri, 16 Jan, 14:09 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5049) Jobs with 0 maps will never get removed from the default scheduler |
Sat, 17 Jan, 17:30 |
| Amar Kamat (JIRA) |
[jira] Assigned: (HADOOP-5049) Jobs with 0 maps will never get removed from the default scheduler |
Sat, 17 Jan, 17:32 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Sun, 18 Jan, 09:43 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5082) No way to retrieve JobID from Job |
Tue, 20 Jan, 07:34 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5082) No way to retrieve JobID from Job |
Tue, 20 Jan, 09:27 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5082) Job.getJobID() will always return null |
Tue, 20 Jan, 09:33 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Wed, 21 Jan, 04:49 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Wed, 21 Jan, 05:25 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Wed, 21 Jan, 05:40 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Thu, 22 Jan, 09:09 |
| Amar Kamat (JIRA) |
[jira] Assigned: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Thu, 22 Jan, 11:42 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Thu, 22 Jan, 11:51 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5049) Jobs with 0 maps will never get removed from the default scheduler |
Fri, 23 Jan, 04:56 |
| Amar Kamat (JIRA) |
[jira] Resolved: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Fri, 23 Jan, 15:39 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Wed, 28 Jan, 18:05 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Thu, 29 Jan, 02:59 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Thu, 29 Jan, 08:21 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Thu, 29 Jan, 08:54 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4766) Hadoop performance degrades significantly as more and more jobs complete |
Thu, 29 Jan, 09:55 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Fri, 30 Jan, 04:57 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Fri, 30 Jan, 06:39 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4934) Distinguish running/successful/failed/killed jobs in jobtracker's history |
Fri, 30 Jan, 13:05 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Fri, 30 Jan, 13:59 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4963) Logs saying org.apache.hadoop.util.DiskChecker$DiskErrorException in TaskTracker are not relevant |
Fri, 02 Jan, 04:05 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4963) Logs saying org.apache.hadoop.util.DiskChecker$DiskErrorException in TaskTracker are not relevant |
Fri, 02 Jan, 04:05 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Assigned: (HADOOP-4966) Setup tasks are not removed from JobTracker's taskIdToTIPMap even after the job completes |
Fri, 02 Jan, 04:31 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4966) Setup tasks are not removed from JobTracker's taskIdToTIPMap even after the job completes |
Fri, 02 Jan, 04:49 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4966) Setup tasks are not removed from JobTracker's taskIdToTIPMap even after the job completes |
Fri, 02 Jan, 04:49 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Commented: (HADOOP-4966) Setup tasks are not removed from JobTracker's taskIdToTIPMap even after the job completes |
Fri, 02 Jan, 13:49 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Commented: (HADOOP-4963) Logs saying org.apache.hadoop.util.DiskChecker$DiskErrorException in TaskTracker are not relevant |
Tue, 06 Jan, 06:17 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Commented: (HADOOP-4847) OutputCommitter is loaded in the TaskTracker in localizeConfiguration |
Tue, 06 Jan, 07:33 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Assigned: (HADOOP-4730) multi-threaded merge phase |
Tue, 06 Jan, 08:03 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Commented: (HADOOP-4983) Job counters sometimes go down as tasks run without task failures |
Wed, 07 Jan, 06:20 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Commented: (HADOOP-4987) One more illegal map task been launched when the job almost complete |
Wed, 07 Jan, 07:36 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4992) TestCustomOutputCommitter fails on hadoop-0.19 |
Thu, 08 Jan, 07:24 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4992) TestCustomOutputCommitter fails on hadoop-0.19 |
Thu, 08 Jan, 07:24 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4992) TestCustomOutputCommitter fails on hadoop-0.19 |
Thu, 08 Jan, 07:28 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4759) HADOOP-4654 to be fixed for branches >= 0.19 |
Fri, 09 Jan, 03:58 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Commented: (HADOOP-3327) Shuffling fetchers waited too long between map output fetch re-tries |
Fri, 09 Jan, 04:38 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-5002) 2 core tests TestFileOutputFormat and TestHarFileSystem are failing in branch 19 |
Fri, 09 Jan, 09:14 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-5002) 2 core tests TestFileOutputFormat and TestHarFileSystem are failing in branch 19 |
Mon, 12 Jan, 06:12 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4759) HADOOP-4654 to be fixed for branches >= 0.19 |
Tue, 13 Jan, 10:15 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4759) HADOOP-4654 to be fixed for branches >= 0.19 |
Tue, 13 Jan, 10:17 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Commented: (HADOOP-4828) Update documentation for default configuration |
Thu, 15 Jan, 06:09 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4759) HADOOP-4654 to be fixed for branches >= 0.19 |
Thu, 15 Jan, 07:53 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Commented: (HADOOP-4759) HADOOP-4654 to be fixed for branches >= 0.19 |
Thu, 15 Jan, 07:53 |
| Amareshwari Sriramadasu (JIRA) |
[jira] Updated: (HADOOP-4983) Job counters sometimes go down as tasks run without task failures |
Thu, 15 Jan, 08:57 |