[jira] Created: (HADOOP-1076) Periodic checkpointing cannot resume if the secondary name-node fails.

Periodic checkpointing cannot resume if the secondary name-node fails. -- Key: HADOOP-1076 URL: https://issues.apache.org/jira/browse/HADOOP-1076 Project: Hadoop Issue Type:

[jira] Commented: (HADOOP-1075) Ensure that all test-cases using MiniDFSCluster & MiniMRCluster do not start the datanodes/tasktrackers before namenode/jobtracker due to port-rolling problems.

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

[jira] Commented: (HADOOP-1060) IndexOutOfBoundsException in JobInProgress.updateTaskStatus leads to hung jobs

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

[jira] Updated: (HADOOP-1075) Ensure that all test-cases using MiniDFSCluster & MiniMRCluster do not start the datanodes/tasktrackers before namenode/jobtracker due to port-rolling problems.

[ https://issues.apache.org/jira/browse/HADOOP-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated HADOOP-1075: -- Status: Patch Available (was: Open) > Ensure that all test-cases using MiniDFSCluster & MiniM

[jira] Updated: (HADOOP-1075) Ensure that all test-cases using MiniDFSCluster & MiniMRCluster do not start the datanodes/tasktrackers before namenode/jobtracker due to port-rolling problems.

[ https://issues.apache.org/jira/browse/HADOOP-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated HADOOP-1075: -- Attachment: HADOOP-1075_20070306_1.patch Straight-forward patch... > Ensure that all test-cas

[jira] Created: (HADOOP-1075) Ensure that all test-cases using MiniDFSCluster & MiniMRCluster do not start the datanodes/tasktrackers before namenode/jobtracker due to port-rolling problems.

Ensure that all test-cases using MiniDFSCluster & MiniMRCluster do not start the datanodes/tasktrackers before namenode/jobtracker due to port-rolling problems.

[jira] Created: (HADOOP-1074) fsck reports different number of files with differing dfs.data.dir directories

fsck reports different number of files with differing dfs.data.dir directories -- Key: HADOOP-1074 URL: https://issues.apache.org/jira/browse/HADOOP-1074 Project: Hadoop

[jira] Updated: (HADOOP-1060) IndexOutOfBoundsException in JobInProgress.updateTaskStatus leads to hung jobs

[ https://issues.apache.org/jira/browse/HADOOP-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated HADOOP-1060: -- Status: Open (was: Patch Available) Need to double check this patch; the 0.10.1 release works

[jira] Commented: (HADOOP-1073) DFS Scalability: high CPU usage in choosing replication targets and file open

[ https://issues.apache.org/jira/browse/HADOOP-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478640 ] Sameer Paranjpye commented on HADOOP-1073: -- A fat client makes it harder to provide back compatibility and

[jira] Updated: (HADOOP-1060) IndexOutOfBoundsException in JobInProgress.updateTaskStatus leads to hung jobs

[ https://issues.apache.org/jira/browse/HADOOP-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HADOOP-1060: -- Status: Patch Available (was: Open) +1 > IndexOutOfBoundsException in JobInProgress.updateTa

[jira] Created: (HADOOP-1073) DFS Scalability: high CPU usage in choosing replication targets and file open

DFS Scalability: high CPU usage in choosing replication targets and file open - Key: HADOOP-1073 URL: https://issues.apache.org/jira/browse/HADOOP-1073 Project: Hadoop

[jira] Commented: (HADOOP-1061) S3 listSubPaths bug

[ https://issues.apache.org/jira/browse/HADOOP-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478625 ] Mike Smith commented on HADOOP-1061: Tom, I checked the second patch and it works fine and detects the version

[jira] Created: (HADOOP-1072) VersionMismatch should be VersionMismatchException

VersionMismatch should be VersionMismatchException -- Key: HADOOP-1072 URL: https://issues.apache.org/jira/browse/HADOOP-1072 Project: Hadoop Issue Type: Improvement Components: ipc

[jira] Created: (HADOOP-1071) RPC$VersionMismatch exception is not fatal to JobTracker

RPC$VersionMismatch exception is not fatal to JobTracker Key: HADOOP-1071 URL: https://issues.apache.org/jira/browse/HADOOP-1071 Project: Hadoop Issue Type: Bug Components: m

[jira] Commented: (HADOOP-1031) Enhancements to Hadoop record I/O - Part 2

[ https://issues.apache.org/jira/browse/HADOOP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478623 ] Doug Cutting commented on HADOOP-1031: -- This sounds like a good direction. > Enhancements to Hadoop record I/O

[jira] Commented: (HADOOP-1069) Rename Hadoop record I/O to Jute

[ https://issues.apache.org/jira/browse/HADOOP-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478598 ] Sameer Paranjpye commented on HADOOP-1069: -- These are not bad names, IMO. I didn't have to walk down the li

[jira] Updated: (HADOOP-1067) Compile fails if Checkstyle jar is present in lib directory

[ https://issues.apache.org/jira/browse/HADOOP-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-1067: - Fix Version/s: (was: 0.13.0) 0.12.1 I'm moving this to 0.12.1, since it i

[jira] Commented: (HADOOP-1061) S3 listSubPaths bug

[ https://issues.apache.org/jira/browse/HADOOP-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478590 ] Tom White commented on HADOOP-1061: --- No this is not back-compatible. It's not actually that hard to make it back-

[jira] Updated: (HADOOP-1067) Compile fails if Checkstyle jar is present in lib directory

[ https://issues.apache.org/jira/browse/HADOOP-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom White updated HADOOP-1067: -- Resolution: Fixed Status: Resolved (was: Patch Available) I've just commited this with the su

[jira] Commented: (HADOOP-1061) S3 listSubPaths bug

[ https://issues.apache.org/jira/browse/HADOOP-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478586 ] Doug Cutting commented on HADOOP-1061: -- Should we check not just the FS version, but also the name and type? A

[jira] Updated: (HADOOP-1061) S3 listSubPaths bug

[ https://issues.apache.org/jira/browse/HADOOP-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom White updated HADOOP-1061: -- Attachment: hadoop-1061-v2.patch Patch for review. > S3 listSubPaths bug > --- > >

[jira] Commented: (HADOOP-1067) Compile fails if Checkstyle jar is present in lib directory

[ https://issues.apache.org/jira/browse/HADOOP-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478560 ] Doug Cutting commented on HADOOP-1067: -- +1 This looks fine to me. We might check for "checkstyle*.jar" so that

[jira] Commented: (HADOOP-1066) http://lucene.apache.org/hadoop/ front page is not user-friendly

[ https://issues.apache.org/jira/browse/HADOOP-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478555 ] Tom White commented on HADOOP-1066: --- I think Apache ActiveMQ (http://activemq.apache.org/) might be something to a

[jira] Commented: (HADOOP-1031) Enhancements to Hadoop record I/O - Part 2

[ https://issues.apache.org/jira/browse/HADOOP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478546 ] Milind Bhandarkar commented on HADOOP-1031: --- I would like to add another proposed change to record I/O her

Re: [jira] Commented: (HADOOP-1069) Rename Hadoop record I/O to Jute

> > Swing was originally a separate project that was grafted into the JVM and not > renamed, probably for back-compatibility. > FWIW I was in the Java group at Sun at the time. Swing was always intended to be a new windowing toolkit for the Java platform, offering a higher level of abstractio

[jira] Commented: (HADOOP-1069) Rename Hadoop record I/O to Jute

[ https://issues.apache.org/jira/browse/HADOOP-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478526 ] Doug Cutting commented on HADOOP-1069: -- > What about 'beans' and 'swing'? Beans is meant to be descriptive, vi

[jira] Commented: (HADOOP-1069) Rename Hadoop record I/O to Jute

[ https://issues.apache.org/jira/browse/HADOOP-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478516 ] Sameer Paranjpye commented on HADOOP-1069: -- What about 'beans' and 'swing'? > Rename Hadoop record I/O to

[jira] Commented: (HADOOP-1070) Number of racks and datanode double temporarily when upgrading from 0.10.1 to 0.11.2

[ https://issues.apache.org/jira/browse/HADOOP-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478510 ] Nigel Daley commented on HADOOP-1070: - More from the logs: Namenode Log After 1st Startup:

[jira] Commented: (HADOOP-1070) Number of racks and datanode double temporarily when upgrading from 0.10.1 to 0.11.2

[ https://issues.apache.org/jira/browse/HADOOP-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478512 ] Nigel Daley commented on HADOOP-1070: - My guess this is caused by some interaction between the rack aware patch,

[jira] Created: (HADOOP-1070) Number of racks and datanode double temporarily when upgrading from 0.10.1 to 0.11.2

Number of racks and datanode double temporarily when upgrading from 0.10.1 to 0.11.2 Key: HADOOP-1070 URL: https://issues.apache.org/jira/browse/HADOOP-1070 Project:

[jira] Updated: (HADOOP-1053) Make Record I/O functionally modular from the rest of Hadoop

[ https://issues.apache.org/jira/browse/HADOOP-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-1053: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed javadoc fixes. > M

[jira] Commented: (HADOOP-1069) Rename Hadoop record I/O to Jute

[ https://issues.apache.org/jira/browse/HADOOP-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478498 ] Doug Cutting commented on HADOOP-1069: -- -1 The general naming rule is that projects should have meaningless nam

[jira] Commented: (HADOOP-1066) http://lucene.apache.org/hadoop/ front page is not user-friendly

[ https://issues.apache.org/jira/browse/HADOOP-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478495 ] Doug Cutting commented on HADOOP-1066: -- +1 For a start, the "About" page should probably be merged into the to

[jira] Commented: (HADOOP-1065) DFS client warnings / info's should be centrally logged by name node

[ https://issues.apache.org/jira/browse/HADOOP-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478494 ] dhruba borthakur commented on HADOOP-1065: -- The namenode currently exposes a RPC called reportBadBlock() th

[jira] Created: (HADOOP-1069) Rename Hadoop record I/O to Jute

Rename Hadoop record I/O to Jute Key: HADOOP-1069 URL: https://issues.apache.org/jira/browse/HADOOP-1069 Project: Hadoop Issue Type: Improvement Components: record Affects Versions: 0.12.0

[jira] Updated: (HADOOP-1068) Improve error message for 0 datanode case

[ https://issues.apache.org/jira/browse/HADOOP-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HADOOP-1068: - Attachment: fewdatanodeswarning.patch The error message has been changed to the followin

[jira] Commented: (HADOOP-1067) Compile fails if Checkstyle jar is present in lib directory

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

[jira] Created: (HADOOP-1068) Improve error message for 0 datanode case

Improve error message for 0 datanode case - Key: HADOOP-1068 URL: https://issues.apache.org/jira/browse/HADOOP-1068 Project: Hadoop Issue Type: Improvement Components: dfs Affects Version

[jira] Updated: (HADOOP-1067) Compile fails if Checkstyle jar is present in lib directory

[ https://issues.apache.org/jira/browse/HADOOP-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom White updated HADOOP-1067: -- Fix Version/s: 0.13.0 Status: Patch Available (was: Open) > Compile fails if Checkstyle ja

[jira] Updated: (HADOOP-1067) Compile fails if Checkstyle jar is present in lib directory

[ https://issues.apache.org/jira/browse/HADOOP-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom White updated HADOOP-1067: -- Attachment: checkstyle.patch This patch looks for the checkstyle jar in "lib/excluded" and also exclud

[jira] Created: (HADOOP-1067) Compile fails if Checkstyle jar is present in lib directory

Compile fails if Checkstyle jar is present in lib directory --- Key: HADOOP-1067 URL: https://issues.apache.org/jira/browse/HADOOP-1067 Project: Hadoop Issue Type: Bug Compone

[jira] Commented: (HADOOP-1061) S3 listSubPaths bug

[ https://issues.apache.org/jira/browse/HADOOP-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478330 ] Tom White commented on HADOOP-1061: --- Yes, the patch should include * Fixing listObjects call * Removing URL enc