| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Wed, 04 Mar, 11:59 |
| Suman Sehgal (JIRA) |
[jira] Created: (HADOOP-5393) hadoop-port-range parameter should be optional. |
Wed, 04 Mar, 13:11 |
| Suman Sehgal (JIRA) |
[jira] Commented: (HADOOP-2898) HOD should allow setting MapReduce UI ports within a port range |
Wed, 04 Mar, 13:15 |
| Amar Kamat (JIRA) |
[jira] Assigned: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Wed, 04 Mar, 13:35 |
| Amar Kamat (JIRA) |
[jira] Assigned: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 04 Mar, 13:35 |
| Amar Kamat (JIRA) |
[jira] Created: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 04 Mar, 13:35 |
| Hemanth Yamijala (JIRA) |
[jira] Created: (HADOOP-5395) When queue ACLs are enabled, the error message shown when a job is submitted to a non-existent queue is misleading |
Wed, 04 Mar, 14:05 |
|
[jira] Updated: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
|
| Hemanth Yamijala (JIRA) |
[jira] Updated: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Wed, 04 Mar, 14:07 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Thu, 05 Mar, 07:25 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Fri, 06 Mar, 07:45 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Fri, 06 Mar, 07:49 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Mon, 09 Mar, 13:08 |
| Amar Kamat (JIRA) |
[jira] Updated: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Tue, 10 Mar, 08:44 |
| Devaraj Das (JIRA) |
[jira] Updated: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Tue, 10 Mar, 11:58 |
| Devaraj Das (JIRA) |
[jira] Updated: (HADOOP-5392) JobTracker crashes during recovery if job files are garbled |
Tue, 10 Mar, 12:00 |
|
[jira] Commented: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
|
| Amar Kamat (JIRA) |
[jira] Commented: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 04 Mar, 14:51 |
| Devaraj Das (JIRA) |
[jira] Commented: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Sun, 08 Mar, 04:10 |
| Devaraj Das (JIRA) |
[jira] Commented: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Tue, 17 Mar, 12:30 |
| Devaraj Das (JIRA) |
[jira] Commented: (HADOOP-5394) JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts |
Wed, 25 Mar, 08:00 |
| Hemanth Yamijala (JIRA) |
[jira] Created: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker |
Wed, 04 Mar, 15:03 |
| Giridharan Kesavan (JIRA) |
[jira] Commented: (HADOOP-5331) KFS: Add support for append |
Wed, 04 Mar, 16:43 |
|
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
|
| Ben Maurer (JIRA) |
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
Wed, 04 Mar, 17:11 |
| Doug Cutting (JIRA) |
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
Wed, 04 Mar, 21:39 |
| Ben Maurer (JIRA) |
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
Fri, 06 Mar, 23:03 |
| Ben Maurer (JIRA) |
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
Sat, 07 Mar, 00:50 |
| Doug Cutting (JIRA) |
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
Mon, 09 Mar, 18:01 |
| Doug Cutting (JIRA) |
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
Mon, 09 Mar, 18:03 |
| Ben Maurer (JIRA) |
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
Mon, 09 Mar, 19:29 |
| Ben Maurer (JIRA) |
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
Mon, 09 Mar, 19:29 |
| Ben Maurer (JIRA) |
[jira] Updated: (HADOOP-5369) Small tweaks to reduce MapFile index size |
Mon, 09 Mar, 19:29 |
| Allen Wittenauer (JIRA) |
[jira] Issue Comment Edited: (HADOOP-4546) Minor fix in dfs to make hadoop work in AIX |
Wed, 04 Mar, 17:25 |
|
[jira] Updated: (HADOOP-1722) Make streaming to handle non-utf8 byte array |
|
| Klaas Bosteels (JIRA) |
[jira] Updated: (HADOOP-1722) Make streaming to handle non-utf8 byte array |
Wed, 04 Mar, 17:59 |
| zhuweimin (JIRA) |
[jira] Updated: (HADOOP-1722) Make streaming to handle non-utf8 byte array |
Fri, 06 Mar, 04:23 |
| Jim Kellerman (JIRA) |
[jira] Updated: (HADOOP-4379) In HDFS, sync() not yet guarantees data available to the new readers |
Wed, 04 Mar, 18:05 |
| Ari Rabkin (JIRA) |
[jira] Assigned: (HADOOP-5243) Fix TestAgentConfig |
Wed, 04 Mar, 18:31 |
|
[jira] Commented: (HADOOP-5384) DataNodeCluster should not create blocks with generationStamp == 1 |
|
| Hairong Kuang (JIRA) |
[jira] Commented: (HADOOP-5384) DataNodeCluster should not create blocks with generationStamp == 1 |
Wed, 04 Mar, 18:45 |
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Commented: (HADOOP-5384) DataNodeCluster should not create blocks with generationStamp == 1 |
Wed, 04 Mar, 21:43 |
| Hairong Kuang (JIRA) |
[jira] Commented: (HADOOP-5384) DataNodeCluster should not create blocks with generationStamp == 1 |
Wed, 04 Mar, 21:57 |
| Raghu Angadi (JIRA) |
[jira] Commented: (HADOOP-5384) DataNodeCluster should not create blocks with generationStamp == 1 |
Wed, 04 Mar, 22:23 |
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Commented: (HADOOP-5384) DataNodeCluster should not create blocks with generationStamp == 1 |
Wed, 04 Mar, 23:21 |
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Commented: (HADOOP-5384) DataNodeCluster should not create blocks with generationStamp == 1 |
Wed, 04 Mar, 23:47 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-5384) DataNodeCluster should not create blocks with generationStamp == 1 |
Fri, 13 Mar, 15:05 |
| Eric Yang (JIRA) |
[jira] Created: (HADOOP-5397) chukwa agent controller remove file does not work |
Wed, 04 Mar, 18:45 |
|
[jira] Updated: (HADOOP-5397) chukwa agent controller remove file does not work |
|
| Eric Yang (JIRA) |
[jira] Updated: (HADOOP-5397) chukwa agent controller remove file does not work |
Wed, 04 Mar, 19:03 |
| Eric Yang (JIRA) |
[jira] Updated: (HADOOP-5397) chukwa agent controller remove file does not work |
Wed, 04 Mar, 19:47 |
| Eric Yang (JIRA) |
[jira] Updated: (HADOOP-5397) chukwa agent controller remove file does not work |
Thu, 05 Mar, 18:03 |
| Eric Yang (JIRA) |
[jira] Updated: (HADOOP-5397) chukwa agent controller remove file does not work |
Thu, 05 Mar, 18:07 |
| Eric Yang (JIRA) |
[jira] Updated: (HADOOP-5397) chukwa agent controller remove file does not work |
Thu, 05 Mar, 18:09 |
| Eric Yang (JIRA) |
[jira] Updated: (HADOOP-5397) chukwa agent controller remove file does not work |
Thu, 05 Mar, 21:35 |
| Eric Yang (JIRA) |
[jira] Updated: (HADOOP-5397) chukwa agent controller remove file does not work |
Thu, 05 Mar, 21:35 |
| Eric Yang (JIRA) |
[jira] Updated: (HADOOP-5397) chukwa agent controller remove file does not work |
Mon, 09 Mar, 16:56 |
| Eric Yang (JIRA) |
[jira] Created: (HADOOP-5398) Support SQL macros in Chukwa Charting |
Wed, 04 Mar, 19:21 |
| Hairong Kuang (JIRA) |
[jira] Created: (HADOOP-5399) Simulated datanodes crashes NameNode |
Wed, 04 Mar, 19:23 |
|
[jira] Updated: (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] Updated: (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, 04 Mar, 19:35 |
| Bill Habermaas (JIRA) |
[jira] Updated: (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, 04 Mar, 19:43 |
| Bill Habermaas (JIRA) |
[jira] Updated: (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. |
Thu, 05 Mar, 01:39 |
| Bill Habermaas (JIRA) |
[jira] Updated: (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. |
Mon, 09 Mar, 13:10 |
| Raghu Angadi (JIRA) |
[jira] Updated: (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. |
Tue, 10 Mar, 00:12 |
| Raghu Angadi (JIRA) |
[jira] Updated: (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. |
Mon, 23 Mar, 23:13 |
| Raghu Angadi (JIRA) |
[jira] Updated: (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. |
Tue, 24 Mar, 18:46 |
| Raghu Angadi (JIRA) |
[jira] Updated: (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. |
Tue, 24 Mar, 18:50 |
| Raghu Angadi (JIRA) |
[jira] Updated: (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. |
Tue, 24 Mar, 18:52 |
| Raghu Angadi (JIRA) |
[jira] Updated: (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, 25 Mar, 21:01 |
| Hairong Kuang (JIRA) |
[jira] Commented: (HADOOP-5399) Simulated datanodes crashes NameNode |
Wed, 04 Mar, 19:41 |
| Hairong Kuang (JIRA) |
[jira] Updated: (HADOOP-5399) Simulated DataNode crashes NameNode |
Wed, 04 Mar, 19:45 |
|
[jira] Commented: (HADOOP-4343) Adding user and service-to-service authentication to Hadoop |
|
| Kan Zhang (JIRA) |
[jira] Commented: (HADOOP-4343) Adding user and service-to-service authentication to Hadoop |
Wed, 04 Mar, 19:53 |
| Kan Zhang (JIRA) |
[jira] Commented: (HADOOP-4343) Adding user and service-to-service authentication to Hadoop |
Wed, 04 Mar, 20:23 |
| Kan Zhang (JIRA) |
[jira] Commented: (HADOOP-4343) Adding user and service-to-service authentication to Hadoop |
Wed, 25 Mar, 17:35 |
|
[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. |
|
| Bo Shi (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, 04 Mar, 20:11 |
| 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, 04 Mar, 22:35 |
| Doug Cutting (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, 04 Mar, 22:53 |
| 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, 04 Mar, 23:11 |
| 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. |
Thu, 05 Mar, 00:01 |
| 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. |
Thu, 05 Mar, 01:51 |
| 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. |
Mon, 09 Mar, 20:13 |
| 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. |
Mon, 09 Mar, 22:53 |
| 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. |
Tue, 10 Mar, 00:18 |
| Steve Loughran (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. |
Tue, 10 Mar, 11:38 |
| Doug Cutting (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. |
Tue, 10 Mar, 21:08 |
| 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. |
Mon, 23 Mar, 22:27 |
| 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. |
Mon, 23 Mar, 23:07 |
| Hadoop QA (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. |
Tue, 24 Mar, 10:21 |
| 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. |
Tue, 24 Mar, 12:57 |
| Hadoop QA (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, 25 Mar, 02:45 |
| 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. |
Fri, 27 Mar, 13:26 |
| Rajiv Chittajallu (JIRA) |
[jira] Created: (HADOOP-5400) JT restart recovery: Exclude jobs which failed during SUBMIT_JOB (due to acl) |
Wed, 04 Mar, 20:29 |
| Rajiv Chittajallu (JIRA) |
[jira] Updated: (HADOOP-5400) JT restart recovery: Exclude jobs which failed during SUBMIT_JOB (due to acl) |
Wed, 04 Mar, 20:33 |
|
[jira] Commented: (HADOOP-5397) chukwa agent controller remove file does not work |
|
| Ari Rabkin (JIRA) |
[jira] Commented: (HADOOP-5397) chukwa agent controller remove file does not work |
Wed, 04 Mar, 20:33 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5397) chukwa agent controller remove file does not work |
Thu, 05 Mar, 07:25 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-5397) chukwa agent controller remove file does not work |
Mon, 09 Mar, 08:27 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-5397) chukwa agent controller remove file does not work |
Fri, 13 Mar, 15:05 |
|
[jira] Updated: (HADOOP-5036) chukwa agent controller remove file does not work |
|
| Jerome Boulon (JIRA) |
[jira] Updated: (HADOOP-5036) chukwa agent controller remove file does not work |
Wed, 04 Mar, 20:33 |
| Ari Rabkin (JIRA) |
[jira] Updated: (HADOOP-5036) chukwa agent controller remove file does not work |
Wed, 04 Mar, 20:35 |
| Ari Rabkin (JIRA) |
[jira] Resolved: (HADOOP-5007) can't hard-stop Chukwa adaptors |
Wed, 04 Mar, 20:43 |
| Ari Rabkin (JIRA) |
[jira] Created: (HADOOP-5401) chukwaAgent.agent.control.port is going away |
Wed, 04 Mar, 20:47 |
|
[jira] Updated: (HADOOP-5401) chukwaAgent.agent.control.port is going away |
|
| Ari Rabkin (JIRA) |
[jira] Updated: (HADOOP-5401) chukwaAgent.agent.control.port is going away |
Wed, 04 Mar, 20:53 |
| Ari Rabkin (JIRA) |
[jira] Updated: (HADOOP-5401) chukwaAgent.agent.control.port is going away |
Wed, 04 Mar, 20:59 |
| Ari Rabkin (JIRA) |
[jira] Updated: (HADOOP-5401) chukwaAgent.agent.control.port is going away |
Thu, 05 Mar, 20:47 |
| Ari Rabkin (JIRA) |
[jira] Assigned: (HADOOP-5401) chukwaAgent.agent.control.port is going away |
Wed, 04 Mar, 20:53 |
| Ari Rabkin (JIRA) |
[jira] Commented: (HADOOP-5385) Enhance process information collection |
Wed, 04 Mar, 21:09 |
|
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
|
| Hairong Kuang (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Wed, 04 Mar, 22:25 |
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Wed, 04 Mar, 23:35 |
| dhruba borthakur (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Thu, 05 Mar, 07:49 |
| dhruba borthakur (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Thu, 05 Mar, 23:51 |
| Hairong Kuang (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Fri, 06 Mar, 20:02 |
| dhruba borthakur (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Fri, 06 Mar, 23:56 |
| dhruba borthakur (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Fri, 06 Mar, 23:56 |
| Hadoop QA (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Tue, 10 Mar, 00:14 |
| dhruba borthakur (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Tue, 10 Mar, 00:49 |
| dhruba borthakur (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Wed, 11 Mar, 07:58 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-3998) Got an exception from ClientFinalizer when the JT is terminated |
Fri, 13 Mar, 15:05 |
|
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
|
| Mahadev konar (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Wed, 04 Mar, 22:49 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Fri, 06 Mar, 06:59 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Fri, 06 Mar, 09:57 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 16 Mar, 08:30 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Mon, 23 Mar, 13:17 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Thu, 26 Mar, 10:52 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Tue, 31 Mar, 05:55 |
| Sreekanth Ramakrishnan (JIRA) |
[jira] Updated: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job |
Tue, 31 Mar, 10:31 |
|
[jira] Updated: (HADOOP-4868) Split the hadoop script into 3 parts |
|
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Updated: (HADOOP-4868) Split the hadoop script into 3 parts |
Wed, 04 Mar, 23:03 |
| Sharad Agarwal (JIRA) |
[jira] Updated: (HADOOP-4868) Split the hadoop script into 3 parts |
Fri, 06 Mar, 12:07 |
| Sharad Agarwal (JIRA) |
[jira] Updated: (HADOOP-4868) Split the hadoop script into 3 parts |
Fri, 06 Mar, 12:09 |
|
[jira] Commented: (HADOOP-4868) Split the hadoop script into 3 parts |
|
| Tsz Wo (Nicholas), SZE (JIRA) |
[jira] Commented: (HADOOP-4868) Split the hadoop script into 3 parts |
Wed, 04 Mar, 23:11 |
| Hudson (JIRA) |
[jira] Commented: (HADOOP-4868) Split the hadoop script into 3 parts |
Fri, 13 Mar, 15:05 |
|
[jira] Commented: (HADOOP-5133) FSNameSystem#addStoredBlock does not handle inconsistent block length correctly |
|
| Konstantin Shvachko (JIRA) |
[jira] Commented: (HADOOP-5133) FSNameSystem#addStoredBlock does not handle inconsistent block length correctly |
Wed, 04 Mar, 23:33 |
| Hairong Kuang (JIRA) |
[jira] Commented: (HADOOP-5133) FSNameSystem#addStoredBlock does not handle inconsistent block length correctly |
Thu, 05 Mar, 23:13 |
| Konstantin Shvachko (JIRA) |
[jira] Commented: (HADOOP-5133) FSNameSystem#addStoredBlock does not handle inconsistent block length correctly |
Fri, 06 Mar, 00:25 |