| ²Üéªéª |
Where is the data in Reporter ? |
Wed, 25 Feb, 11:12 |
| Luká¹ Vlèek |
Re: Integration with SGE |
Wed, 18 Feb, 09:49 |
| Luká¹ Vlèek |
Re: Integration with SGE |
Wed, 18 Feb, 18:01 |
| Aaron Kimball (JIRA) |
[jira] Created: (HADOOP-5240) 'ant javadoc' does not check whether outputs are up to date and always rebuilds |
Thu, 12 Feb, 21:02 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-5240) 'ant javadoc' does not check whether outputs are up to date and always rebuilds |
Thu, 12 Feb, 21:04 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-5240) 'ant javadoc' does not check whether outputs are up to date and always rebuilds |
Thu, 12 Feb, 21:04 |
| Aaron Kimball (JIRA) |
[jira] Commented: (HADOOP-3126) org.apache.hadoop.examples.RandomTextWriter$Counters fluctuate when RandonTextWriter job is running |
Thu, 12 Feb, 23:17 |
| Aaron Kimball (JIRA) |
[jira] Commented: (HADOOP-5240) 'ant javadoc' does not check whether outputs are up to date and always rebuilds |
Fri, 13 Feb, 21:54 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-5240) 'ant javadoc' does not check whether outputs are up to date and always rebuilds |
Mon, 23 Feb, 22:06 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-5240) 'ant javadoc' does not check whether outputs are up to date and always rebuilds |
Mon, 23 Feb, 22:06 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-5240) 'ant javadoc' does not check whether outputs are up to date and always rebuilds |
Mon, 23 Feb, 22:06 |
| Aaron Kimball (JIRA) |
[jira] Commented: (HADOOP-4346) Hadoop triggers a "soft" fd leak. |
Mon, 23 Feb, 22:50 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-4346) Hadoop triggers a "soft" fd leak. |
Mon, 23 Feb, 22:54 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-4346) Hadoop triggers a "soft" fd leak. |
Mon, 23 Feb, 23:00 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-4346) Hadoop triggers a "soft" fd leak. |
Mon, 23 Feb, 23:00 |
| Aaron Kimball (JIRA) |
[jira] Commented: (HADOOP-4346) Hadoop triggers a "soft" fd leak. |
Mon, 23 Feb, 23:28 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-4346) Hadoop triggers a "soft" fd leak. |
Mon, 23 Feb, 23:48 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-4346) Hadoop triggers a "soft" fd leak. |
Mon, 23 Feb, 23:54 |
| Aaron Kimball (JIRA) |
[jira] Updated: (HADOOP-5240) 'ant javadoc' does not check whether outputs are up to date and always rebuilds |
Tue, 24 Feb, 19:11 |
| Abdul Qadeer (JIRA) |
[jira] Commented: (HADOOP-5213) BZip2CompressionOutputStream NullPointerException |
Fri, 13 Feb, 07:27 |
| Ajit Ratnaparkhi |
help needed regarding hadoop development |
Thu, 19 Feb, 16:42 |
| Ajit Ratnaparkhi |
Re: help needed regarding hadoop development |
Sun, 22 Feb, 06:29 |
| Ajit Ratnaparkhi |
Re: HDFS Client side buffering |
Mon, 23 Feb, 14:55 |
| Ajit Ratnaparkhi |
multiple datanodes on single node cluster |
Thu, 26 Feb, 07:04 |
| Ajit Ratnaparkhi |
Re: Contributing to hadoop |
Thu, 26 Feb, 07:23 |
| Alan Ho (JIRA) |
[jira] Commented: (HADOOP-2439) Hadoop needs a better XML Input |
Mon, 09 Feb, 17:56 |
| Alan Ho (JIRA) |
[jira] Updated: (HADOOP-2439) Hadoop needs a better XML Input |
Mon, 09 Feb, 17:58 |
| Alan Ho (JIRA) |
[jira] Updated: (HADOOP-2439) Hadoop needs a better XML Input |
Mon, 09 Feb, 17:58 |
| Alan Ho (JIRA) |
[jira] Commented: (HADOOP-2439) Hadoop needs a better XML Input |
Sat, 14 Feb, 01:17 |
| Alejandro Abdelnur (JIRA) |
[jira] Created: (HADOOP-5303) Hadoop Workflow System (HWS) |
Sun, 22 Feb, 03:43 |
| Alejandro Abdelnur (JIRA) |
[jira] Updated: (HADOOP-5303) Hadoop Workflow System (HWS) |
Sun, 22 Feb, 03:47 |
| Alejandro Abdelnur (JIRA) |
[jira] Updated: (HADOOP-5303) Hadoop Workflow System (HWS) |
Sun, 22 Feb, 03:49 |
| Alejandro Abdelnur (JIRA) |
[jira] Commented: (HADOOP-5303) Hadoop Workflow System (HWS) |
Mon, 23 Feb, 12:01 |
| Alejandro Abdelnur (JIRA) |
[jira] Commented: (HADOOP-5303) Hadoop Workflow System (HWS) |
Mon, 23 Feb, 23:52 |
| Alejandro Abdelnur (JIRA) |
[jira] Commented: (HADOOP-5303) Hadoop Workflow System (HWS) |
Wed, 25 Feb, 16:21 |
| Alex Loddengaard (JIRA) |
[jira] Commented: (HADOOP-4757) Replace log4j.properties with log4j.xml |
Thu, 26 Feb, 09:05 |
| Amandeep Khurana |
Unable to connect to SVN repository |
Wed, 04 Feb, 20:00 |
| Amandeep Khurana |
Re: Unable to connect to SVN repository |
Sun, 08 Feb, 01:44 |
| Amandeep Khurana |
Re: Unable to connect to SVN repository |
Mon, 09 Feb, 19:17 |
| Amandeep Khurana |
HDFS architecture based on GFS? |
Sun, 15 Feb, 19:57 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Sun, 15 Feb, 21:36 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Sun, 15 Feb, 23:20 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Sun, 15 Feb, 23:22 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Mon, 16 Feb, 01:32 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Mon, 16 Feb, 02:00 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Mon, 16 Feb, 02:14 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Mon, 16 Feb, 03:15 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Mon, 16 Feb, 04:07 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Mon, 16 Feb, 04:43 |
| Amandeep Khurana |
Re: HDFS architecture based on GFS? |
Tue, 17 Feb, 00:54 |
| Amandeep Khurana |
Re: [VOTE] Release Hadoop 0.19.1 (candidate 0) |
Mon, 23 Feb, 07:26 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5166) JobTracker fails to restart if recovery and ACLs are enabled |
Wed, 04 Feb, 13:55 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5166) JobTracker fails to restart if recovery and ACLs are enabled |
Wed, 04 Feb, 13:57 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5067) Failed/Killed attempts column in jobdetails.jsp does not show the number of failed/killed attempts correctly |
Fri, 06 Feb, 08:07 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5067) Failed/Killed attempts column in jobdetails.jsp does not show the number of failed/killed attempts correctly |
Fri, 06 Feb, 11:47 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Tue, 10 Feb, 06:48 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes, can time out very easily |
Tue, 10 Feb, 11:57 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Tue, 10 Feb, 12:23 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4191) Add a testcase for jobhistory |
Tue, 10 Feb, 17:44 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5166) JobTracker fails to restart if recovery and ACLs are enabled |
Wed, 11 Feb, 04:01 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes, can time out very easily |
Wed, 11 Feb, 04:02 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes, can time out very easily |
Wed, 11 Feb, 04:02 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5166) JobTracker fails to restart if recovery and ACLs are enabled |
Wed, 11 Feb, 10:14 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes, can time out very easily |
Thu, 12 Feb, 05:47 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes, can time out very easily |
Thu, 12 Feb, 05:49 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes, can time out very easily |
Thu, 12 Feb, 05:49 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5166) JobTracker fails to restart if recovery and ACLs are enabled |
Thu, 12 Feb, 13:53 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes, can time out very easily |
Fri, 13 Feb, 04:27 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes, can time out very easily |
Fri, 13 Feb, 04:31 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5020) JobStatus of killed JobInProgress does not carry forward start time of the Job |
Fri, 13 Feb, 05:23 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4933) ConcurrentModificationException in JobHistory.java |
Fri, 13 Feb, 05:37 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5247) NPEs in JobTracker and JobClient when mapred.jobtracker.completeuserjobs.maximum is set to zero. |
Fri, 13 Feb, 07:05 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5247) NPEs in JobTracker and JobClient when mapred.jobtracker.completeuserjobs.maximum is set to zero. |
Fri, 13 Feb, 08:57 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5249) Remove getNumResolvedTaskTrackers() api from JobTracker |
Fri, 13 Feb, 09:31 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5250) There can be more than 'mapred.jobtracker.completeuserjobs.maximum' jobs for a user in the jobtracker |
Fri, 13 Feb, 09:57 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5247) NPEs in JobTracker and JobClient when mapred.jobtracker.completeuserjobs.maximum is set to zero. |
Fri, 13 Feb, 13:43 |
| Amar Kamat (JIRA) |
[jira] Resolved: (HADOOP-4934) Distinguish running/successful/failed/killed jobs in jobtracker's history |
Fri, 13 Feb, 13:53 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-4638) Exception thrown in/from RecoveryManager.recover() should be caught and handled |
Mon, 16 Feb, 14:07 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5272) TaskInProgress.isFirstAttempt() does not log TIP start information after JobTracker restart |
Tue, 17 Feb, 07:12 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5272) JobTracker does not log TIP start information after restart |
Tue, 17 Feb, 07:50 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5273) License header missing in TestJobInProgress.java |
Tue, 17 Feb, 08:12 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5272) JobTracker does not log TIP start information after restart |
Tue, 17 Feb, 09:57 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5276) Upon a lost tracker, the task's start time is reset to 0 |
Tue, 17 Feb, 11:52 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5276) Upon a lost tracker, the task's start time is reset to 0 |
Tue, 17 Feb, 12:08 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-4191) Add a testcase for jobhistory |
Tue, 17 Feb, 12:18 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5276) Upon a lost tracker, the task's start time is reset to 0 |
Tue, 17 Feb, 13:24 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5278) Finish time of a TIP is incorrectly logged to the jobhistory upon jobtracker restart |
Wed, 18 Feb, 11:03 |
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5278) Finish time of a TIP is incorrectly logged to the jobhistory upon jobtracker restart |
Wed, 18 Feb, 11:05 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5276) Upon a lost tracker, the task's start time is reset to 0 |
Wed, 18 Feb, 11:11 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5278) Finish time of a TIP is incorrectly logged to the jobhistory upon jobtracker restart |
Wed, 18 Feb, 13:21 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5282) Running tasks on lost trackers are incorrectly logging the attempt and task failures |
Thu, 19 Feb, 04:39 |
| Amar Kamat (JIRA) |
[jira] Assigned: (HADOOP-5282) Running tasks on lost trackers are incorrectly logging the attempt and task failures |
Thu, 19 Feb, 04:39 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5282) Running tasks on lost trackers are incorrectly logging the attempt and task failures |
Thu, 19 Feb, 05:17 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5247) NPEs in JobTracker and JobClient when mapred.jobtracker.completeuserjobs.maximum is set to zero. |
Thu, 19 Feb, 10:32 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5083) Optionally a separate daemon should serve JobHistory |
Thu, 19 Feb, 11:24 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5247) NPEs in JobTracker and JobClient when mapred.jobtracker.completeuserjobs.maximum is set to zero. |
Thu, 19 Feb, 11:28 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5282) Running tasks on lost trackers are incorrectly logging the attempt and task failures |
Thu, 19 Feb, 14:02 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5287) Killed task is logged as Failed upon a lost tracker |
Thu, 19 Feb, 14:04 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5287) Killed task is logged as Failed upon a lost tracker |
Thu, 19 Feb, 14:10 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5282) Running tasks on lost trackers are incorrectly logging the attempt and task failures |
Fri, 20 Feb, 06:11 |