[jira] Updated: (HDFS-763) DataBlockScanner reporting of bad blocks is slightly misleading

[ https://issues.apache.org/jira/browse/HDFS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-763: -- Resolution: Fixed Fix Version/s: 0.22.0 Hadoop Flags: [Reviewed] Status: Re

[jira] Updated: (HDFS-756) libhdfs unit tests do not run

[ https://issues.apache.org/jira/browse/HDFS-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-756: -- Status: Open (was: Patch Available) Let's use the snapshot jar for now. > libhdfs unit tests do

[jira] Commented: (HDFS-760) "fs -put" fails if dfs.umask is set to 63

[ https://issues.apache.org/jira/browse/HDFS-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779270#action_12779270 ] Jakob Homan commented on HDFS-760: -- Some info: This is being caused by a problem in the conf

[jira] Commented: (HDFS-756) libhdfs unit tests do not run

[ https://issues.apache.org/jira/browse/HDFS-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779246#action_12779246 ] Eli Collins commented on HDFS-756: -- I'd prefer using the snapshot jar instead of duplicating

[jira] Commented: (HDFS-756) libhdfs unit tests do not run

[ https://issues.apache.org/jira/browse/HDFS-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779242#action_12779242 ] Eli Collins commented on HDFS-756: -- Hey Konstantin -- Thanks for the feedback. Using the sna

[jira] Updated: (HDFS-564) Adding pipeline test 17-35

[ https://issues.apache.org/jira/browse/HDFS-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Chansler updated HDFS-564: - Fix Version/s: 0.21.0 > Adding pipeline test 17-35 > -- > >

[jira] Updated: (HDFS-724) Pipeline close hangs if one of the datanode is not responsive.

[ https://issues.apache.org/jira/browse/HDFS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Chansler updated HDFS-724: - Fix Version/s: 0.21.0 > Pipeline close hangs if one of the datanode is not responsive. > --

[jira] Updated: (HDFS-566) INode.permissions should be marked as volatile to avoid synchronization problems

[ https://issues.apache.org/jira/browse/HDFS-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Chansler updated HDFS-566: - Priority: Blocker (was: Minor) Fix Version/s: 0.21.0 Issue Type: Bug (was: Improve

[jira] Updated: (HDFS-776) Fix exception handling in Balancer

[ https://issues.apache.org/jira/browse/HDFS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Chansler updated HDFS-776: - Priority: Blocker (was: Critical) > Fix exception handling in Balancer > -

[jira] Updated: (HDFS-564) Adding pipeline test 17-35

[ https://issues.apache.org/jira/browse/HDFS-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Chansler updated HDFS-564: - Priority: Blocker (was: Major) Affects Version/s: 0.21.0 > Adding pipeline test 17-35

[jira] Updated: (HDFS-760) "fs -put" fails if dfs.umask is set to 63

[ https://issues.apache.org/jira/browse/HDFS-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Chansler updated HDFS-760: - Priority: Blocker (was: Major) > "fs -put" fails if dfs.umask is set to 63 > -

[jira] Updated: (HDFS-724) Pipeline close hangs if one of the datanode is not responsive.

[ https://issues.apache.org/jira/browse/HDFS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Chansler updated HDFS-724: - Affects Version/s: 0.21.0 > Pipeline close hangs if one of the datanode is not responsive. > --

[jira] Updated: (HDFS-724) Pipeline close hangs if one of the datanode is not responsive.

[ https://issues.apache.org/jira/browse/HDFS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Chansler updated HDFS-724: - Priority: Blocker (was: Major) > Pipeline close hangs if one of the datanode is not responsive. >

[jira] Updated: (HDFS-101) DFS write pipeline : DFSClient sometimes does not detect second datanode failure

[ https://issues.apache.org/jira/browse/HDFS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Chansler updated HDFS-101: - Description: When the first datanode's write to second datanode fails or times out DFSClient end

[jira] Commented: (HDFS-756) libhdfs unit tests do not run

[ https://issues.apache.org/jira/browse/HDFS-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779239#action_12779239 ] Konstantin Boudnik commented on HDFS-756: - Slightly different modification of the pro

[jira] Commented: (HDFS-630) In DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating the next block.

[ https://issues.apache.org/jira/browse/HDFS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779229#action_12779229 ] Hadoop QA commented on HDFS-630: -1 overall. Here are the results of testing the latest atta

[jira] Updated: (HDFS-630) In DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating the next block.

[ https://issues.apache.org/jira/browse/HDFS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cosmin Lehene updated HDFS-630: --- Status: Patch Available (was: Open) Fix for 0.21 and trunk. > In DFSOutputStream.nextBlockOutputStre

[jira] Updated: (HDFS-630) In DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating the next block.

[ https://issues.apache.org/jira/browse/HDFS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HDFS-630: --- Status: Open (was: Patch Available) Cancelling so Cosmin can resubmit > In DFSOutputStream.nextBlockOutputStream(), t

[jira] Updated: (HDFS-630) In DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating the next block.

[ https://issues.apache.org/jira/browse/HDFS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cosmin Lehene updated HDFS-630: --- Attachment: 0001-Fix-HDFS-630-svn.patch fixed old method in NameNode.addBlock it returned addBlock(src,

[jira] Commented: (HDFS-326) Add a lifecycle interface for Hadoop components: namenodes, job clients, etc.

[ https://issues.apache.org/jira/browse/HDFS-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779187#action_12779187 ] Tom White commented on HDFS-326: bq. switch to Git to keep changes more isolated And make ma

[jira] Commented: (HDFS-764) Moving Access Token implementation from Common to HDFS

[ https://issues.apache.org/jira/browse/HDFS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779152#action_12779152 ] Hudson commented on HDFS-764: - Integrated in Hadoop-Hdfs-trunk-Commit #115 (See [http://hudson.z

[jira] Updated: (HDFS-764) Moving Access Token implementation from Common to HDFS

[ https://issues.apache.org/jira/browse/HDFS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj Das updated HDFS-764: - Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this. Thanks, Kan! > M

[jira] Updated: (HDFS-265) Revisit append

[ https://issues.apache.org/jira/browse/HDFS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HDFS-265: --- Affects Version/s: (was: Append Branch) Fix Version/s: (was: Append Branch) > Revisit a

[jira] Updated: (HDFS-265) Revisit append

[ https://issues.apache.org/jira/browse/HDFS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HDFS-265: --- Affects Version/s: 0.21.0 Fix Version/s: 0.21.0 > Revisit append > -- > >

[jira] Commented: (HDFS-758) Improve reporting of progress of decommissioning

[ https://issues.apache.org/jira/browse/HDFS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779120#action_12779120 ] Suresh Srinivas commented on HDFS-758: -- # Check for 80 char column size in the code # In

[jira] Commented: (HDFS-734) TestDatanodeBlockScanner times out in branch 0.20

[ https://issues.apache.org/jira/browse/HDFS-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779085#action_12779085 ] gary murry commented on HDFS-734: - This also looks to be timing out on trunk: http://hudson.

[jira] Commented: (HDFS-641) Move all of the benchmarks and tests that depend on mapreduce to mapreduce

[ https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779008#action_12779008 ] Lee Tucker commented on HDFS-641: - Circular dependencies are inherently evil, and fragile, an

[jira] Commented: (HDFS-641) Move all of the benchmarks and tests that depend on mapreduce to mapreduce

[ https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779005#action_12779005 ] Doug Cutting commented on HDFS-641: --- > Sharad/Hemant/Dhruba/Me all were either -1 or not +1

[jira] Commented: (HDFS-641) Move all of the benchmarks and tests that depend on mapreduce to mapreduce

[ https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778997#action_12778997 ] Owen O'Malley commented on HDFS-641: *Sigh* I apologize for not closing the loop on the c

[jira] Commented: (HDFS-326) Add a lifecycle interface for Hadoop components: namenodes, job clients, etc.

[ https://issues.apache.org/jira/browse/HDFS-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778992#action_12778992 ] Steve Loughran commented on HDFS-326: - Stu., I've not touched this code for a bit becau

[jira] Updated: (HDFS-776) Fix exception handling in Balancer

[ https://issues.apache.org/jira/browse/HDFS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HDFS-776: --- Component/s: Balancer Description: The Balancer's AccessKeyUpdater handles exceptions badly. In par

[jira] Created: (HDFS-776) Fix exception handling in Balancer

Fix exception handling in Balancer -- Key: HDFS-776 URL: https://issues.apache.org/jira/browse/HDFS-776 Project: Hadoop HDFS Issue Type: Bug Reporter: Owen O'Malley Priority: Critical

[jira] Updated: (HDFS-775) FSDataset calls getCapacity() twice -bug?

[ https://issues.apache.org/jira/browse/HDFS-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-775: Priority: Minor (was: Major) minor defect; its transient and nothing will actually break. > FSData

[jira] Commented: (HDFS-775) FSDataset calls getCapacity() twice -bug?

[ https://issues.apache.org/jira/browse/HDFS-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778828#action_12778828 ] Steve Loughran commented on HDFS-775: - Here's the code {code} long getCapacity() thr

[jira] Created: (HDFS-775) FSDataset calls getCapacity() twice -bug?

FSDataset calls getCapacity() twice -bug? - Key: HDFS-775 URL: https://issues.apache.org/jira/browse/HDFS-775 Project: Hadoop HDFS Issue Type: Bug Components: data-node Affects Versions:

[jira] Commented: (HDFS-641) Move all of the benchmarks and tests that depend on mapreduce to mapreduce

[ https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778773#action_12778773 ] Vinod K V commented on HDFS-641: It is unfortunate that we couldn't make any progress on the