[jira] Updated: (HADOOP-1002) setting io.sort.factor does not have effect?

[ https://issues.apache.org/jira/browse/HADOOP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Runping Qi updated HADOOP-1002: --- Component/s: mapred > setting io.sort.factor does not have effect? > ---

[jira] Created: (HADOOP-1005) Percentage of reducer progress reaches more than 100%, even though the tasks are still in sorting phase

Percentage of reducer progress reaches more than 100%, even though the tasks are still in sorting phase --- Key: HADOOP-1005 URL: https://issues.apache.org/jira/br

[jira] Commented: (HADOOP-1003) Proposal to batch commits to edits log.

[ https://issues.apache.org/jira/browse/HADOOP-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471589 ] Yoram Arnon commented on HADOOP-1003: - a train station algorithm comes to mind. collect all the requests (passen

[jira] Commented: (HADOOP-612) DFs copyFromLocal fails with NullPointerException for a single file

[ https://issues.apache.org/jira/browse/HADOOP-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471569 ] Marco Nicosia commented on HADOOP-612: -- Is it possible to close this bug? > DFs copyFromLocal fails with NullP

[jira] Created: (HADOOP-1004) dfs -getmerge should process its argments better

dfs -getmerge should process its argments better -- Key: HADOOP-1004 URL: https://issues.apache.org/jira/browse/HADOOP-1004 Project: Hadoop Issue Type: Bug Reporter: arkady borkov

[jira] Created: (HADOOP-1003) Proposal to batch commits to edits log.

Proposal to batch commits to edits log. --- Key: HADOOP-1003 URL: https://issues.apache.org/jira/browse/HADOOP-1003 Project: Hadoop Issue Type: Improvement Components: dfs Reporter: R

[jira] Created: (HADOOP-1002) setting io.sort.factor does not have effect?

setting io.sort.factor does not have effect? Key: HADOOP-1002 URL: https://issues.apache.org/jira/browse/HADOOP-1002 Project: Hadoop Issue Type: Bug Reporter: Runping Qi I have a m/r

[jira] Commented: (HADOOP-761) Unit tests should cleanup created files in /tmp. It causes tests to fail if more than one users run tests on same machine.

[ https://issues.apache.org/jira/browse/HADOOP-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471549 ] Nigel Daley commented on HADOOP-761: Streaming tests and libhdfs tests also use /tmp. > Unit tests should cleanu

[jira] Created: (HADOOP-1001) the output of the map is not type checked against the specified types

the output of the map is not type checked against the specified types - Key: HADOOP-1001 URL: https://issues.apache.org/jira/browse/HADOOP-1001 Project: Hadoop Issue Type: B

[jira] Commented: (HADOOP-977) The output from the user's task should be tagged and sent to the resepective console streams.

[ https://issues.apache.org/jira/browse/HADOOP-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471512 ] Owen O'Malley commented on HADOOP-977: -- +1 > The output from the user's task should be tagged and sent to the r

[jira] Commented: (HADOOP-882) S3FileSystem should retry if there is a communication problem with S3

[ https://issues.apache.org/jira/browse/HADOOP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471505 ] [EMAIL PROTECTED] commented on HADOOP-882: -- Nigel, I'm guessing the patch application failed because it does

[jira] Created: (HADOOP-1000) Loggers in the Task framework should not write the the Tasks stderr

Loggers in the Task framework should not write the the Tasks stderr --- Key: HADOOP-1000 URL: https://issues.apache.org/jira/browse/HADOOP-1000 Project: Hadoop Issue Type: Bug

[jira] Created: (HADOOP-999) DFS Client should create file when the user creates the file

DFS Client should create file when the user creates the file Key: HADOOP-999 URL: https://issues.apache.org/jira/browse/HADOOP-999 Project: Hadoop Issue Type: Bug Compone

[jira] Created: (HADOOP-998) The URL in TaskCompletionEvent should be the root URL for the taskTracker

The URL in TaskCompletionEvent should be the root URL for the taskTracker - Key: HADOOP-998 URL: https://issues.apache.org/jira/browse/HADOOP-998 Project: Hadoop Issue T

[jira] Commented: (HADOOP-882) S3FileSystem should retry if there is a communication problem with S3

[ https://issues.apache.org/jira/browse/HADOOP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471495 ] Hadoop QA commented on HADOOP-882: -- -1, because 3 attempts failed to build and test the latest attachment (http://i

[jira] Updated: (HADOOP-882) S3FileSystem should retry if there is a communication problem with S3

[ https://issues.apache.org/jira/browse/HADOOP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom White updated HADOOP-882: - Status: Patch Available (was: Open) > S3FileSystem should retry if there is a communication problem with

[jira] Commented: (HADOOP-882) S3FileSystem should retry if there is a communication problem with S3

[ https://issues.apache.org/jira/browse/HADOOP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471493 ] Tom White commented on HADOOP-882: -- +1 I have tested the patch successfully using Jets3tS3FileSystemTest and think

[jira] Created: (HADOOP-997) Implement S3 retry mechanism for failed block transfers

Implement S3 retry mechanism for failed block transfers --- Key: HADOOP-997 URL: https://issues.apache.org/jira/browse/HADOOP-997 Project: Hadoop Issue Type: Improvement Component

[jira] Commented: (HADOOP-943) fsck to show the filename of the corrupted file

[ https://issues.apache.org/jira/browse/HADOOP-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471488 ] Koji Noguchi commented on HADOOP-943: - It'll be nice if this can also print ouf the info(file/block) for under-

[jira] Commented: (HADOOP-803) Reducing memory consumption on Namenode : Part 1

[ https://issues.apache.org/jira/browse/HADOOP-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471471 ] Raghu Angadi commented on HADOOP-803: - TreeMap allows us to get the object that was inserted into the map. With

[jira] Commented: (HADOOP-803) Reducing memory consumption on Namenode : Part 1

[ https://issues.apache.org/jira/browse/HADOOP-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471467 ] Hairong Kuang commented on HADOOP-803: -- In the patch the type of the field "blocks" in DatanodeDescriptor is cha

[jira] Updated: (HADOOP-996) fsck -files -blocks -locations is a little slow

[ https://issues.apache.org/jira/browse/HADOOP-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Noguchi updated HADOOP-996: Component/s: dfs > fsck -files -blocks -locations is a little slow > --

[jira] Created: (HADOOP-996) fsck -files -blocks -locations is a little slow

fsck -files -blocks -locations is a little slow --- Key: HADOOP-996 URL: https://issues.apache.org/jira/browse/HADOOP-996 Project: Hadoop Issue Type: Improvement Reporter: Koji Noguchi

[jira] Created: (HADOOP-995) DataNode started with illegal startup options should print usage and stop

DataNode started with illegal startup options should print usage and stop - Key: HADOOP-995 URL: https://issues.apache.org/jira/browse/HADOOP-995 Project: Hadoop Issue T

[jira] Assigned: (HADOOP-994) DFS Scalability : a BlockReport that returns large number of blocks-to-be-deleted cause datanode to lost connectivity to namenode

[ https://issues.apache.org/jira/browse/HADOOP-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur reassigned HADOOP-994: --- Assignee: dhruba borthakur > DFS Scalability : a BlockReport that returns large numbe

[jira] Created: (HADOOP-994) DFS Scalability : a BlockReport that returns large number of blocks-to-be-deleted cause datanode to lost connectivity to namenode

DFS Scalability : a BlockReport that returns large number of blocks-to-be-deleted cause datanode to lost connectivity to namenode - Key: HADOOP-994

[jira] Commented: (HADOOP-993) Namenode does not need to store any data node info persistently.

[ https://issues.apache.org/jira/browse/HADOOP-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471443 ] Raghu Angadi commented on HADOOP-993: - I should have specified that this was mainly a place holder. Details are

[jira] Updated: (HADOOP-654) jobs fail with some hardware/system failures on a small number of nodes

[ https://issues.apache.org/jira/browse/HADOOP-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated HADOOP-654: - Attachment: HADOOP-654_20070209_2.patch Here is a complete patch with necessary enhancements and

[jira] Commented: (HADOOP-993) Namenode does not need to store any data node info persistently.

[ https://issues.apache.org/jira/browse/HADOOP-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471427 ] Konstantin Shvachko commented on HADOOP-993: What does datanode to storageID map mean? Currently namenode

[jira] Created: (HADOOP-993) Namenode does not need to store any data node info persistently.

Namenode does not need to store any data node info persistently. Key: HADOOP-993 URL: https://issues.apache.org/jira/browse/HADOOP-993 Project: Hadoop Issue Type: Improvement

[jira] Updated: (HADOOP-977) The output from the user's task should be tagged and sent to the resepective console streams.

[ https://issues.apache.org/jira/browse/HADOOP-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated HADOOP-977: - Attachment: HADOOP-977_20070208_2.patch Update patch since HADOOP-975 got in... > The output fro

[jira] Resolved: (HADOOP-826) job tracker WI doesnt display shuffle finish time correctly.

[ https://issues.apache.org/jira/browse/HADOOP-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Dahiya resolved HADOOP-826. -- Resolution: Duplicate > job tracker WI doesnt display shuffle finish time correctly. >

[jira] Commented: (HADOOP-878) reducer NONE does not work with multiple maps

[ https://issues.apache.org/jira/browse/HADOOP-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471251 ] Sanjay Dahiya commented on HADOOP-878: -- This seems to be working for multiple maps after recent patches HADOOP-