[jira] [Updated] (HDFS-5901) NameNode new UI doesn't support IE8 and IE9 on windows 7

[ https://issues.apache.org/jira/browse/HDFS-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5901: Attachment: HDFS-5901.patch Attaching the patch. Please review NameNode new UI doesn't support IE8 and IE9 on

[jira] [Updated] (HDFS-5901) NameNode new UI doesn't support IE8 and IE9 on windows 7

[ https://issues.apache.org/jira/browse/HDFS-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5901: Status: Patch Available (was: Open) NameNode new UI doesn't support IE8 and IE9 on windows 7

[jira] [Commented] (HDFS-5901) NameNode new UI doesn't support IE8 and IE9 on windows 7

[ https://issues.apache.org/jira/browse/HDFS-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894325#comment-13894325 ] Vinay commented on HDFS-5901: - Yes [~wheat9], That works. Moving {{DOCTYPE}} before apache

[jira] [Updated] (HDFS-5901) NameNode new UI doesn't support IE8 and IE9 on windows 7

[ https://issues.apache.org/jira/browse/HDFS-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5901: Attachment: HDFS-5901.patch Updated the patch as per [~wheat9] suggestion NameNode new UI doesn't support IE8 and

[jira] [Updated] (HDFS-5185) DN fails to startup if one of the data dir is full

[ https://issues.apache.org/jira/browse/HDFS-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5185: Attachment: HDFS-5185.patch Adding a patch to check for disk failures before adding block pools to storage DN

[jira] [Updated] (HDFS-5185) DN fails to startup if one of the data dir is full

[ https://issues.apache.org/jira/browse/HDFS-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5185: Status: Patch Available (was: Open) DN fails to startup if one of the data dir is full

[jira] [Commented] (HDFS-5185) DN fails to startup if one of the data dir is full

[ https://issues.apache.org/jira/browse/HDFS-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894453#comment-13894453 ] Vinay commented on HDFS-5185: - Even after patch behaviour will be same by default unless

[jira] [Created] (HDFS-5903) FSVolumeList#initializeReplicaMaps(..) not doing anything, it can be removed

Vinay created HDFS-5903: --- Summary: FSVolumeList#initializeReplicaMaps(..) not doing anything, it can be removed Key: HDFS-5903 URL: https://issues.apache.org/jira/browse/HDFS-5903 Project: Hadoop HDFS

[jira] [Updated] (HDFS-5903) FSVolumeList#initializeReplicaMaps(..) not doing anything, it can be removed

[ https://issues.apache.org/jira/browse/HDFS-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5903: Attachment: HDFS-5903.patch Attaching a patch Please review FSVolumeList#initializeReplicaMaps(..) not doing

[jira] [Updated] (HDFS-5903) FSVolumeList#initializeReplicaMaps(..) not doing anything, it can be removed

[ https://issues.apache.org/jira/browse/HDFS-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5903: Status: Patch Available (was: Open) FSVolumeList#initializeReplicaMaps(..) not doing anything, it can be removed

[jira] [Updated] (HDFS-5903) FSVolumeList#initializeReplicaMaps(..) not doing anything, it can be removed

[ https://issues.apache.org/jira/browse/HDFS-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5903: Attachment: HDFS-5903.patch Attaching same patch to trigger jenkins again. FSVolumeList#initializeReplicaMaps(..)

[jira] [Commented] (HDFS-5903) FSVolumeList#initializeReplicaMaps(..) not doing anything, it can be removed

[ https://issues.apache.org/jira/browse/HDFS-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894559#comment-13894559 ] Vinay commented on HDFS-5903: - {noformat}# # There is insufficient memory for the Java Runtime

[jira] [Commented] (HDFS-3405) Checkpointing should use HTTP POST or PUT instead of GET-GET to send merged fsimages

[ https://issues.apache.org/jira/browse/HDFS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895377#comment-13895377 ] Vinay commented on HDFS-3405: - Bq. Popping up one level, I wonder, since we're uploading one

[jira] [Updated] (HDFS-5901) NameNode new UI doesn't support IE8 and IE9 on windows 7

[ https://issues.apache.org/jira/browse/HDFS-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5901: Attachment: HDFS-5901.patch Updated the patch. Removed redundant meta tag NameNode new UI doesn't support IE8 and

[jira] [Commented] (HDFS-3405) Checkpointing should use HTTP POST or PUT instead of GET-GET to send merged fsimages

[ https://issues.apache.org/jira/browse/HDFS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895398#comment-13895398 ] Vinay commented on HDFS-3405: - I found this RFC [link|http://tools.ietf.org/html/rfc1867]

[jira] [Updated] (HDFS-3405) Checkpointing should use HTTP POST or PUT instead of GET-GET to send merged fsimages

[ https://issues.apache.org/jira/browse/HDFS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-3405: Attachment: HDFS-3405.patch Attaching a patch fixing test failures. Missed one line during rebase ;)

[jira] [Commented] (HDFS-3405) Checkpointing should use HTTP POST or PUT instead of GET-GET to send merged fsimages

[ https://issues.apache.org/jira/browse/HDFS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893635#comment-13893635 ] Vinay commented on HDFS-3405: - Test failed with below exception {noformat}Exception in thread

[jira] [Commented] (HDFS-3405) Checkpointing should use HTTP POST or PUT instead of GET-GET to send merged fsimages

[ https://issues.apache.org/jira/browse/HDFS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893799#comment-13893799 ] Vinay commented on HDFS-3405: - If commos fileupload not used then parsing and encoding of

[jira] [Commented] (HDFS-3405) Checkpointing should use HTTP POST or PUT instead of GET-GET to send merged fsimages

[ https://issues.apache.org/jira/browse/HDFS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894183#comment-13894183 ] Vinay commented on HDFS-3405: - Thanks [~wheat9] for explaining your concern. Actually,

[jira] [Created] (HDFS-5901) NameNode new UI doesn't support IE8 and IE9 on windows 7

Vinay created HDFS-5901: --- Summary: NameNode new UI doesn't support IE8 and IE9 on windows 7 Key: HDFS-5901 URL: https://issues.apache.org/jira/browse/HDFS-5901 Project: Hadoop HDFS Issue Type: Bug

[jira] [Created] (HDFS-5890) Avoid NPE in Datanode heartbeat

Vinay created HDFS-5890: --- Summary: Avoid NPE in Datanode heartbeat Key: HDFS-5890 URL: https://issues.apache.org/jira/browse/HDFS-5890 Project: Hadoop HDFS Issue Type: Sub-task Components:

[jira] [Updated] (HDFS-5890) Avoid NPE in Datanode heartbeat

[ https://issues.apache.org/jira/browse/HDFS-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5890: Attachment: HDFS-5890.patch Attaching the patch 1. Avoids NPE 2. Checks for valid RollingUpgradeStatus in

[jira] [Commented] (HDFS-5890) Avoid NPE in Datanode heartbeat

[ https://issues.apache.org/jira/browse/HDFS-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892929#comment-13892929 ] Vinay commented on HDFS-5890: - Thank you Brandon Avoid NPE in Datanode heartbeat

[jira] [Commented] (HDFS-5878) Trunk windows build broken after HDFS-5746

[ https://issues.apache.org/jira/browse/HDFS-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893025#comment-13893025 ] Vinay commented on HDFS-5878: - bq. Vinay, thanks for picking this up. HDFS-5746 added

[jira] [Commented] (HDFS-5889) When rolling upgrade is in progress, standby NN should create checkpoint for downgrade.

[ https://issues.apache.org/jira/browse/HDFS-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893033#comment-13893033 ] Vinay commented on HDFS-5889: - Hi Nicholas, How you are planning to keep these checkpointed

[jira] [Commented] (HDFS-5869) When rolling upgrade is in progress, NN should only create checkpoint right before the upgrade marker

[ https://issues.apache.org/jira/browse/HDFS-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893036#comment-13893036 ] Vinay commented on HDFS-5869: - bq. Once we have HDFS-5889, we do not need to disable the

[jira] [Resolved] (HDFS-5890) Avoid NPE in Datanode heartbeat

[ https://issues.apache.org/jira/browse/HDFS-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay resolved HDFS-5890. - Resolution: Fixed Fix Version/s: HDFS-5535 (Rolling upgrades) Hadoop Flags: Reviewed Avoid NPE in

[jira] [Updated] (HDFS-3405) Checkpointing should use HTTP POST or PUT instead of GET-GET to send merged fsimages

[ https://issues.apache.org/jira/browse/HDFS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-3405: Attachment: HDFS-3405.patch Attaching the rabased patch. Please review. Checkpointing should use HTTP POST or

[jira] [Assigned] (HDFS-5185) DN fails to startup if one of the data dir is full

[ https://issues.apache.org/jira/browse/HDFS-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay reassigned HDFS-5185: --- Assignee: Vinay DN fails to startup if one of the data dir is full

[jira] [Commented] (HDFS-5177) blocksScheduled count should be decremented for abandoned blocks

[ https://issues.apache.org/jira/browse/HDFS-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890869#comment-13890869 ] Vinay commented on HDFS-5177: - Hi all, Can someone please take a look at the patch. Thanks in

[jira] [Commented] (HDFS-5669) Storage#tryLock() should check for null before logging successfull message

[ https://issues.apache.org/jira/browse/HDFS-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890875#comment-13890875 ] Vinay commented on HDFS-5669: - Please someone take a look at simple patch. Thanks

[jira] [Commented] (HDFS-5503) Datanode#checkDiskError also should check for ClosedChannelException

[ https://issues.apache.org/jira/browse/HDFS-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890879#comment-13890879 ] Vinay commented on HDFS-5503: - Hi All, Please someone take a look at simple patch. Thanks in

[jira] [Commented] (HDFS-5869) When rolling upgrade is in progress, NN should only create checkpoint right before the upgrade marker

[ https://issues.apache.org/jira/browse/HDFS-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891808#comment-13891808 ] Vinay commented on HDFS-5869: - Patch looks good nicholas. I think it will be better to roll

[jira] [Commented] (HDFS-5869) When rolling upgrade is in progress, NN should only create checkpoint right before the upgrade marker

[ https://issues.apache.org/jira/browse/HDFS-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891821#comment-13891821 ] Vinay commented on HDFS-5869: - Oops. I had forgot that. Thanks for the update. When rolling

[jira] [Commented] (HDFS-5869) When rolling upgrade is in progress, NN should only create checkpoint right before the upgrade marker

[ https://issues.apache.org/jira/browse/HDFS-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891824#comment-13891824 ] Vinay commented on HDFS-5869: - One more thing.. {code}} else if (rollingUpgradeOpt ==

[jira] [Commented] (HDFS-5869) When rolling upgrade is in progress, NN should only create checkpoint right before the upgrade marker

[ https://issues.apache.org/jira/browse/HDFS-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891837#comment-13891837 ] Vinay commented on HDFS-5869: - Got it. saveNamespace() while loading OP_UPGRADE_MARKER will not

[jira] [Commented] (HDFS-5869) When rolling upgrade is in progress, NN should only create checkpoint right before the upgrade marker

[ https://issues.apache.org/jira/browse/HDFS-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891854#comment-13891854 ] Vinay commented on HDFS-5869: - startCheckpoint() will be used only with BackupNode. As Jing

[jira] [Commented] (HDFS-5874) Should not compare DataNode current layout version with that of NameNode in DataStrorage

[ https://issues.apache.org/jira/browse/HDFS-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890376#comment-13890376 ] Vinay commented on HDFS-5874: - Thanks for filing this jira Brandon. Should not compare

[jira] [Created] (HDFS-5878) Trunk windows build broken after HDFS-5746

Vinay created HDFS-5878: --- Summary: Trunk windows build broken after HDFS-5746 Key: HDFS-5878 URL: https://issues.apache.org/jira/browse/HDFS-5878 Project: Hadoop HDFS Issue Type: Bug

[jira] [Updated] (HDFS-5878) Trunk windows build broken after HDFS-5746

[ https://issues.apache.org/jira/browse/HDFS-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5878: Attachment: HDFS-5878.patch This seems to fix the issue. Please check Trunk windows build broken after HDFS-5746

[jira] [Commented] (HDFS-5878) Trunk windows build broken after HDFS-5746

[ https://issues.apache.org/jira/browse/HDFS-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890460#comment-13890460 ] Vinay commented on HDFS-5878: - Build fails with following error

[jira] [Commented] (HDFS-5848) Add rolling upgrade infomation to heartbeat response

[ https://issues.apache.org/jira/browse/HDFS-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887562#comment-13887562 ] Vinay commented on HDFS-5848: - Changes looks good. +1 Add rolling upgrade infomation to

[jira] [Created] (HDFS-5861) Add CLI test for Ls output for extended ACL marker

Vinay created HDFS-5861: --- Summary: Add CLI test for Ls output for extended ACL marker Key: HDFS-5861 URL: https://issues.apache.org/jira/browse/HDFS-5861 Project: Hadoop HDFS Issue Type: Sub-task

[jira] [Updated] (HDFS-5861) Add CLI test for Ls output for extended ACL marker

[ https://issues.apache.org/jira/browse/HDFS-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5861: Attachment: HDFS-5861.patch Add CLI test for Ls output for extended ACL marker

[jira] [Commented] (HDFS-5861) Add CLI test for Ls output for extended ACL marker

[ https://issues.apache.org/jira/browse/HDFS-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13888461#comment-13888461 ] Vinay commented on HDFS-5861: - Hi [~cnauroth] , Could you take a look at added test. Thanks.

[jira] [Created] (HDFS-5855) Reading edits should not stop at UpgradeMarker for normal restart of the namenode

Vinay created HDFS-5855: --- Summary: Reading edits should not stop at UpgradeMarker for normal restart of the namenode Key: HDFS-5855 URL: https://issues.apache.org/jira/browse/HDFS-5855 Project: Hadoop HDFS

[jira] [Commented] (HDFS-5855) Reading edits should not stop at UpgradeMarker for normal restart of the namenode

[ https://issues.apache.org/jira/browse/HDFS-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886704#comment-13886704 ] Vinay commented on HDFS-5855: - Thanks Nicholas. That could actually solve the issue. My bad. I

[jira] [Resolved] (HDFS-5855) Reading edits should not stop at UpgradeMarker for normal restart of the namenode

[ https://issues.apache.org/jira/browse/HDFS-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay resolved HDFS-5855. - Resolution: Duplicate Assignee: Vinay Reading edits should not stop at UpgradeMarker for normal restart of

[jira] [Commented] (HDFS-5754) Split LayoutVerion into NamenodeLayoutVersion and DatanodeLayoutVersion

[ https://issues.apache.org/jira/browse/HDFS-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887540#comment-13887540 ] Vinay commented on HDFS-5754: - First of all, sorry for coming in late ( that too after commit

[jira] [Work started] (HDFS-5702) FsShell Cli: Add XML based End-to-End test for getfacl and setfacl commands

[ https://issues.apache.org/jira/browse/HDFS-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-5702 started by Vinay. FsShell Cli: Add XML based End-to-End test for getfacl and setfacl commands

[jira] [Updated] (HDFS-5702) FsShell Cli: Add XML based End-to-End test for getfacl and setfacl commands

[ https://issues.apache.org/jira/browse/HDFS-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5702: Attachment: HDFS-5702.patch Added mentioned 4 tests. Please review. I couldn't avoid the long line in expected

[jira] [Commented] (HDFS-5585) Provide admin commands for data node upgrade

[ https://issues.apache.org/jira/browse/HDFS-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885590#comment-13885590 ] Vinay commented on HDFS-5585: - changes looks good kihwal. some minor suggestions you might

[jira] [Commented] (HDFS-5586) Add quick-restart option for datanode

[ https://issues.apache.org/jira/browse/HDFS-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885593#comment-13885593 ] Vinay commented on HDFS-5586: - I think this is being covered in HDFS-5585. Can we make it

[jira] [Resolved] (HDFS-5827) Children are not inheriting parent's default ACLs

[ https://issues.apache.org/jira/browse/HDFS-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay resolved HDFS-5827. - Resolution: Duplicate This will be implemented in HDFS-5616 And tests are already added as part of HDFS-5702. So

[jira] [Updated] (HDFS-5832) Deadlock found in NN between SafeMode#canLeave and DatanodeManager#handleHeartbeat

[ https://issues.apache.org/jira/browse/HDFS-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5832: Summary: Deadlock found in NN between SafeMode#canLeave and DatanodeManager#handleHeartbeat (was: Deadeadlock

[jira] [Commented] (HDFS-5832) Deadlock found in NN between SafeMode#canLeave and DatanodeManager#handleHeartbeat

[ https://issues.apache.org/jira/browse/HDFS-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13882189#comment-13882189 ] Vinay commented on HDFS-5832: - As mentioned in HDFS-5132, Moving SafemodeMonitor#run() checks

[jira] [Created] (HDFS-5827) Children are not inheriting parent's default ACLs

Vinay created HDFS-5827: --- Summary: Children are not inheriting parent's default ACLs Key: HDFS-5827 URL: https://issues.apache.org/jira/browse/HDFS-5827 Project: Hadoop HDFS Issue Type: Bug

[jira] [Commented] (HDFS-5827) Children are not inheriting parent's default ACLs

[ https://issues.apache.org/jira/browse/HDFS-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13880940#comment-13880940 ] Vinay commented on HDFS-5827: - Following is the ACLs on parent and child in HDFS {noformat}#

[jira] [Updated] (HDFS-5827) Children are not inheriting parent's default ACLs

[ https://issues.apache.org/jira/browse/HDFS-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5827: Description: Children are not inheriting the parent's default ACLs on creation. was: Children are not

[jira] [Commented] (HDFS-5827) Children are not inheriting parent's default ACLs

[ https://issues.apache.org/jira/browse/HDFS-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13880942#comment-13880942 ] Vinay commented on HDFS-5827: - Hi [~cnauroth], Could you take a look at this. This I found

[jira] [Updated] (HDFS-5702) FsShell Cli: Add XML based End-to-End test for getfacl and setfacl commands

[ https://issues.apache.org/jira/browse/HDFS-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5702: Attachment: HDFS-5702.patch Attaching the patch with some of the initial tests. Please review Among added tests

[jira] [Commented] (HDFS-5723) Append failed FINALIZED replica should not be accepted as valid when that block is underconstruction

[ https://issues.apache.org/jira/browse/HDFS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13880721#comment-13880721 ] Vinay commented on HDFS-5723: - bq. Hi Vinay, one question about the patch: so this inconsistent

[jira] [Updated] (HDFS-5728) [Diskfull] Block recovery will fail if the metafile not having crc for all chunks of the block

[ https://issues.apache.org/jira/browse/HDFS-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5728: Attachment: HDFS-5728.patch Thanks Kihwal for taking a look. Attaching a patch by removing unnecessary lines as you

[jira] [Commented] (HDFS-5728) [Diskfull] Block recovery will fail if the metafile not having crc for all chunks of the block

[ https://issues.apache.org/jira/browse/HDFS-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13876178#comment-13876178 ] Vinay commented on HDFS-5728: - bq. Logically we already truncated in memory by having the

[jira] [Updated] (HDFS-5728) [Diskfull] Block recovery will fail if the metafile not having crc for all chunks of the block

[ https://issues.apache.org/jira/browse/HDFS-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5728: Attachment: HDFS-5728.patch Attaching the updated patch as per Uma's comment Please review [Diskfull] Block

[jira] [Commented] (HDFS-5745) Unnecessary disk check triggered when socket operation has problem.

[ https://issues.apache.org/jira/browse/HDFS-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866443#comment-13866443 ] Vinay commented on HDFS-5745: - HDFS-5503 also look similar, but with ClosedChannelException

[jira] [Commented] (HDFS-5728) [Diskfull] Block recovery will fail if the metafile not having crc for all chunks of the block

[ https://issues.apache.org/jira/browse/HDFS-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867487#comment-13867487 ] Vinay commented on HDFS-5728: - bq. Is this case happened only if we restart DN where crc has

[jira] [Updated] (HDFS-5723) Append failed FINALIZED replica should not be accepted as valid when that block is underconstruction

[ https://issues.apache.org/jira/browse/HDFS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5723: Assignee: Vinay Status: Patch Available (was: Open) Append failed FINALIZED replica should not be accepted

[jira] [Updated] (HDFS-5723) Append failed FINALIZED replica should not be accepted as valid when that block is underconstruction

[ https://issues.apache.org/jira/browse/HDFS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5723: Attachment: HDFS-5723.patch Attached the patch, Please review Append failed FINALIZED replica should not be

[jira] [Commented] (HDFS-5535) Umbrella jira for improved HDFS rolling upgrades

[ https://issues.apache.org/jira/browse/HDFS-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866350#comment-13866350 ] Vinay commented on HDFS-5535: - Very good work. From the doc what I can understand is,

[jira] [Created] (HDFS-5728) [Diskfull] Block recovery will fail if the metafile not having crc for all chunks of the block

Vinay created HDFS-5728: --- Summary: [Diskfull] Block recovery will fail if the metafile not having crc for all chunks of the block Key: HDFS-5728 URL: https://issues.apache.org/jira/browse/HDFS-5728 Project:

[jira] [Commented] (HDFS-5728) [Diskfull] Block recovery will fail if the metafile not having crc for all chunks of the block

[ https://issues.apache.org/jira/browse/HDFS-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865059#comment-13865059 ] Vinay commented on HDFS-5728: - 2013-12-28 13:22:30,467 WARN

[jira] [Updated] (HDFS-5728) [Diskfull] Block recovery will fail if the metafile not having crc for all chunks of the block

[ https://issues.apache.org/jira/browse/HDFS-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5728: Status: Patch Available (was: Open) [Diskfull] Block recovery will fail if the metafile not having crc for all

[jira] [Updated] (HDFS-5728) [Diskfull] Block recovery will fail if the metafile not having crc for all chunks of the block

[ https://issues.apache.org/jira/browse/HDFS-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5728: Attachment: HDFS-5728.patch Attached the patch, please review [Diskfull] Block recovery will fail if the metafile

[jira] [Created] (HDFS-5723) Append failed FINALIZED replica should not be accepted as valid when that block is underconstruction

Vinay created HDFS-5723: --- Summary: Append failed FINALIZED replica should not be accepted as valid when that block is underconstruction Key: HDFS-5723 URL: https://issues.apache.org/jira/browse/HDFS-5723

[jira] [Commented] (HDFS-5723) Append failed FINALIZED replica should not be accepted as valid when that block is underconstruction

[ https://issues.apache.org/jira/browse/HDFS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863898#comment-13863898 ] Vinay commented on HDFS-5723: - {noformat}2014-01-07 09:47:22,878 ERROR

[jira] [Updated] (HDFS-5723) Append failed FINALIZED replica should not be accepted as valid when that block is underconstruction

[ https://issues.apache.org/jira/browse/HDFS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5723: Description: Scenario: 1. 3 node cluster with dfs.client.block.write.replace-datanode-on-failure.enable set to

[jira] [Created] (HDFS-5702) FsShell Cli: Add XML based End-to-End test for getfacl and setfacl commands

Vinay created HDFS-5702: --- Summary: FsShell Cli: Add XML based End-to-End test for getfacl and setfacl commands Key: HDFS-5702 URL: https://issues.apache.org/jira/browse/HDFS-5702 Project: Hadoop HDFS

[jira] [Commented] (HDFS-5698) Use protobuf to serialize / deserialize FSImage

[ https://issues.apache.org/jira/browse/HDFS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13856308#comment-13856308 ] Vinay commented on HDFS-5698: - Thanks for filing this Jira [~wheat9]. Looks like its going to

[jira] [Updated] (HDFS-5600) FsShell CLI: add getfacl and setfacl with minimal support for getting and setting ACLs.

[ https://issues.apache.org/jira/browse/HDFS-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5600: Attachment: HDFS-5600.patch Attaching the updated patch. Addressed Uma's comment. Updated stickybit printing based

[jira] [Updated] (HDFS-5600) FsShell CLI: add getfacl and setfacl with minimal support for getting and setting ACLs.

[ https://issues.apache.org/jira/browse/HDFS-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5600: Attachment: HDFS-5600.patch Thanks Chris for the detailed review and comments. I have tried to address all your

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848939#comment-13848939 ] Vinay commented on HDFS-5496: - {quote}How about changing this to {code}if (!isInSafeMode() ||

[jira] [Updated] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5496: Attachment: HDFS-5496.patch Attaching the patch with below changes. 1. Included reprocessing from

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848962#comment-13848962 ] Vinay commented on HDFS-5496: - Also added a method to get the progress of initialization. Which

[jira] [Updated] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5496: Attachment: HDFS-5496.patch Added missed change Make replication queue initialization asynchronous

[jira] [Commented] (HDFS-5592) DIR* completeFile: /file is closed by DFSClient_ should be logged only for successful closure of the file.

[ https://issues.apache.org/jira/browse/HDFS-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848986#comment-13848986 ] Vinay commented on HDFS-5592: - Thanks Uma DIR* completeFile: /file is closed by DFSClient_

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13849961#comment-13849961 ] Vinay commented on HDFS-5496: - Thanks for the explanation Jing. I knew I missed something. Now

[jira] [Updated] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5496: Attachment: HDFS-5496.patch Here is updated patch Make replication queue initialization asynchronous

[jira] [Assigned] (HDFS-5638) FileContext API for ACLs.

[ https://issues.apache.org/jira/browse/HDFS-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay reassigned HDFS-5638: --- Assignee: Vinay FileContext API for ACLs. - Key: HDFS-5638

[jira] [Created] (HDFS-5669) Storage#tryLock() should check for null before logging successfull message

Vinay created HDFS-5669: --- Summary: Storage#tryLock() should check for null before logging successfull message Key: HDFS-5669 URL: https://issues.apache.org/jira/browse/HDFS-5669 Project: Hadoop HDFS

[jira] [Updated] (HDFS-5669) Storage#tryLock() should check for null before logging successfull message

[ https://issues.apache.org/jira/browse/HDFS-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5669: Affects Version/s: 2.2.0 Status: Patch Available (was: Open) Storage#tryLock() should check for

[jira] [Updated] (HDFS-5669) Storage#tryLock() should check for null before logging successfull message

[ https://issues.apache.org/jira/browse/HDFS-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5669: Attachment: HDFS-5669.patch Storage#tryLock() should check for null before logging successfull message

[jira] [Updated] (HDFS-5669) Storage#tryLock() should check for null before logging successfull message

[ https://issues.apache.org/jira/browse/HDFS-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5669: Description: In the following code in Storage#tryLock(), there is a possibility that

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846178#comment-13846178 ] Vinay commented on HDFS-5496: - bq. The following change would have been fine if leaving safe

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13847026#comment-13847026 ] Vinay commented on HDFS-5496: - Hi Jing, I think that would work. With that change, multiple

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13847049#comment-13847049 ] Vinay commented on HDFS-5496: - I think, block processing will be postponed, not put into

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13847063#comment-13847063 ] Vinay commented on HDFS-5496: - bq. So for that part of the change, can we make sure that

[jira] [Updated] (HDFS-5600) FsShell CLI: add getfacl and setfacl with minimal support for getting and setting ACLs.

[ https://issues.apache.org/jira/browse/HDFS-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5600: Attachment: HDFS-5600.patch Attaching a patch for FsShell CLI implementations. Tests needs to be updated after

[jira] [Updated] (HDFS-5638) FileContext API for ACLs.

[ https://issues.apache.org/jira/browse/HDFS-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5638: Attachment: HDFS-5638.patch Attaching a patch to add ACL apis to FileContext and AbstractFileSystem FileContext

[jira] [Commented] (HDFS-5496) Make replication queue initialization asynchronous

[ https://issues.apache.org/jira/browse/HDFS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845046#comment-13845046 ] Vinay commented on HDFS-5496: - bq. For (4), looks like currently we only retrieve metrics

  1   2   3   4   5   6   >