[jira] [Updated] (HDFS-4278) Log an ERROR when DFS_BLOCK_ACCESS_TOKEN_ENABLE config is disabled but security is turned on.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-4278: -- Summary: Log an ERROR when DFS_BLOCK_ACCESS_TOKEN_ENABLE config is disabled but security is turned on. (was: T

[jira] [Commented] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713388#comment-13713388 ] Harsh J commented on HDFS-4278: --- Thanks! Cleaning it up a bit and committing shortly.

[jira] [Updated] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-4979: -- Attachment: HDFS-4979.7.patch Updated patch to include previously missed test and to fix findbug

[jira] [Commented] (HDFS-5007) Replace hard-coded property keys with DFSConfigKeys fields

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713361#comment-13713361 ] Kousuke Saruta commented on HDFS-5007: -- Jing, thank you for committing!

[jira] [Updated] (HDFS-5007) Replace hard-coded property keys with DFSConfigKeys fields

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5007: Priority: Minor (was: Major) > Replace hard-coded property keys with DFSConfigKeys fields > ---

[jira] [Updated] (HDFS-5007) Replace hard-coded property keys with DFSConfigKeys fields

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5007: Component/s: (was: namenode) > Replace hard-coded property keys with DFSConfigKeys fields >

[jira] [Updated] (HDFS-5007) Replace hard-coded property keys with DFSConfigKeys fields

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5007: Resolution: Fixed Fix Version/s: (was: 3.0.0) 2.1.0-beta Target Ve

[jira] [Updated] (HDFS-5007) Replace hard-coded property keys with DFSConfigKeys fields

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5007: Issue Type: Improvement (was: Bug) > Replace hard-coded property keys with DFSConfigKeys fields > -

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713358#comment-13713358 ] Hadoop QA commented on HDFS-4979: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-4278: - Status: Patch Available (was: Open) > The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be auto

[jira] [Updated] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-4278: - Attachment: HDFS-4278.patch Thank you for your comment, Harsh! I've improved the error message.

[jira] [Updated] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-4278: - Status: Open (was: Patch Available) > The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be auto

[jira] [Commented] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713350#comment-13713350 ] Harsh J commented on HDFS-4278: --- Hi Kousuke, The patch looks good. Can we improve the messag

[jira] [Updated] (HDFS-5007) Replace hard-coded property keys with DFSConfigKeys fields

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5007: Summary: Replace hard-coded property keys with DFSConfigKeys fields (was: the property key "dfs.http.port"

[jira] [Updated] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-4278: - Target Version/s: 3.0.0 Status: Patch Available (was: Open) > The DFS_BLOCK_ACC

[jira] [Updated] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-4278: - Attachment: HDFS-4278.patch I've attached a new patch for logging error. > The DF

[jira] [Assigned] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta reassigned HDFS-4278: Assignee: Kousuke Saruta > The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatica

[jira] [Comment Edited] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713305#comment-13713305 ] Suresh Srinivas edited comment on HDFS-4979 at 7/19/13 4:57 AM: -

[jira] [Created] (HDFS-5012) replica.getGenerationStamp() may be >= recoveryId

Ted Yu created HDFS-5012: Summary: replica.getGenerationStamp() may be >= recoveryId Key: HDFS-5012 URL: https://issues.apache.org/jira/browse/HDFS-5012 Project: Hadoop HDFS Issue Type: Bug Affec

[jira] [Updated] (HDFS-5012) replica.getGenerationStamp() may be >= recoveryId

[ https://issues.apache.org/jira/browse/HDFS-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HDFS-5012: - Attachment: testReplicationQueueFailover.txt Here is the test output. > replica.getGenerationStam

[jira] [Commented] (HDFS-4019) FSShell should support creating symlinks

[ https://issues.apache.org/jira/browse/HDFS-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713329#comment-13713329 ] Colin Patrick McCabe commented on HDFS-4019: Now that symlinks have been added

[jira] [Assigned] (HDFS-4019) FSShell should support creating symlinks

[ https://issues.apache.org/jira/browse/HDFS-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe reassigned HDFS-4019: -- Assignee: Colin Patrick McCabe (was: Andy Isaacson) > FSShell should suppor

[jira] [Commented] (HDFS-4949) Centralized cache management in HDFS

[ https://issues.apache.org/jira/browse/HDFS-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713327#comment-13713327 ] Colin Patrick McCabe commented on HDFS-4949: A meetup is a good idea. I will b

[jira] [Commented] (HDFS-5007) the property key "dfs.http.port" and "dfs.https.port" are hard corded

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713318#comment-13713318 ] Hadoop QA commented on HDFS-5007: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-4979: -- Attachment: HDFS-4979.6.patch I realized that ClientProtocol#mkdirs() is idempotent. It always r

[jira] [Commented] (HDFS-5011) '._COPYING_' sufix temp file could prevent from running MapReduce job

[ https://issues.apache.org/jira/browse/HDFS-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713299#comment-13713299 ] Kousuke Saruta commented on HDFS-5011: -- Sorry, I've written wrong comment. the suffix

[jira] [Created] (HDFS-5011) '._COPYING_' sufix temp file could prevent from MapReduce job

Kousuke Saruta created HDFS-5011: Summary: '._COPYING_' sufix temp file could prevent from MapReduce job Key: HDFS-5011 URL: https://issues.apache.org/jira/browse/HDFS-5011 Project: Hadoop HDFS

[jira] [Updated] (HDFS-5011) '._COPYING_' sufix temp file could prevent from running MapReduce job

[ https://issues.apache.org/jira/browse/HDFS-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-5011: - Summary: '._COPYING_' sufix temp file could prevent from running MapReduce job (was: '._COPYING

[jira] [Commented] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713292#comment-13713292 ] Harsh J commented on HDFS-4278: --- bq. How do you make it work for testing purpose? I felt it

[jira] [Commented] (HDFS-4278) The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on when security is enabled.

[ https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713281#comment-13713281 ] Kousuke Saruta commented on HDFS-4278: -- Harsh, do you have any concrete ideas? So far,

[jira] [Commented] (HDFS-4817) make HDFS advisory caching configurable on a per-file basis

[ https://issues.apache.org/jira/browse/HDFS-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713278#comment-13713278 ] Aaron T. Myers commented on HDFS-4817: -- Latest patch looks really good. Two very small

[jira] [Updated] (HDFS-5007) the property key "dfs.http.port" and "dfs.https.port" are hard corded

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-5007: - Status: Patch Available (was: Open) > the property key "dfs.http.port" and "dfs.https.port" a

[jira] [Updated] (HDFS-5007) the property key "dfs.http.port" and "dfs.https.port" are hard corded

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-5007: - Attachment: HDFS-5007.patch Thanks for adding me as a contributor and checking my patch, Jing! I'v

[jira] [Updated] (HDFS-5007) the property key "dfs.http.port" and "dfs.https.port" are hard corded

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-5007: - Status: Open (was: Patch Available) > the property key "dfs.http.port" and "dfs.https.port" a

[jira] [Commented] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713253#comment-13713253 ] Konstantin Boudnik commented on HDFS-5004: -- Luke, care to review the patch? It see

[jira] [Commented] (HDFS-5010) Reduce the frequency of getCurrentUser() calls from namenode

[ https://issues.apache.org/jira/browse/HDFS-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713230#comment-13713230 ] Hadoop QA commented on HDFS-5010: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-3220) Improve some block recovery log messages

[ https://issues.apache.org/jira/browse/HDFS-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713215#comment-13713215 ] Jean-Daniel Cryans commented on HDFS-3220: -- Hey [~eli], I did see this in "real li

[jira] [Commented] (HDFS-4974) Analyze and add annotations to Namenode and Datanode protocol methods to enable retry

[ https://issues.apache.org/jira/browse/HDFS-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713140#comment-13713140 ] Suresh Srinivas commented on HDFS-4974: --- [~shv] There are some protocol methods such

[jira] [Commented] (HDFS-5007) the property key "dfs.http.port" and "dfs.https.port" are hard corded

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713122#comment-13713122 ] Jing Zhao commented on HDFS-5007: - Thanks Kousuke. I've added you as a contributor and assi

[jira] [Commented] (HDFS-4949) Centralized cache management in HDFS

[ https://issues.apache.org/jira/browse/HDFS-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713117#comment-13713117 ] Sanjay Radia commented on HDFS-4949: To converge on this could we do a meetup?

[jira] [Updated] (HDFS-5007) the property key "dfs.http.port" and "dfs.https.port" are hard corded

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5007: Assignee: Kousuke Saruta > the property key "dfs.http.port" and "dfs.https.port" are hard corded > -

[jira] [Commented] (HDFS-4794) Browsing filesystem via webui throws kerberos exception when NN service RPC is enabled in a secure cluster

[ https://issues.apache.org/jira/browse/HDFS-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713109#comment-13713109 ] Jitendra Nath Pandey commented on HDFS-4794: I see that JspHelper.namenodeAddr

[jira] [Updated] (HDFS-5010) Reduce the frequency of getCurrentUser() calls from namenode

[ https://issues.apache.org/jira/browse/HDFS-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-5010: - Component/s: performance namenode Affects Version/s: 2.1.0-beta

[jira] [Updated] (HDFS-5010) Reduce the frequency of getCurrentUser() calls from namenode

[ https://issues.apache.org/jira/browse/HDFS-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-5010: - Status: Patch Available (was: Open) > Reduce the frequency of getCurrentUser() calls from namenode >

[jira] [Updated] (HDFS-5010) Reduce the frequency of getCurrentUser() calls from namenode

[ https://issues.apache.org/jira/browse/HDFS-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-5010: - Attachment: HDFS-5010.patch > Reduce the frequency of getCurrentUser() calls from namenode > -

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713054#comment-13713054 ] Jing Zhao commented on HDFS-4979: - 1. For FSNamesystem#renameTo(String, String, Options.Ren

[jira] [Assigned] (HDFS-4946) Allow preferLocalNode in BlockPlacementPolicyDefault to be configurable

[ https://issues.apache.org/jira/browse/HDFS-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers reassigned HDFS-4946: Assignee: James Kinley > Allow preferLocalNode in BlockPlacementPolicyDefault to be conf

[jira] [Updated] (HDFS-5010) Reduce the frequency of getCurrentUser() calls from namenode

[ https://issues.apache.org/jira/browse/HDFS-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-5010: - Description: According to the "worst" jstack of a busy namenode I took, there were 29 BLOCKED handler thr

[jira] [Commented] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent

[ https://issues.apache.org/jira/browse/HDFS-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713013#comment-13713013 ] Hadoop QA commented on HDFS-5008: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4996: Resolution: Fixed Fix Version/s: 2.1.0-beta 3.0.0 Status: Resolv

[jira] [Commented] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712949#comment-13712949 ] Hudson commented on HDFS-4996: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4112 (See [https:

[jira] [Created] (HDFS-5010) Reduce the frequency of getCurrentUser() calls from namenode

Kihwal Lee created HDFS-5010: Summary: Reduce the frequency of getCurrentUser() calls from namenode Key: HDFS-5010 URL: https://issues.apache.org/jira/browse/HDFS-5010 Project: Hadoop HDFS Issue

[jira] [Created] (HDFS-5009) NameNode should expose storage type in the LocatedBlock

Arpit Agarwal created HDFS-5009: --- Summary: NameNode should expose storage type in the LocatedBlock Key: HDFS-5009 URL: https://issues.apache.org/jira/browse/HDFS-5009 Project: Hadoop HDFS Issue

[jira] [Updated] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4996: Hadoop Flags: Reviewed Thank you for the reviews, Arpit and Jing. I'll commit this.

[jira] [Updated] (HDFS-5000) DataNode configuration should allow specifying storage type

[ https://issues.apache.org/jira/browse/HDFS-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-5000: Description: The DataNode configuration should allow the administrator to optionally specify the st

[jira] [Commented] (HDFS-4985) Add storage type to the protocol and expose it in block report and block locations

[ https://issues.apache.org/jira/browse/HDFS-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712859#comment-13712859 ] Arpit Agarwal commented on HDFS-4985: - The failure looks unrelated. The test passes for

[jira] [Commented] (HDFS-4949) Centralized cache management in HDFS

[ https://issues.apache.org/jira/browse/HDFS-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712856#comment-13712856 ] Sanjay Radia commented on HDFS-4949: bq. we have to use mmap of a file on disk. Please

[jira] [Commented] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712832#comment-13712832 ] Jing Zhao commented on HDFS-4996: - +1 for the patch also. > ClientProtocol

[jira] [Commented] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent

[ https://issues.apache.org/jira/browse/HDFS-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712826#comment-13712826 ] Hadoop QA commented on HDFS-5008: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-4985) Add storage type to the protocol and expose it in block report and block locations

[ https://issues.apache.org/jira/browse/HDFS-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712805#comment-13712805 ] Hadoop QA commented on HDFS-4985: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712809#comment-13712809 ] Hadoop QA commented on HDFS-4996: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712801#comment-13712801 ] Arpit Agarwal commented on HDFS-4996: - +1 for the patch. Built and ran TestMetaSave on

[jira] [Updated] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent

[ https://issues.apache.org/jira/browse/HDFS-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5008: Status: Patch Available (was: Open) > Make ClientProtocol#abandonBlock() idempotent > -

[jira] [Updated] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent

[ https://issues.apache.org/jira/browse/HDFS-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5008: Attachment: HDFS-5008.002.patch Update the patch: if the block is no longer in the file, we do not need to

[jira] [Updated] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent

[ https://issues.apache.org/jira/browse/HDFS-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5008: Status: Open (was: Patch Available) > Make ClientProtocol#abandonBlock() idempotent > -

[jira] [Updated] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent

[ https://issues.apache.org/jira/browse/HDFS-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5008: Attachment: HDFS-5008.001.patch Initial patch for review. > Make ClientProtocol#abandonBloc

[jira] [Updated] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent

[ https://issues.apache.org/jira/browse/HDFS-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5008: Affects Version/s: 3.0.0 Status: Patch Available (was: Open) > Make ClientProtocol#aband

[jira] [Commented] (HDFS-4517) Cover class RemoteBlockReader with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712637#comment-13712637 ] Hadoop QA commented on HDFS-4517: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-4985) Add storage type to the protocol and expose it in block report and block locations

[ https://issues.apache.org/jira/browse/HDFS-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-4985: Status: Patch Available (was: Open) > Add storage type to the protocol and expose it in block r

[jira] [Updated] (HDFS-4985) Add storage type to the protocol and expose it in block report and block locations

[ https://issues.apache.org/jira/browse/HDFS-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-4985: Affects Version/s: 3.0.0 > Add storage type to the protocol and expose it in block report and bl

[jira] [Updated] (HDFS-4985) Add storage type to the protocol and expose it in block report and block locations

[ https://issues.apache.org/jira/browse/HDFS-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-4985: Attachment: HDFS-4985.001.patch Patch to add StorageMedium to LocatedBlock and DatanodeStorageInfo.

[jira] [Updated] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4996: Attachment: HDFS-4996.2.patch Uploading new patch, including mention of overwrite behavior in the do

[jira] [Updated] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4996: Status: Patch Available (was: Open) > ClientProtocol#metaSave can be made idempotent by overwri

[jira] [Updated] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4996: Release Note: The dfsadmin -metasave command has been changed to overwrite the output file. Previou

[jira] [Updated] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4996: Status: Open (was: Patch Available) Actually, I'm going to mention the overwrite behavior in the do

[jira] [Updated] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4996: Attachment: HDFS-4996.1.patch I'm attaching a patch to switch to opening the output file for overwri

[jira] [Updated] (HDFS-4996) ClientProtocol#metaSave can be made idempotent by overwriting the output file instead of appending to it

[ https://issues.apache.org/jira/browse/HDFS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4996: Status: Patch Available (was: Open) > ClientProtocol#metaSave can be made idempotent by overwri

[jira] [Commented] (HDFS-4949) Centralized cache management in HDFS

[ https://issues.apache.org/jira/browse/HDFS-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712579#comment-13712579 ] Colin Patrick McCabe commented on HDFS-4949: As Todd, Andrew, and I said before

[jira] [Created] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent

Suresh Srinivas created HDFS-5008: - Summary: Make ClientProtocol#abandonBlock() idempotent Key: HDFS-5008 URL: https://issues.apache.org/jira/browse/HDFS-5008 Project: Hadoop HDFS Issue Type:

[jira] [Assigned] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent

[ https://issues.apache.org/jira/browse/HDFS-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao reassigned HDFS-5008: --- Assignee: Jing Zhao > Make ClientProtocol#abandonBlock() idempotent >

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712562#comment-13712562 ] Suresh Srinivas commented on HDFS-4979: --- bq. notifyAll... Chris, you are right. Nice

[jira] [Commented] (HDFS-4949) Centralized cache management in HDFS

[ https://issues.apache.org/jira/browse/HDFS-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712529#comment-13712529 ] Sanjay Radia commented on HDFS-4949: Caching partial blocks: There is no problem with a

[jira] [Updated] (HDFS-4517) Cover class RemoteBlockReader with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Bondarev updated HDFS-4517: - Attachment: HADOOP-4517-branch-2--N4.patch > Cover class RemoteBlockReader with unit tests > -

[jira] [Updated] (HDFS-4517) Cover class RemoteBlockReader with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Bondarev updated HDFS-4517: - Attachment: (was: HADOOP-4517-branch-2--N4.patch) > Cover class RemoteBlockReader with uni

[jira] [Updated] (HDFS-4517) Cover class RemoteBlockReader with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Bondarev updated HDFS-4517: - Attachment: HDFS-4517-branch-2--N4.patch > Cover class RemoteBlockReader with unit tests > ---

[jira] [Updated] (HDFS-4517) Cover class RemoteBlockReader with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Bondarev updated HDFS-4517: - Attachment: HADOOP-4517-branch-2-N4.patch > Cover class RemoteBlockReader with unit tests > --

[jira] [Updated] (HDFS-4517) Cover class RemoteBlockReader with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Bondarev updated HDFS-4517: - Attachment: (was: HADOOP-4517-branch-2-N4.patch) > Cover class RemoteBlockReader with unit

[jira] [Commented] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712356#comment-13712356 ] Hudson commented on HDFS-5003: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1491 (See [htt

[jira] [Commented] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

[ https://issues.apache.org/jira/browse/HDFS-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712354#comment-13712354 ] Hudson commented on HDFS-5005: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1491 (See [htt

[jira] [Commented] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712317#comment-13712317 ] Hadoop QA commented on HDFS-5004: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

[ https://issues.apache.org/jira/browse/HDFS-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712302#comment-13712302 ] Hudson commented on HDFS-5005: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1464 (See [https://

[jira] [Commented] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712304#comment-13712304 ] Hudson commented on HDFS-5003: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1464 (See [https://

[jira] [Commented] (HDFS-4943) WebHdfsFileSystem does not work when original file path has encoded chars

[ https://issues.apache.org/jira/browse/HDFS-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712278#comment-13712278 ] Hudson commented on HDFS-4943: -- SUCCESS: Integrated in Hadoop-Hdfs-0.23-Build #672 (See [http

[jira] [Updated] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated HDFS-5004: - Status: Patch Available (was: Open) > Add additional JMX bean for NameNode status data >

[jira] [Updated] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated HDFS-5004: - Attachment: HDFS-5004.diff Added NameNodeStatusMXBean, diffed against trunk > Add

[jira] [Updated] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated HDFS-5004: - Attachment: (was: HDFS-5004.diff) > Add additional JMX bean for NameNode status data > ---

[jira] [Updated] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated HDFS-5004: - Status: Open (was: Patch Available) > Add additional JMX bean for NameNode status data >

[jira] [Commented] (HDFS-5007) the property key "dfs.http.port" and "dfs.https.port" are hard corded

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712224#comment-13712224 ] Hadoop QA commented on HDFS-5007: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

[ https://issues.apache.org/jira/browse/HDFS-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712212#comment-13712212 ] Hudson commented on HDFS-5005: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #274 (See [https://b

[jira] [Commented] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712214#comment-13712214 ] Hudson commented on HDFS-5003: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #274 (See [https://b

  1   2   >