[jira] [Commented] (HDFS-16756) RBF proxies the client's user by the login user to enable CacheEntry

[ https://issues.apache.org/jira/browse/HDFS-16756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600567#comment-17600567 ] ASF GitHub Bot commented on HDFS-16756: --- hadoop-yetus commented on PR #4853: URL:

[jira] [Commented] (HDFS-2139) Fast copy for HDFS.

[ https://issues.apache.org/jira/browse/HDFS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600565#comment-17600565 ] Hui Fei commented on HDFS-2139: --- [~xuzq_zander] cut a feature branch HDFS-2139 from trunk. can start your

[jira] [Commented] (HDFS-16737) Fix number of threads in FsDatasetAsyncDiskService#addExecutorForVolume

[ https://issues.apache.org/jira/browse/HDFS-16737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600562#comment-17600562 ] ASF GitHub Bot commented on HDFS-16737: --- ZanderXu commented on PR #4784: URL:

[jira] [Commented] (HDFS-16703) Enable RPC Timeout for some protocols of NameNode.

[ https://issues.apache.org/jira/browse/HDFS-16703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600560#comment-17600560 ] ASF GitHub Bot commented on HDFS-16703: --- ZanderXu commented on PR #4660: URL:

[jira] [Commented] (HDFS-16697) Randomly setting “dfs.namenode.resource.checked.volumes.minimum” will always prevent safe mode from being turned off

[ https://issues.apache.org/jira/browse/HDFS-16697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600517#comment-17600517 ] ASF GitHub Bot commented on HDFS-16697: --- hadoop-yetus commented on PR #4849: URL:

[jira] [Commented] (HDFS-16756) RBF proxies the client's user by the login user to enable CacheEntry

[ https://issues.apache.org/jira/browse/HDFS-16756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600495#comment-17600495 ] ASF GitHub Bot commented on HDFS-16756: --- hadoop-yetus commented on PR #4853: URL:

[jira] [Commented] (HDFS-16697) Randomly setting “dfs.namenode.resource.checked.volumes.minimum” will always prevent safe mode from being turned off

[ https://issues.apache.org/jira/browse/HDFS-16697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600445#comment-17600445 ] ASF GitHub Bot commented on HDFS-16697: --- Likkey commented on PR #4849: URL:

[jira] [Commented] (HDFS-16721) Improve the check code of the important configuration item “dfs.client.socket-timeout”.

[ https://issues.apache.org/jira/browse/HDFS-16721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600442#comment-17600442 ] ASF GitHub Bot commented on HDFS-16721: --- Likkey commented on PR #4847: URL:

[jira] [Commented] (HDFS-16653) Safe mode related operations cannot be performed when “dfs.client.mmap.cache.size” is set to a negative number

[ https://issues.apache.org/jira/browse/HDFS-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600439#comment-17600439 ] ASF GitHub Bot commented on HDFS-16653: --- Likkey commented on PR #4848: URL:

[jira] [Commented] (HDFS-16748) RBF: DFSClient should uniquely identify writing files by namespace id and iNodeId

[ https://issues.apache.org/jira/browse/HDFS-16748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600393#comment-17600393 ] ASF GitHub Bot commented on HDFS-16748: --- ZanderXu commented on PR #4813: URL:

[jira] [Updated] (HDFS-16756) RBF proxies the client's user by the login user to enable CacheEntry

[ https://issues.apache.org/jira/browse/HDFS-16756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDFS-16756: -- Labels: pull-request-available (was: ) > RBF proxies the client's user by the login user to

[jira] [Commented] (HDFS-16756) RBF proxies the client's user by the login user to enable CacheEntry

[ https://issues.apache.org/jira/browse/HDFS-16756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600388#comment-17600388 ] ASF GitHub Bot commented on HDFS-16756: --- ZanderXu opened a new pull request, #4853: URL:

[jira] [Created] (HDFS-16756) RBF proxies the client's user by the login user to enable CacheEntry

ZanderXu created HDFS-16756: --- Summary: RBF proxies the client's user by the login user to enable CacheEntry Key: HDFS-16756 URL: https://issues.apache.org/jira/browse/HDFS-16756 Project: Hadoop HDFS

[jira] [Updated] (HDFS-16748) RBF: DFSClient should uniquely identify writing files by namespace id and iNodeId

[ https://issues.apache.org/jira/browse/HDFS-16748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-16748: Summary: RBF: DFSClient should uniquely identify writing files by namespace id and iNodeId (was:

[jira] [Commented] (HDFS-16748) RBF: DFSClient should uniquely identify writing files by namespace id and iNodeId

[ https://issues.apache.org/jira/browse/HDFS-16748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600365#comment-17600365 ] Ayush Saxena commented on HDFS-16748: - Committed to trunk. Thanx [~xuzq_zander] for the

[jira] [Resolved] (HDFS-16748) RBF: DFSClient should uniquely identify writing files by namespace id and iNodeId

[ https://issues.apache.org/jira/browse/HDFS-16748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved HDFS-16748. - Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed > RBF: DFSClient

[jira] [Commented] (HDFS-16748) DFSClient should uniquely identify writing files by namespace id and iNodeId

[ https://issues.apache.org/jira/browse/HDFS-16748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600364#comment-17600364 ] ASF GitHub Bot commented on HDFS-16748: --- ayushtkn merged PR #4813: URL:

[jira] [Resolved] (HDFS-16593) Correct inaccurate BlocksRemoved metric on DataNode side

[ https://issues.apache.org/jira/browse/HDFS-16593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16593. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk. >

[jira] [Commented] (HDFS-16593) Correct inaccurate BlocksRemoved metric on DataNode side

[ https://issues.apache.org/jira/browse/HDFS-16593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600338#comment-17600338 ] ASF GitHub Bot commented on HDFS-16593: --- Hexiaoqiao commented on PR #4353: URL:

[jira] [Commented] (HDFS-16593) Correct inaccurate BlocksRemoved metric on DataNode side

[ https://issues.apache.org/jira/browse/HDFS-16593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600337#comment-17600337 ] ASF GitHub Bot commented on HDFS-16593: --- Hexiaoqiao merged PR #4353: URL:

[jira] [Resolved] (HDFS-16752) 2.7.2 Rolling Upgrade 3.3.4 Datanode cannot be Degraded due to version Inconsistency

[ https://issues.apache.org/jira/browse/HDFS-16752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yuyanlei resolved HDFS-16752. - Resolution: Fixed > 2.7.2 Rolling Upgrade 3.3.4 Datanode cannot be Degraded due to version >

[jira] [Commented] (HDFS-16752) 2.7.2 Rolling Upgrade 3.3.4 Datanode cannot be Degraded due to version Inconsistency

[ https://issues.apache.org/jira/browse/HDFS-16752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600278#comment-17600278 ] yuyanlei commented on HDFS-16752: - after rollback https://issues.apache.org/jira/browse/HDFS-8791，Can