[jira] [Updated] (HDFS-1619) Remove AC_TYPE* from the libhdfs

[ https://issues.apache.org/jira/browse/HDFS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-1619: -- Resolution: Fixed Status: Resolved (was: Patch Available) I've committed this to branch 22 and

[jira] [Commented] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

[ https://issues.apache.org/jira/browse/HDFS-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045279#comment-13045279 ] Hairong Kuang commented on HDFS-1948: - +1 lgtm. Thanks, Stack! > Forward port 'hdfs-15

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045278#comment-13045278 ] stack commented on HDFS-941: I took a look at patch. It looks good to me. Minor comments below

[jira] [Commented] (HDFS-2042) Require c99 when building libhdfs

[ https://issues.apache.org/jira/browse/HDFS-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045235#comment-13045235 ] Allen Wittenauer commented on HDFS-2042: Agreed. I've got a patch that removes alm

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

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

[jira] [Assigned] (HDFS-2041) Some mtimes and atimes are lost when edit logs are replayed

[ https://issues.apache.org/jira/browse/HDFS-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers reassigned HDFS-2041: Assignee: Todd Lipcon > Some mtimes and atimes are lost when edit logs are replayed > --

[jira] [Updated] (HDFS-1998) make refresh-namodenodes.sh refreshing all namenodes

[ https://issues.apache.org/jira/browse/HDFS-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-1998: -- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Availabl

[jira] [Commented] (HDFS-2013) Recurring failure of TestMissingBlocksAlert on branch-0.22

[ https://issues.apache.org/jira/browse/HDFS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045220#comment-13045220 ] Suresh Srinivas commented on HDFS-2013: --- You are right. Hudson tests had indicated te

[jira] [Commented] (HDFS-2017) A partial rollback cause the new changes done after upgrade to be visible after rollback

[ https://issues.apache.org/jira/browse/HDFS-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045219#comment-13045219 ] Suresh Srinivas commented on HDFS-2017: --- > Here , it is the Namenode process stopping

[jira] [Updated] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2003: -- Attachment: hdfs-2003.txt - Updated patch against trunk to include the new ReassignLeaseOp. - I filed HD

[jira] [Commented] (HDFS-2042) Require c99 when building libhdfs

[ https://issues.apache.org/jira/browse/HDFS-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045213#comment-13045213 ] Eli Collins commented on HDFS-2042: --- Our configure file already has compiler-specific sec

[jira] [Updated] (HDFS-2041) Some mtimes and atimes are lost when edit logs are replayed

[ https://issues.apache.org/jira/browse/HDFS-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2041: -- Attachment: hdfs-2041.txt Patch on top of HDFS-2003 to fix this issue. > Some mtimes and atimes are los

[jira] [Commented] (HDFS-2042) Require c99 when building libhdfs

[ https://issues.apache.org/jira/browse/HDFS-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045212#comment-13045212 ] Allen Wittenauer commented on HDFS-2042: Setting of CFLAGS is almost always non-por

[jira] [Updated] (HDFS-1619) Remove AC_TYPE* from the libhdfs

[ https://issues.apache.org/jira/browse/HDFS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-1619: -- Description: Remove AC_TYPE* from the libhdfs build since we get these via stdint. Currently configure.

[jira] [Commented] (HDFS-1980) Move build/webapps deeper in directory heirarchy to aid eclipse users

[ https://issues.apache.org/jira/browse/HDFS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045209#comment-13045209 ] Hudson commented on HDFS-1980: -- Integrated in Hadoop-Hdfs-22-branch #62 (See [https://builds.

[jira] [Created] (HDFS-2042) Require c99 when building libhdfs

Require c99 when building libhdfs - Key: HDFS-2042 URL: https://issues.apache.org/jira/browse/HDFS-2042 Project: Hadoop HDFS Issue Type: Improvement Components: libhdfs Reporter: Eli Coll

[jira] [Commented] (HDFS-2039) TestNameNodeMetrics uses a bad test root path

[ https://issues.apache.org/jira/browse/HDFS-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045210#comment-13045210 ] Hudson commented on HDFS-2039: -- Integrated in Hadoop-Hdfs-22-branch #62 (See [https://builds.

[jira] [Commented] (HDFS-1619) Does libhdfs really need to depend on AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T and AC_TYPE_UINT16_T ?

[ https://issues.apache.org/jira/browse/HDFS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045206#comment-13045206 ] Eli Collins commented on HDFS-1619: --- This patch does not remove the c99 requirement, we d

[jira] [Created] (HDFS-2041) Some mtimes and atimes are lost when edit logs are replayed

Some mtimes and atimes are lost when edit logs are replayed --- Key: HDFS-2041 URL: https://issues.apache.org/jira/browse/HDFS-2041 Project: Hadoop HDFS Issue Type: Bug Affects Vers

[jira] [Commented] (HDFS-1619) Does libhdfs really need to depend on AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T and AC_TYPE_UINT16_T ?

[ https://issues.apache.org/jira/browse/HDFS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045201#comment-13045201 ] Allen Wittenauer commented on HDFS-1619: libhdfs already requires c99 mode for vari

[jira] [Updated] (HDFS-2040) Only build libhdfs if a flag is passed

[ https://issues.apache.org/jira/browse/HDFS-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2040: -- Attachment: hdfs-2040-1.patch Patch attached: * Removes the auto-setting of libhdfs * Modifies bin-packa

[jira] [Created] (HDFS-2040) Only build libhdfs if a flag is passed

Only build libhdfs if a flag is passed -- Key: HDFS-2040 URL: https://issues.apache.org/jira/browse/HDFS-2040 Project: Hadoop HDFS Issue Type: Improvement Affects Versions: 0.23.0 Reporter:

[jira] [Commented] (HDFS-1950) Blocks that are under construction are not getting read if the blocks are more than 10. Only complete blocks are read properly.

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

[jira] [Assigned] (HDFS-1148) Convert FSDataset to ReadWriteLock

[ https://issues.apache.org/jira/browse/HDFS-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Thompson reassigned HDFS-1148: --- Assignee: Dave Thompson (was: Todd Lipcon) > Convert FSDataset to ReadWriteLock > ---

[jira] [Updated] (HDFS-1619) Does libhdfs really need to depend on AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T and AC_TYPE_UINT16_T ?

[ https://issues.apache.org/jira/browse/HDFS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-1619: -- Component/s: libhdfs Fix Version/s: 0.22.0 Assignee: Roman Shaposhnik (was: Konstantin Sh

[jira] [Commented] (HDFS-1950) Blocks that are under construction are not getting read if the blocks are more than 10. Only complete blocks are read properly.

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

[jira] [Updated] (HDFS-1149) Lease reassignment is not persisted to edit log

[ https://issues.apache.org/jira/browse/HDFS-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-1149: -- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) +1.

[jira] [Commented] (HDFS-1619) Does libhdfs really need to depend on AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T and AC_TYPE_UINT16_T ?

[ https://issues.apache.org/jira/browse/HDFS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045176#comment-13045176 ] Roman Shaposhnik commented on HDFS-1619: After some additional googling around it s

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045171#comment-13045171 ] Ivan Kelly commented on HDFS-2003: -- Im +1 on all these changes. One small question though.

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

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

[jira] [Commented] (HDFS-2011) Removal and restoration of storage directories on checkpointing failure doesn't work properly

[ https://issues.apache.org/jira/browse/HDFS-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045168#comment-13045168 ] Matt Foley commented on HDFS-2011: -- Oh, and in that last bit of code, if fc is still open

[jira] [Commented] (HDFS-1950) Blocks that are under construction are not getting read if the blocks are more than 10. Only complete blocks are read properly.

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

[jira] [Commented] (HDFS-2011) Removal and restoration of storage directories on checkpointing failure doesn't work properly

[ https://issues.apache.org/jira/browse/HDFS-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045163#comment-13045163 ] Matt Foley commented on HDFS-2011: -- Hi Ravi, looking a lot better. Here's a few more. Te

[jira] [Commented] (HDFS-1950) Blocks that are under construction are not getting read if the blocks are more than 10. Only complete blocks are read properly.

[ https://issues.apache.org/jira/browse/HDFS-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045161#comment-13045161 ] Todd Lipcon commented on HDFS-1950: --- Hi Ramkrishna. Could you please explain in some deta

[jira] [Updated] (HDFS-1950) Blocks that are under construction are not getting read if the blocks are more than 10. Only complete blocks are read properly.

[ https://issues.apache.org/jira/browse/HDFS-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-1950: -- Attachment: hdfs-1950-0.20-append-tests.txt cleaned up tests on 0.20-append > Blocks that are under con

[jira] [Commented] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

[ https://issues.apache.org/jira/browse/HDFS-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045157#comment-13045157 ] stack commented on HDFS-1948: - @Hairong I uploaded patch and above is what jenkins thinks of th

[jira] [Commented] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

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

[jira] [Updated] (HDFS-1950) Blocks that are under construction are not getting read if the blocks are more than 10. Only complete blocks are read properly.

[ https://issues.apache.org/jira/browse/HDFS-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-1950: -- Attachment: hdfs-1950-trunk-test.txt same patch with shorter test method names > Blocks that are under

[jira] [Updated] (HDFS-1950) Blocks that are under construction are not getting read if the blocks are more than 10. Only complete blocks are read properly.

[ https://issues.apache.org/jira/browse/HDFS-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-1950: -- Attachment: hdfs-1950-trunk-test.txt Cleaned up and updated the test case for trunk to make sure this bu

[jira] [Commented] (HDFS-1149) Lease reassignment is not persisted to edit log

[ https://issues.apache.org/jira/browse/HDFS-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045143#comment-13045143 ] Aaron T. Myers commented on HDFS-1149: -- TestBalancer just passed for me on my local bo

[jira] [Commented] (HDFS-1149) Lease reassignment is not persisted to edit log

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

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

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

[jira] [Updated] (HDFS-2039) TestNameNodeMetrics uses a bad test root path

[ https://issues.apache.org/jira/browse/HDFS-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2039: -- Resolution: Fixed Fix Version/s: (was: 0.23.0) 0.22.0 Hadoop Flags: [R

[jira] [Commented] (HDFS-2039) TestNameNodeMetrics uses a bad test root path

[ https://issues.apache.org/jira/browse/HDFS-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045120#comment-13045120 ] Matt Foley commented on HDFS-2039: -- +1. Normally I expect file manipulations to work equa

[jira] [Updated] (HDFS-248) dynamically add/subtract dfs.name.dir directories

[ https://issues.apache.org/jira/browse/HDFS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-248: - Assignee: (was: John George) > dynamically add/subtract dfs.name.dir directories >

[jira] [Updated] (HDFS-2025) Go Back to File View link is not working in tail.jsp

[ https://issues.apache.org/jira/browse/HDFS-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2025: -- Status: Open (was: Patch Available) canceling patch due to failed test > Go Back to File View link is

[jira] [Updated] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

[ https://issues.apache.org/jira/browse/HDFS-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HDFS-1948: Status: Patch Available (was: Open) > Forward port 'hdfs-1520 lightweight namenode operation to trigger lease > re

[jira] [Updated] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

[ https://issues.apache.org/jira/browse/HDFS-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HDFS-1948: Status: Open (was: Patch Available) > Forward port 'hdfs-1520 lightweight namenode operation to trigger lease > re

[jira] [Updated] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

[ https://issues.apache.org/jira/browse/HDFS-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HDFS-1948: Attachment: 1948-v4-minus_rpc_version_change.txt v4 of the patch for TRUNK minus rpc version increment. > Forward p

[jira] [Updated] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2003: -- Attachment: hdfs-2003.txt Rebased patch against trunk, using the new LayoutVersion support, etc. > Sepa

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

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

[jira] [Updated] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2003: -- Attachment: 2003-delta.txt Here is a patch on top of your latest (https://issues.apache.org/jira/secure

[jira] [Updated] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-2034: -- Attachment: HDFS-2034-3.patch Thanks Todd. Attaching a patch with the following changes. - added assert

[jira] [Commented] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

[ https://issues.apache.org/jira/browse/HDFS-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045067#comment-13045067 ] Hairong Kuang commented on HDFS-1948: - Yes, please update the patch for the trunk. > F

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045061#comment-13045061 ] Todd Lipcon commented on HDFS-2003: --- - Looks like a missing import in FSEditLogLoader of

[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI

[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045060#comment-13045060 ] Konstantin Shvachko commented on HDFS-1954: --- FAQ is here: [HDFS 3.15|http://wiki

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

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

[jira] [Updated] (HDFS-1149) Lease reassignment is not persisted to edit log

[ https://issues.apache.org/jira/browse/HDFS-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-1149: - Attachment: hdfs-1149.2.patch Thanks a lot for the review, Todd. The only change in this latest pa

[jira] [Commented] (HDFS-1149) Lease reassignment is not persisted to edit log

[ https://issues.apache.org/jira/browse/HDFS-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045052#comment-13045052 ] Todd Lipcon commented on HDFS-1149: --- It seems to me that the new condition for safe mode

[jira] [Commented] (HDFS-1149) Lease reassignment is not persisted to edit log

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

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045043#comment-13045043 ] Todd Lipcon commented on HDFS-2034: --- In general regarding asserts: - definitely don't rel

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

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

[jira] [Updated] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-2034: -- Attachment: HDFS-2034-2.patch Good point about the "incomplete block being added to an offset larger tha

[jira] [Commented] (HDFS-1980) Move build/webapps deeper in directory heirarchy to aid eclipse users

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

[jira] [Commented] (HDFS-2039) TestNameNodeMetrics uses a bad test root path

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

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045003#comment-13045003 ] Daryn Sharp commented on HDFS-2034: --- Looking good! bq. The reason I am hesitant about ad

[jira] [Updated] (HDFS-1149) Lease reassignment is not persisted to edit log

[ https://issues.apache.org/jira/browse/HDFS-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-1149: - Attachment: hdfs-1149.1.patch Resubmitting the patch since test-patch tried to apply the binary {

[jira] [Commented] (HDFS-1149) Lease reassignment is not persisted to edit log

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

[jira] [Commented] (HDFS-1980) Move build/webapps deeper in directory heirarchy to aid eclipse users

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

[jira] [Updated] (HDFS-1148) Convert FSDataset to ReadWriteLock

[ https://issues.apache.org/jira/browse/HDFS-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-1148: -- Status: Open (was: Patch Available) looks like this caused test timeouts: https://builds.apache.org/jo

[jira] [Updated] (HDFS-1980) Move build/webapps deeper in directory heirarchy to aid eclipse users

[ https://issues.apache.org/jira/browse/HDFS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-1980: -- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) Comm

[jira] [Updated] (HDFS-1149) Lease reassignment is not persisted to edit log

[ https://issues.apache.org/jira/browse/HDFS-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-1149: - Attachment: editsStored hdfs-1149.1.patch Thanks a lot for the review, Todd. Atta

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

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

[jira] [Commented] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

[ https://issues.apache.org/jira/browse/HDFS-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044986#comment-13044986 ] stack commented on HDFS-1948: - @Hairong Thanks for the review. OK with you if I commit the pa

[jira] [Updated] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-941: - Attachment: hdfs-941.txt Updated patch to fix failing tests: - TestDFSClientRetries works by setting the ma

[jira] [Commented] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

[ https://issues.apache.org/jira/browse/HDFS-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044979#comment-13044979 ] Hairong Kuang commented on HDFS-1948: - Both patches look good! Stack, thanks for your t

[jira] [Commented] (HDFS-1619) Does libhdfs really need to depend on AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T and AC_TYPE_UINT16_T ?

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

[jira] [Updated] (HDFS-1619) Does libhdfs really need to depend on AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T and AC_TYPE_UINT16_T ?

[ https://issues.apache.org/jira/browse/HDFS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shaposhnik updated HDFS-1619: --- Attachment: HDFS-1619-C99.patch.txt Agreed. Minor nitpick, I think we should replace AC_PROG_C

[jira] [Updated] (HDFS-1923) Intermittent recurring failure in TestFiDataTransferProtocol2.pipeline_Fi_29

[ https://issues.apache.org/jira/browse/HDFS-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1923: - Resolution: Fixed Fix Version/s: 0.23.0 Hadoop Flags: [Reviewed]

[jira] [Created] (HDFS-2039) TestNameNodeMetrics uses a bad test root path

TestNameNodeMetrics uses a bad test root path - Key: HDFS-2039 URL: https://issues.apache.org/jira/browse/HDFS-2039 Project: Hadoop HDFS Issue Type: Improvement Affects Versions: 0.23.0

[jira] [Updated] (HDFS-2039) TestNameNodeMetrics uses a bad test root path

[ https://issues.apache.org/jira/browse/HDFS-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2039: -- Attachment: hdfs-2039.txt > TestNameNodeMetrics uses a bad test root path >

[jira] [Updated] (HDFS-2039) TestNameNodeMetrics uses a bad test root path

[ https://issues.apache.org/jira/browse/HDFS-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2039: -- Status: Patch Available (was: Open) > TestNameNodeMetrics uses a bad test root path > -

[jira] [Commented] (HDFS-1980) Move build/webapps deeper in directory heirarchy to aid eclipse users

[ https://issues.apache.org/jira/browse/HDFS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044962#comment-13044962 ] Eli Collins commented on HDFS-1980: --- The test failure above is unrelated. > Move build/w

[jira] [Updated] (HDFS-1980) Move build/webapps deeper in directory heirarchy to aid eclipse users

[ https://issues.apache.org/jira/browse/HDFS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-1980: -- Attachment: hdfs-1980-1.patch +1 Uploading patch that applies to trunk. > Move build/webapps deeper in

[jira] [Commented] (HDFS-1923) Intermittent recurring failure in TestFiDataTransferProtocol2.pipeline_Fi_29

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

[jira] [Updated] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-2034: -- Attachment: HDFS-2034-1.patch > Daryn Sharp commented on HDFS-2034: > -

[jira] [Updated] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-2034: -- Attachment: HDFS-2034-1.patch > Daryn Sharp commented on HDFS-2034: > -

[jira] [Commented] (HDFS-1923) Intermittent recurring failure in TestFiDataTransferProtocol2.pipeline_Fi_29

[ https://issues.apache.org/jira/browse/HDFS-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044947#comment-13044947 ] Tsz Wo (Nicholas), SZE commented on HDFS-1923: -- > That is to say, if you had a

[jira] [Commented] (HDFS-2004) Enable replicating and pinning files to a data node

[ https://issues.apache.org/jira/browse/HDFS-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044943#comment-13044943 ] Allen Wittenauer commented on HDFS-2004: bq. What if this theoretical facility only

[jira] [Commented] (HDFS-2018) Move all journal stream management code into one place

[ https://issues.apache.org/jira/browse/HDFS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044913#comment-13044913 ] Ivan Kelly commented on HDFS-2018: -- This would also mean removing edits completely from th

[jira] [Commented] (HDFS-2025) Go Back to File View link is not working in tail.jsp

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

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044900#comment-13044900 ] Daryn Sharp commented on HDFS-2034: --- * I'd suggest changing {{"lastblkcomplete but read p

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044873#comment-13044873 ] Ivan Kelly commented on HDFS-2003: -- I've uploaded a new patch which reduces the number of

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

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

[jira] [Updated] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-2003: - Attachment: HDFS-2003.diff > Separate FSEditLog reading logic from editLog memory state building logic > -

[jira] [Updated] (HDFS-2025) Go Back to File View link is not working in tail.jsp

[ https://issues.apache.org/jira/browse/HDFS-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sravankorumilli updated HDFS-2025: -- Affects Version/s: (was: 0.20.1) Status: Patch Available (was: Open) > Go Ba

[jira] [Updated] (HDFS-2025) Go Back to File View link is not working in tail.jsp

[ https://issues.apache.org/jira/browse/HDFS-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sravankorumilli updated HDFS-2025: -- Attachment: HDFS-2025.patch > Go Back to File View link is not working in tail.jsp > ---

[jira] [Commented] (HDFS-1969) Running rollback on new-version namenode destroys namespace

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

[jira] [Commented] (HDFS-977) DataNode.createInterDataNodeProtocolProxy() guards a log at the wrong level

[ https://issues.apache.org/jira/browse/HDFS-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044797#comment-13044797 ] Hudson commented on HDFS-977: - Integrated in Hadoop-Hdfs-22-branch #61 (See [https://builds.apa

[jira] [Commented] (HDFS-1978) All but first option in LIBHDFS_OPTS is ignored

[ https://issues.apache.org/jira/browse/HDFS-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044798#comment-13044798 ] Hudson commented on HDFS-1978: -- Integrated in Hadoop-Hdfs-22-branch #61 (See [https://builds.

  1   2   >