[jira] [Updated] (HDFS-2568) Use a set to manage child sockets in XceiverServer

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2568: -- Assignee: Harsh J Status: Patch Available (was: Open) Use a set to manage child sockets in

[jira] [Updated] (HDFS-2568) Use a set to manage child sockets in XceiverServer

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2568: -- Status: Open (was: Patch Available) Some unnecessary changes got through. Use a set to

[jira] [Updated] (HDFS-2568) Use a set to manage child sockets in XceiverServer

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2568: -- Status: Patch Available (was: Open) Use a set to manage child sockets in XceiverServer

[jira] [Updated] (HDFS-2568) Use a set to manage child sockets in XceiverServer

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2568: -- Attachment: HDFS-2568.patch Proper patch. Existing tests should cover the change. We still use a synchronized

[jira] [Updated] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2454: -- Attachment: HDFS-2454.patch Move maxXceiverCount check to before starting the thread in dataXceiver

[jira] [Updated] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2454: -- Assignee: Harsh J (was: Uma Maheswara Rao G) Status: Patch Available (was: Open) Move

[jira] [Updated] (HDFS-442) dfsthroughput in test.jar throws NPE

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-442: - Fix Version/s: 0.24.0 Status: Patch Available (was: Open) dfsthroughput in test.jar throws NPE

[jira] [Updated] (HDFS-69) Improve dfsadmin command line help

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-69: Attachment: HDFS-69.patch Ravi and Jakob's comments are both addressed in this trunk docfix patch. No tests should

[jira] [Updated] (HDFS-557) 0.20 HDFS documentation for dfsadmin is using bin/hadoop instead of bin/hdfs

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-557: - Attachment: HDFS-557.patch Here are s/hadoop /hdfs /g updates for HDFS docs. All references I could manage to

[jira] [Updated] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2502: -- Attachment: HDFS-2502.patch hdfs-default.xml should include dfs.name.dir.restore

[jira] [Updated] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2502: -- Fix Version/s: 0.24.0 Assignee: Harsh J Status: Patch Available (was: Open)

[jira] [Updated] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2570: -- Hadoop Flags: Reviewed Add descriptions for dfs.*.https.address in hdfs-default.xml

[jira] [Updated] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2567: -- Attachment: HDFS-2567.patch Agreed Eli, was silly of me (I hesitated in using up the nn object upfront :))

[jira] [Updated] (HDFS-2572) Unnecessary double-check in DN#getHostName

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2572: -- Status: Patch Available (was: Open) Unnecessary double-check in DN#getHostName

[jira] [Updated] (HDFS-2572) Unnecessary double-check in DN#getHostName

2011-11-19 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2572: -- Attachment: HDFS-2572.patch Unnecessary double-check in DN#getHostName

[jira] [Updated] (HDFS-1445) Batch the calls in DataStorage to FileUtil.createHardLink(), so we call it once per directory instead of once per file

2011-11-15 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-1445: -- Fix Version/s: (was: 0.20.204.0) This isn't in 0.20.204. Not sure how that got into the Fix Version.

[jira] [Updated] (HDFS-1445) Batch the calls in DataStorage to FileUtil.createHardLink(), so we call it once per directory instead of once per file

2011-11-15 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-1445: -- Fix Version/s: 0.20.204.0 I was wrong. This one does seem to be present. Not present in CHANGES.txt though.

[jira] [Updated] (HDFS-2547) ReplicationTargetChooser has incorrect block placement comments

2011-11-11 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2547: -- Description: {code} /** The class is responsible for choosing the desired number of targets * for placing

[jira] [Updated] (HDFS-2547) ReplicationTargetChooser has incorrect block placement comments

2011-11-11 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2547: -- Attachment: HDFS-2547.patch New patch that changes comments and fixes a typo.

[jira] [Updated] (HDFS-2547) ReplicationTargetChooser has incorrect block placement comments

2011-11-11 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2547: -- Status: Patch Available (was: Reopened) ReplicationTargetChooser has incorrect block placement comments

[jira] [Updated] (HDFS-2547) Design doc is wrong about default block placement policy.

2011-11-10 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2547: -- Resolution: Invalid Status: Resolved (was: Patch Available) The ReplicationTargetChooser comments are

[jira] [Updated] (HDFS-2547) Design doc is wrong about default block placement policy.

2011-11-09 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2547: -- Status: Patch Available (was: Open) Design doc is wrong about default block placement policy.

[jira] [Updated] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

2011-11-05 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2541: -- Attachment: BSBugTest.java HDFS-2541.patch Patch and sample test attached.

[jira] [Updated] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

2011-11-05 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2541: -- Status: Patch Available (was: Open) Running build + test. For a sufficiently large value of

[jira] [Updated] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

2011-11-05 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2541: -- Attachment: (was: HDFS-2541.patch) For a sufficiently large value of blocks, the DN Scanner may

[jira] [Updated] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

2011-11-05 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2541: -- Attachment: HDFS-2541.patch Re-upping patch for proper buildbot submission. For a

[jira] [Updated] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

2011-11-05 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2541: -- Status: Open (was: Patch Available) For a sufficiently large value of blocks, the DN Scanner may request

[jira] [Updated] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

2011-11-05 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2541: -- Status: Patch Available (was: Open) For a sufficiently large value of blocks, the DN Scanner may request

[jira] [Updated] (HDFS-2349) DN should log a WARN, not an INFO when it detects a corruption during block transfer

2011-10-11 Thread Harsh J (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2349: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for

<    1   2