[jira] [Updated] (HDFS-15079) RBF: Client maybe get an unexpected result with network anomaly

[ https://issues.apache.org/jira/browse/HDFS-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-15079: --- Parent: HDFS-14603 Issue Type: Sub-task (was: Bug) > RBF: Client maybe get an unexpected res

[jira] [Commented] (HDFS-14740) Recover data blocks from persistent memory read cache during datanode restarts

[ https://issues.apache.org/jira/browse/HDFS-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003132#comment-17003132 ] Feilong He commented on HDFS-14740: --- [^HDFS-14740.009.patch], [^HDFS-14740-branch-3.1-0

[jira] [Commented] (HDFS-15054) Delete Snapshot not updating new modification time

[ https://issues.apache.org/jira/browse/HDFS-15054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003130#comment-17003130 ] Hudson commented on HDFS-15054: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #

[jira] [Commented] (HDFS-14993) checkDiskError doesn't work during datanode startup

[ https://issues.apache.org/jira/browse/HDFS-14993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003125#comment-17003125 ] Ayush Saxena commented on HDFS-14993: - Build results aren't available now. I have ret

[jira] [Updated] (HDFS-15054) Delete Snapshot not updating new modification time

[ https://issues.apache.org/jira/browse/HDFS-15054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15054: Fix Version/s: 3.3.0 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolve

[jira] [Commented] (HDFS-15054) Delete Snapshot not updating new modification time

[ https://issues.apache.org/jira/browse/HDFS-15054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003119#comment-17003119 ] Ayush Saxena commented on HDFS-15054: - v002 LGTM +1 > Delete Snapshot not updating n

[jira] [Commented] (HDFS-15003) RBF: Make Router support storage type quota.

[ https://issues.apache.org/jira/browse/HDFS-15003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003112#comment-17003112 ] Ayush Saxena commented on HDFS-15003: - Thanx [~LiJinglun] for the update. I suppose i

[jira] [Commented] (HDFS-15080) Fix the issue in reading persistent memory cache with an offset

[ https://issues.apache.org/jira/browse/HDFS-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003109#comment-17003109 ] Hadoop QA commented on HDFS-15080: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Commented] (HDFS-12999) When reach the end of the block group, it may not need to flush all the data packets(flushAllInternals) twice.

[ https://issues.apache.org/jira/browse/HDFS-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003094#comment-17003094 ] Hudson commented on HDFS-12999: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #

[jira] [Updated] (HDFS-12999) When reach the end of the block group, it may not need to flush all the data packets(flushAllInternals) twice.

[ https://issues.apache.org/jira/browse/HDFS-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-12999: Fix Version/s: 3.3.0 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolve

[jira] [Commented] (HDFS-12999) When reach the end of the block group, it may not need to flush all the data packets(flushAllInternals) twice.

[ https://issues.apache.org/jira/browse/HDFS-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003081#comment-17003081 ] Ayush Saxena commented on HDFS-12999: - Thanx [~ferhui] for the help. v003 LGTM +1 >

[jira] [Updated] (HDFS-15080) Fix the issue in reading persistent memory cache with an offset

[ https://issues.apache.org/jira/browse/HDFS-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feilong He updated HDFS-15080: -- Fix Version/s: 3.2.2 3.1.4 3.3.0 > Fix the issue in reading persi

[jira] [Updated] (HDFS-15080) Fix the issue in reading persistent memory cache with an offset

[ https://issues.apache.org/jira/browse/HDFS-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feilong He updated HDFS-15080: -- Description: Some applications can read a segment of pmem cache with an offset specified. The previous

[jira] [Updated] (HDFS-15080) Fix the issue in reading persistent memory cache with an offset

[ https://issues.apache.org/jira/browse/HDFS-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feilong He updated HDFS-15080: -- Description: Some applications can read a segment of pmem cache with an offset specified. The previous

[jira] [Updated] (HDFS-15080) Fix the issue in reading persistent memory cache with an offset

[ https://issues.apache.org/jira/browse/HDFS-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feilong He updated HDFS-15080: -- Attachment: HDFS-15080-000.patch Status: Patch Available (was: Open) > Fix the issue in readin

[jira] [Created] (HDFS-15080) Fix the issue in reading persistent memory cache with an offset

Feilong He created HDFS-15080: - Summary: Fix the issue in reading persistent memory cache with an offset Key: HDFS-15080 URL: https://issues.apache.org/jira/browse/HDFS-15080 Project: Hadoop HDFS

[jira] [Resolved] (HDFS-15073) Replace curator-shaded guava import with the standard one

[ https://issues.apache.org/jira/browse/HDFS-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HDFS-15073. -- Resolution: Fixed > Replace curator-shaded guava import with the standard one > ---

[jira] [Updated] (HDFS-15073) Replace curator-shaded guava import with the standard one

[ https://issues.apache.org/jira/browse/HDFS-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HDFS-15073: - Fix Version/s: 3.2.2 3.1.4 3.3.0 Hadoop Flags: Reviewed

[jira] [Commented] (HDFS-15073) Replace curator-shaded guava import with the standard one

[ https://issues.apache.org/jira/browse/HDFS-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003048#comment-17003048 ] Akira Ajisaka commented on HDFS-15073: -- Merged the PR into trunk, branch-3.2, and br

[jira] [Commented] (HDFS-15073) Replace curator-shaded guava import with the standard one

[ https://issues.apache.org/jira/browse/HDFS-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003043#comment-17003043 ] Hudson commented on HDFS-15073: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #

[jira] [Updated] (HDFS-15073) Replace curator-shaded guava import with the standard one

[ https://issues.apache.org/jira/browse/HDFS-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HDFS-15073: - Summary: Replace curator-shaded guava import with the standard one (was: Remove the usage of cur

[jira] [Work started] (HDFS-15073) Remove the usage of curator-shaded guava in SnapshotDiffReportListing.java

[ https://issues.apache.org/jira/browse/HDFS-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-15073 started by Chandra Sanivarapu. - > Remove the usage of curator-shaded guava in SnapshotDiffReportListin

[jira] [Commented] (HDFS-15076) Fix tests that hold FSDirectory lock, without holding FSNamesystem lock.

[ https://issues.apache.org/jira/browse/HDFS-15076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002994#comment-17002994 ] Hudson commented on HDFS-15076: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #

[jira] [Updated] (HDFS-15076) Fix tests that hold FSDirectory lock, without holding FSNamesystem lock.

[ https://issues.apache.org/jira/browse/HDFS-15076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-15076: --- Fix Version/s: 2.10.1 3.2.2 3.1.4

[jira] [Commented] (HDFS-15063) HttpFS : getFileStatus doesn't return ecPolicy

[ https://issues.apache.org/jira/browse/HDFS-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002918#comment-17002918 ] hemanthboyina commented on HDFS-15063: -- thanks for the review [~tasanuma]  {quote}Wh

[jira] [Commented] (HDFS-14740) Recover data blocks from persistent memory read cache during datanode restarts

[ https://issues.apache.org/jira/browse/HDFS-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002793#comment-17002793 ] Hadoop QA commented on HDFS-14740: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Commented] (HDFS-14740) Recover data blocks from persistent memory read cache during datanode restarts

[ https://issues.apache.org/jira/browse/HDFS-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002792#comment-17002792 ] Hadoop QA commented on HDFS-14740: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Commented] (HDFS-14740) Recover data blocks from persistent memory read cache during datanode restarts

[ https://issues.apache.org/jira/browse/HDFS-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002777#comment-17002777 ] Hadoop QA commented on HDFS-14740: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Comment Edited] (HDFS-15078) RBF: Should check connection channel before sending rpc to namenode

[ https://issues.apache.org/jira/browse/HDFS-15078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002739#comment-17002739 ] Fei Hui edited comment on HDFS-15078 at 12/24/19 10:23 AM: --- {qu

[jira] [Comment Edited] (HDFS-15078) RBF: Should check connection channel before sending rpc to namenode

[ https://issues.apache.org/jira/browse/HDFS-15078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002739#comment-17002739 ] Fei Hui edited comment on HDFS-15078 at 12/24/19 10:02 AM: --- {qu

[jira] [Commented] (HDFS-15079) RBF: Client maybe get an unexpected result with network anomaly

[ https://issues.apache.org/jira/browse/HDFS-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002762#comment-17002762 ] Fei Hui commented on HDFS-15079: General Idea: * client generate id and send it with call

[jira] [Commented] (HDFS-12999) When reach the end of the block group, it may not need to flush all the data packets(flushAllInternals) twice.

[ https://issues.apache.org/jira/browse/HDFS-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002760#comment-17002760 ] Hadoop QA commented on HDFS-12999: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Commented] (HDFS-15063) HttpFS : getFileStatus doesn't return ecPolicy

[ https://issues.apache.org/jira/browse/HDFS-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002752#comment-17002752 ] Takanobu Asanuma commented on HDFS-15063: - Thanks for working on this, [~hemanthb

[jira] [Updated] (HDFS-15079) RBF: Client maybe get an unexpected result with network anomaly

[ https://issues.apache.org/jira/browse/HDFS-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fei Hui updated HDFS-15079: --- Summary: RBF: Client maybe get an unexpected result with network anomaly (was: RBF: Client may get an unexp

[jira] [Commented] (HDFS-15078) RBF: Should check connection channel before sending rpc to namenode

[ https://issues.apache.org/jira/browse/HDFS-15078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002739#comment-17002739 ] Fei Hui commented on HDFS-15078: {quote} The issue is the first router which c, That clie

[jira] [Commented] (HDFS-15078) RBF: Should check connection channel before sending rpc to namenode

[ https://issues.apache.org/jira/browse/HDFS-15078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002729#comment-17002729 ] Ayush Saxena commented on HDFS-15078: - {quote}And overwrite is true by default, this

[jira] [Commented] (HDFS-12999) When reach the end of the block group, it may not need to flush all the data packets(flushAllInternals) twice.

[ https://issues.apache.org/jira/browse/HDFS-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002720#comment-17002720 ] Fei Hui commented on HDFS-12999: Yes, [~figo] doesn't seems active nowdays. Upload v003 p

[jira] [Updated] (HDFS-12999) When reach the end of the block group, it may not need to flush all the data packets(flushAllInternals) twice.

[ https://issues.apache.org/jira/browse/HDFS-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fei Hui updated HDFS-12999: --- Attachment: HDFS-12999.003.patch > When reach the end of the block group, it may not need to flush all the da

[jira] [Updated] (HDFS-15079) RBF: Client may get an unexpected result with network anomaly

[ https://issues.apache.org/jira/browse/HDFS-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fei Hui updated HDFS-15079: --- Issue Type: Bug (was: Improvement) > RBF: Client may get an unexpected result with network anomaly > --

[jira] [Created] (HDFS-15079) RBF: Client may get an unexpected result with network anomaly

Fei Hui created HDFS-15079: -- Summary: RBF: Client may get an unexpected result with network anomaly Key: HDFS-15079 URL: https://issues.apache.org/jira/browse/HDFS-15079 Project: Hadoop HDFS Issue