[jira] [Created] (HDFS-2028) There are lot of ESTABLISHED socket connetions at 50010 port.

There are lot of ESTABLISHED socket connetions at 50010 port. - Key: HDFS-2028 URL: https://issues.apache.org/jira/browse/HDFS-2028 Project: Hadoop HDFS Issue Type: Bug

[jira] [Updated] (HDFS-1934) Fix NullPointerException when File.listFiles() API returns null

[ https://issues.apache.org/jira/browse/HDFS-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-1934: - Resolution: Fixed Status: Resolved (was: Patch Available) Fix NullPointerException when

[jira] [Assigned] (HDFS-1454) Update the documentation to reflect true client caching strategy

[ https://issues.apache.org/jira/browse/HDFS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J Chouraria reassigned HDFS-1454: --- Assignee: Harsh J Chouraria Update the documentation to reflect true client caching

[jira] [Updated] (HDFS-1454) Update the documentation to reflect true client caching strategy

[ https://issues.apache.org/jira/browse/HDFS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J Chouraria updated HDFS-1454: Attachment: HDFS-1454.r1.diff Initial docfix patch that gets rid of the staging talk.

[jira] [Commented] (HDFS-1968) Enhance TestWriteRead to support File Append and Position Read

[ https://issues.apache.org/jira/browse/HDFS-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043324#comment-13043324 ] Hudson commented on HDFS-1968: -- Integrated in Hadoop-Hdfs-trunk #686 (See

[jira] [Commented] (HDFS-2022) ant binary should build libhdfs

[ https://issues.apache.org/jira/browse/HDFS-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043325#comment-13043325 ] Hudson commented on HDFS-2022: -- Integrated in Hadoop-Hdfs-trunk #686 (See

[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-tabpanelfocusedCommentId=13043326#comment-13043326 ] Hudson commented on HDFS-1954: -- Integrated in Hadoop-Hdfs-trunk #686 (See

[jira] [Commented] (HDFS-2014) RPM packages broke bin/hdfs script

[ https://issues.apache.org/jira/browse/HDFS-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043327#comment-13043327 ] Hudson commented on HDFS-2014: -- Integrated in Hadoop-Hdfs-trunk #686 (See

[jira] [Commented] (HDFS-1986) Add an option for user to return http or https ports regardless of security is on/off in DFSUtil.getInfoServer()

[ https://issues.apache.org/jira/browse/HDFS-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043328#comment-13043328 ] Hudson commented on HDFS-1986: -- Integrated in Hadoop-Hdfs-trunk #686 (See

[jira] [Commented] (HDFS-1995) Minor modification to both dfsclusterhealth and dfshealth pages for Web UI

[ https://issues.apache.org/jira/browse/HDFS-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043329#comment-13043329 ] Hudson commented on HDFS-1995: -- Integrated in Hadoop-Hdfs-trunk #686 (See

[jira] [Updated] (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:all-tabpanel ] Ravi Prakash updated HDFS-2011: --- Attachment: HDFS-2011.4.patch Incorporated Matt's and Konstantin's comments Removal and restoration

[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-tabpanelfocusedCommentId=13043370#comment-13043370 ] Ravi Prakash commented on HDFS-2011: Hi Matt, Thanks a ton for your review! I learned

[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-tabpanelfocusedCommentId=13043383#comment-13043383 ] Ivan Kelly commented on HDFS-2003: -- I'm still waiting to get access to some big logs. If

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043405#comment-13043405 ] Daryn Sharp commented on HDFS-1907: --- +1 Ah. I didn't go further up the callstack to see

[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-tabpanelfocusedCommentId=13043414#comment-13043414 ] Hadoop QA commented on HDFS-2011: - +1 overall. Here are the results of testing the latest

[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-tabpanelfocusedCommentId=13043420#comment-13043420 ] Ivan Kelly commented on HDFS-2003: -- {quote} From the perspective of FSEditLogLoader, an

[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 Uploaded patch addressing Todd's comments Separate FSEditLog reading logic

[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-tabpanelfocusedCommentId=13043453#comment-13043453 ] Hadoop QA commented on HDFS-2003: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2014) RPM packages broke bin/hdfs script

[ https://issues.apache.org/jira/browse/HDFS-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043454#comment-13043454 ] Eric Yang commented on HDFS-2014: - Aaron, the developer setup is set HADOOP_COMMON_HOME to

[jira] [Commented] (HDFS-2014) RPM packages broke bin/hdfs script

[ https://issues.apache.org/jira/browse/HDFS-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043865#comment-13043865 ] Aaron T. Myers commented on HDFS-2014: -- Eric, I totally agree. The observation I'm

[jira] [Commented] (HDFS-1454) Update the documentation to reflect true client caching strategy

[ https://issues.apache.org/jira/browse/HDFS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043872#comment-13043872 ] Todd Lipcon commented on HDFS-1454: --- +1 pending Hudson. Thanks Harsh! It's amazing this

[jira] [Updated] (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:all-tabpanel ] Ivan Kelly updated HDFS-2018: - Attachment: HDFS-2018.diff Updated to work on top of latest HDFS-2003 patch Move all journal stream

[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-tabpanelfocusedCommentId=13043879#comment-13043879 ] Hadoop QA commented on HDFS-2018: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2028) There are lot of ESTABLISHED socket connetions at 50010 port.

[ https://issues.apache.org/jira/browse/HDFS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043880#comment-13043880 ] Matt Foley commented on HDFS-2028: -- There is an open bug related to lots of port 50010

[jira] [Commented] (HDFS-1787) Not enough xcievers error should propagate to client

[ https://issues.apache.org/jira/browse/HDFS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043882#comment-13043882 ] Jonathan Hsieh commented on HDFS-1787: -- Nicholas, Thanks for the review! {quote}

[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-tabpanelfocusedCommentId=13043892#comment-13043892 ] Todd Lipcon commented on HDFS-2011: --- A few style nits on HDFS-2011.4.patch: - please try

[jira] [Updated] (HDFS-1787) Not enough xcievers error should propagate to client

[ https://issues.apache.org/jira/browse/HDFS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh updated HDFS-1787: - Attachment: hdfs-1787.5.patch Not enough xcievers error should propagate to client

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043904#comment-13043904 ] Todd Lipcon commented on HDFS-1907: --- nits: - positionReadOption is already assigned to

[jira] [Updated] (HDFS-1454) Update the documentation to reflect true client caching strategy

[ https://issues.apache.org/jira/browse/HDFS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J Chouraria updated HDFS-1454: Tags: doc Fix Version/s: 0.23.0 Affects Version/s: 0.20.2

[jira] [Commented] (HDFS-2014) RPM packages broke bin/hdfs script

[ https://issues.apache.org/jira/browse/HDFS-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043912#comment-13043912 ] Eric Yang commented on HDFS-2014: - Aaron, HADOOP_COMMON_HOME and HADOOP_HDFS_HOME are the

[jira] [Updated] (HDFS-2014) bin/hdfs no longer works from a source checkout

[ https://issues.apache.org/jira/browse/HDFS-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang updated HDFS-2014: Summary: bin/hdfs no longer works from a source checkout (was: RPM packages broke bin/hdfs script)

[jira] [Updated] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

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

[jira] [Commented] (HDFS-2014) bin/hdfs no longer works from a source checkout

[ https://issues.apache.org/jira/browse/HDFS-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043927#comment-13043927 ] Aaron T. Myers commented on HDFS-2014: -- @Eric: ah, sorry, didn't realize that was

[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-tabpanelfocusedCommentId=13043928#comment-13043928 ] Todd Lipcon commented on HDFS-2003: --- bq. This is intentional. We read from the journal

[jira] [Created] (HDFS-2029) Improve TestWriteRead

Improve TestWriteRead - Key: HDFS-2029 URL: https://issues.apache.org/jira/browse/HDFS-2029 Project: Hadoop HDFS Issue Type: Improvement Components: test Reporter: Tsz Wo (Nicholas), SZE

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043929#comment-13043929 ] Tsz Wo (Nicholas), SZE commented on HDFS-1907: -- Created HDFS-2029.

[jira] [Assigned] (HDFS-2029) Improve TestWriteRead

[ https://issues.apache.org/jira/browse/HDFS-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George reassigned HDFS-2029: - Assignee: John George Improve TestWriteRead - Key:

[jira] [Commented] (HDFS-2014) bin/hdfs no longer works from a source checkout

[ https://issues.apache.org/jira/browse/HDFS-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043943#comment-13043943 ] Eric Yang commented on HDFS-2014: - Owen told me verbally in his cube. Add Owen for

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043941#comment-13043941 ] Hudson commented on HDFS-1907: -- Integrated in Hadoop-Hdfs-trunk-Commit #710 (See

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043942#comment-13043942 ] Todd Lipcon commented on HDFS-1907: --- No problem Nicholas. Do you have any thought on the

[jira] [Commented] (HDFS-2014) bin/hdfs no longer works from a source checkout

[ https://issues.apache.org/jira/browse/HDFS-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043946#comment-13043946 ] Todd Lipcon commented on HDFS-2014: --- It's unfortunate that all of these behavioral

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043949#comment-13043949 ] John George commented on HDFS-1907: --- If the last block is in progress then readPastEnd

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043951#comment-13043951 ] Tsz Wo (Nicholas), SZE commented on HDFS-1907: -- if the last block is

[jira] [Created] (HDFS-2030) Fix the usability of namenode upgrade command

Fix the usability of namenode upgrade command - Key: HDFS-2030 URL: https://issues.apache.org/jira/browse/HDFS-2030 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.23.0

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043955#comment-13043955 ] John George commented on HDFS-1907: --- Even I meant complete blocks not committed blocks.

[jira] [Created] (HDFS-2031) request test-patch to work with -Dresolvers=internal, for pre-patch and/or post-patch builds

request test-patch to work with -Dresolvers=internal, for pre-patch and/or post-patch builds Key: HDFS-2031 URL: https://issues.apache.org/jira/browse/HDFS-2031

[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-tabpanelfocusedCommentId=13043956#comment-13043956 ] Eli Collins commented on HDFS-1969: --- Todd, I agree that Konst's suggestion should be

[jira] [Commented] (HDFS-2031) request test-patch to work with -Dresolvers=internal, for pre-patch and/or post-patch builds

[ https://issues.apache.org/jira/browse/HDFS-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043960#comment-13043960 ] Todd Lipcon commented on HDFS-2031: --- Hey Matt. With the 'unsplit' of repositories

[jira] [Commented] (HDFS-1787) Not enough xcievers error should propagate to client

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

[jira] [Commented] (HDFS-2031) request test-patch to work with -Dresolvers=internal, for pre-patch and/or post-patch builds

[ https://issues.apache.org/jira/browse/HDFS-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043961#comment-13043961 ] Todd Lipcon commented on HDFS-2031: --- err sorry, typo... I meant HADOOP-7106 above.

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043965#comment-13043965 ] Todd Lipcon commented on HDFS-1907: --- aha, I see. Perhaps we can improve the readability

[jira] [Commented] (HDFS-1907) BlockMissingException upon concurrent read and write: reader was doing file position read while writer is doing write without hflush

[ https://issues.apache.org/jira/browse/HDFS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043970#comment-13043970 ] John George commented on HDFS-1907: --- Sorry, I was not very clear in my previous

[jira] [Commented] (HDFS-1454) Update the documentation to reflect true client caching strategy

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

[jira] [Updated] (HDFS-2029) Improve TestWriteRead

[ https://issues.apache.org/jira/browse/HDFS-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-2029: -- Attachment: HDFS-2029.patch Improve TestWriteRead - Key:

[jira] [Updated] (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:all-tabpanel ] Ravi Prakash updated HDFS-2011: --- Attachment: HDFS-2011.5.patch Removal and restoration of storage directories on checkpointing

[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-tabpanelfocusedCommentId=13043990#comment-13043990 ] Ravi Prakash commented on HDFS-2011: Hi Todd, Thanks a lot for reviewing the patch. :)

[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-tabpanelfocusedCommentId=13044011#comment-13044011 ] Todd Lipcon commented on HDFS-2011: --- re SecurityException: I still don't see any reason

[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-tabpanelfocusedCommentId=13044025#comment-13044025 ] Hadoop QA commented on HDFS-2011: - +1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2026) 1073: 2NN needs to handle case of reformatted NN better

[ https://issues.apache.org/jira/browse/HDFS-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044029#comment-13044029 ] Sanjay Radia commented on HDFS-2026: I also prefer option 1. Shouldn't we be using the

[jira] [Updated] (HDFS-1454) Update the documentation to reflect true client caching strategy

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

[jira] [Updated] (HDFS-2029) Improve TestWriteRead

[ https://issues.apache.org/jira/browse/HDFS-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2029: - Hadoop Flags: [Reviewed] Status: Patch Available (was: Open) +1 patch

[jira] [Commented] (HDFS-2026) 1073: 2NN needs to handle case of reformatted NN better

[ https://issues.apache.org/jira/browse/HDFS-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044034#comment-13044034 ] Todd Lipcon commented on HDFS-2026: --- Great. I'll move forward with option 1 -- yes, the

[jira] [Commented] (HDFS-2026) 1073: 2NN needs to handle case of reformatted NN better

[ https://issues.apache.org/jira/browse/HDFS-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044042#comment-13044042 ] Sanjay Radia commented on HDFS-2026: On a related note, each edits should have the same

[jira] [Commented] (HDFS-2026) 1073: 2NN needs to handle case of reformatted NN better

[ https://issues.apache.org/jira/browse/HDFS-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044047#comment-13044047 ] Todd Lipcon commented on HDFS-2026: --- I agree with that as well. I'll file a new JIRA for

[jira] [Created] (HDFS-2032) Encode namespace identification info in image and edits headers

Encode namespace identification info in image and edits headers --- Key: HDFS-2032 URL: https://issues.apache.org/jira/browse/HDFS-2032 Project: Hadoop HDFS Issue Type: Improvement

[jira] [Commented] (HDFS-2026) 1073: 2NN needs to handle case of reformatted NN better

[ https://issues.apache.org/jira/browse/HDFS-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044052#comment-13044052 ] Todd Lipcon commented on HDFS-2026: --- Created HDFS-2032 for the idea to add namespace id

[jira] [Commented] (HDFS-1454) Update the documentation to reflect true client caching strategy

[ https://issues.apache.org/jira/browse/HDFS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044056#comment-13044056 ] Hudson commented on HDFS-1454: -- Integrated in Hadoop-Hdfs-trunk-Commit #711 (See

[jira] [Commented] (HDFS-2029) Improve TestWriteRead

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

[jira] [Updated] (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:all-tabpanel ] Todd Lipcon updated HDFS-1969: -- Attachment: hdfs-1969.txt Updated patch based on Eli's comments. I decided to use IllegalStateException

[jira] [Updated] (HDFS-2031) request HDFS test-patch to support coordinated change in COMMON jar, for post-patch build only

[ https://issues.apache.org/jira/browse/HDFS-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-2031: - Description: For dev test, need to test an HDFS patch that is dependent on a modified COMMON jar. For

[jira] [Updated] (HDFS-2029) Improve TestWriteRead

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

[jira] [Commented] (HDFS-2029) Improve TestWriteRead

[ https://issues.apache.org/jira/browse/HDFS-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044101#comment-13044101 ] Hudson commented on HDFS-2029: -- Integrated in Hadoop-Hdfs-trunk-Commit #712 (See

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

[ https://issues.apache.org/jira/browse/HDFS-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044113#comment-13044113 ] Suresh Srinivas commented on HDFS-1998: --- Minor comments: # Could you change

[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-tabpanelfocusedCommentId=13044124#comment-13044124 ] Hadoop QA commented on HDFS-1969: - +1 overall. Here are the results of testing the latest

[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 ] Tanping Wang updated HDFS-1998: --- Attachment: HDFS-1998.3.patch Upload a patch to address the review comments. make

[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 ] Tanping Wang updated HDFS-1998: --- Status: Open (was: Patch Available) make refresh-namodenodes.sh refreshing all namenodes

[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 ] Tanping Wang updated HDFS-1998: --- Status: Patch Available (was: Open) make refresh-namodenodes.sh refreshing all namenodes

[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-tabpanelfocusedCommentId=13044129#comment-13044129 ] Todd Lipcon commented on HDFS-2003: --- h3. Test stup I ran performance tests with an

[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-tabpanelfocusedCommentId=13044133#comment-13044133 ] Todd Lipcon commented on HDFS-2003: --- BTW, I thought of another reason why EOFException

[jira] [Updated] (HDFS-1875) MiniDFSCluster hard-codes dfs.datanode.address to localhost

[ https://issues.apache.org/jira/browse/HDFS-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated HDFS-1875: - Attachment: HDFS-1875.patch Updated after review comments. MiniDFSCluster hard-codes

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

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

[jira] [Commented] (HDFS-1875) MiniDFSCluster hard-codes dfs.datanode.address to localhost

[ https://issues.apache.org/jira/browse/HDFS-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044154#comment-13044154 ] Eric Payne commented on HDFS-1875: -- Thanks for your review, Matt. I have submitted a new

[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: --- Status: Patch Available (was: Open) Does libhdfs really need to depend on AC_TYPE_INT16_T,

[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.patch.txt This trivial patch bites the bullet and removes the

[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-tabpanelfocusedCommentId=13044163#comment-13044163 ] Allen Wittenauer commented on HDFS-1619: Shouldn't we test for c99 then? In the

[jira] [Commented] (HDFS-1875) MiniDFSCluster hard-codes dfs.datanode.address to localhost

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

[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-tabpanelfocusedCommentId=13044169#comment-13044169 ] Roman Shaposhnik commented on HDFS-1619: That's a pretty good idea. We can add

[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-tabpanelfocusedCommentId=13044173#comment-13044173 ] Hadoop QA commented on HDFS-1619: - -1 overall. Here are the results of testing the latest

[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-tabpanelfocusedCommentId=13044175#comment-13044175 ] Eli Collins commented on HDFS-1619: --- We don't need to set AC_PROG_CC_C99 because we don'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-tabpanelfocusedCommentId=13044176#comment-13044176 ] Eli Collins commented on HDFS-1619: --- Also note that fuse-dfs is AC_PREREQ(2.52), no

[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-tabpanelfocusedCommentId=13044177#comment-13044177 ] Roman Shaposhnik commented on HDFS-1619: ||| Also note that fuse-dfs is

[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-tabpanelfocusedCommentId=13044179#comment-13044179 ] Eli Collins commented on HDFS-1619: --- bq. I don't think I follow your logic here.

[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-tabpanelfocusedCommentId=13044181#comment-13044181 ] Eli Collins commented on HDFS-1619: --- bq. The idea behind AC_PROG_CC_C99 is to try and ask

[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-tabpanelfocusedCommentId=13044182#comment-13044182 ] Roman Shaposhnik commented on HDFS-1619: ||| Not exactly, stdint is a header that

[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-tabpanelfocusedCommentId=13044188#comment-13044188 ] Allen Wittenauer commented on HDFS-1619: IIRC, using // is a comment for C code 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: Attachment: 1948-v4.22.txt Here is a version for branch 0.22. Two minor changes only -- the rpc version and how

[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-tabpanelfocusedCommentId=13044195#comment-13044195 ] stack commented on HDFS-1948: - I've been testing w/ this 0.22 patch and the lease grabbing

[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-tabpanelfocusedCommentId=13044196#comment-13044196 ] Hadoop QA commented on HDFS-1948: - -1 overall. Here are the results of testing the latest

[jira] [Created] (HDFS-2033) JIRA to redesign client side read path

JIRA to redesign client side read path -- Key: HDFS-2033 URL: https://issues.apache.org/jira/browse/HDFS-2033 Project: Hadoop HDFS Issue Type: Bug Reporter: John George Assignee:

[jira] [Created] (HDFS-2034) reading from currently being written block does not work

reading from currently being written block does not work - Key: HDFS-2034 URL: https://issues.apache.org/jira/browse/HDFS-2034 Project: Hadoop HDFS Issue Type: Bug

  1   2   >