[jira] [Created] (HDFS-17347) EC: Limit recovery worker counts to prevent holding two many network connections.
farmmamba created HDFS-17347: Summary: EC: Limit recovery worker counts to prevent holding two many network connections. Key: HDFS-17347 URL: https://issues.apache.org/jira/browse/HDFS-17347 Project: Hadoop HDFS Issue Type: Improvement Reporter: farmmamba Assignee: farmmamba -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
Apache Hadoop qbt Report: branch-2.10+JDK7 on Linux/x86_64
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/ No changes -1 overall The following subsystems voted -1: asflicense hadolint mvnsite pathlen unit The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck whitespace The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: Failed junit tests : hadoop.ipc.TestIPC hadoop.fs.TestFileUtil hadoop.contrib.bkjournal.TestBookKeeperHACheckpoints hadoop.hdfs.TestLeaseRecovery2 hadoop.hdfs.server.blockmanagement.TestReplicationPolicyWithUpgradeDomain hadoop.hdfs.server.namenode.snapshot.TestSnapshotDeletion hadoop.hdfs.TestFileLengthOnClusterRestart hadoop.hdfs.server.namenode.ha.TestPipelinesFailover hadoop.hdfs.server.namenode.TestDecommissioningStatus hadoop.hdfs.TestDFSInotifyEventInputStream hadoop.hdfs.server.namenode.snapshot.TestSnapshotBlocksMap hadoop.hdfs.qjournal.server.TestJournalNodeRespectsBindHostKeys hadoop.fs.viewfs.TestViewFileSystemHdfs hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes hadoop.hdfs.server.federation.router.TestRouterQuota hadoop.hdfs.server.federation.router.TestRouterNamenodeHeartbeat hadoop.hdfs.server.federation.resolver.order.TestLocalResolver hadoop.hdfs.server.federation.resolver.TestMultipleDestinationResolver hadoop.contrib.bkjournal.TestBookKeeperHACheckpoints hadoop.mapreduce.lib.input.TestLineRecordReader hadoop.mapred.TestLineRecordReader hadoop.mapreduce.jobhistory.TestHistoryViewerPrinter hadoop.resourceestimator.service.TestResourceEstimatorService hadoop.resourceestimator.solver.impl.TestLpSolver hadoop.yarn.sls.appmaster.TestAMSimulator hadoop.yarn.sls.TestSLSRunner hadoop.yarn.server.nodemanager.containermanager.linux.resources.TestNumaResourceAllocator hadoop.yarn.server.nodemanager.containermanager.linux.resources.TestNumaResourceHandlerImpl hadoop.yarn.server.nodemanager.amrmproxy.TestFederationInterceptor hadoop.yarn.server.resourcemanager.TestClientRMService hadoop.yarn.server.resourcemanager.monitor.invariants.TestMetricsInvariantChecker cc: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/diff-compile-cc-root.txt [4.0K] javac: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/diff-compile-javac-root.txt [488K] checkstyle: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/diff-checkstyle-root.txt [14M] hadolint: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/diff-patch-hadolint.txt [4.0K] mvnsite: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/patch-mvnsite-root.txt [572K] pathlen: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/pathlen.txt [12K] pylint: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/diff-patch-pylint.txt [20K] shellcheck: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/diff-patch-shellcheck.txt [72K] whitespace: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/whitespace-eol.txt [12M] https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/whitespace-tabs.txt [1.3M] javadoc: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/patch-javadoc-root.txt [36K] unit: https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt [224K] https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt [1.8M] https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt [36K] https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs_src_contrib_bkjournal.txt [16K] https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-core.txt [104K] https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1279/artifact
[jira] [Created] (HDFS-17348) Enhance Log when checkLocations in RecoveryTaskStriped
farmmamba created HDFS-17348: Summary: Enhance Log when checkLocations in RecoveryTaskStriped Key: HDFS-17348 URL: https://issues.apache.org/jira/browse/HDFS-17348 Project: Hadoop HDFS Issue Type: Improvement Components: datanode Affects Versions: 3.4.0 Reporter: farmmamba Assignee: farmmamba Enhance IOE log to better debug. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
[jira] [Created] (HDFS-17349) evictWriters command does not seem to work effectively
Srinivasu Majeti created HDFS-17349:
---
Summary: evictWriters command does not seem to work effectively
Key: HDFS-17349
URL: https://issues.apache.org/jira/browse/HDFS-17349
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Srinivasu Majeti
Post running {{evictWriters}} on Datanodes while decommissioning going on,
noticed the below messages being logged. That means {{evictWriters is
successfully issued to Datanode and it tried interrupting all xceivers.}}
{code:java}
2023-11-29 16:37:18,599 INFO org.apache.hadoop.hdfs.server.datanode.DataNode:
Evicting all writers.
2023-11-29 16:37:18,600 INFO org.apache.hadoop.hdfs.server.datanode.DataNode:
Stopped the writer:
NioInetPeer(Socket[addr=/10.4.33.104,port=42982,localport=9866])
2023-11-29 16:37:18,600 INFO org.apache.hadoop.hdfs.server.datanode.DataNode:
Stopped the writer:
NioInetPeer(Socket[addr=/10.4.35.105,port=43300,localport=9866])
2023-11-29 16:37:18,600 INFO org.apache.hadoop.hdfs.server.datanode.DataNode:
Stopped the writer:
NioInetPeer(Socket[addr=/10.4.33.60,port=59978,localport=9866]){code}
Even after we see "Stopped the writer: NioInetPeer(Socket[addr=/10.4.35.105",
we still see open files not released from 10.4.35.105, and decommission did not
progress.
{code:java}
$ hdfs dfsadmin -listOpenFiles -blockingDecommission -path=/
Client Host Client Name Open File Path
10.4.35.105 DFSClient_NONMAPREDUCE_-211169064_96
/warehouse/tablespace/managed/hive/sys.db/query_data/date=2023-11-28/hive_3162c2fd-cdd0-47f4-979c-d1c3263bfc86_1
10.4.35.149 DFSClient_NONMAPREDUCE_1084942995_59
/warehouse/tablespace/managed/hive/sys.db/query_data/date=2023-11-28/hive_2360faef-7894-41d9-a13c-57d70593583e_1{code}
We may need to either report if evictWriters successfully executed or failed by
checking for the actual status of xceivers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
Re: [INFO] Hadoop-3.4 Release Update
Thanks for driving this. One query: Does all the jiras from 3.3 are part of the 3.4? On Mon, 22 Jan 2024 at 11:50 AM, slfan1989 wrote: > Thank you very much for specifying the frozen time for the > Branch-3.4.0. @Xiaoqiao > He > > If there is a need to backport any PRs to branch-3.4/branch-3.4.0, please > feel free to contact me. > > Best Regards, > Shilun Fan. > > On Mon, Jan 22, 2024 at 1:58 PM Xiaoqiao He wrote: > > > Hi All, > > > > Branch-3.4.0 will be frozen this Thursday (UTC 00:00 Jan 25, 2024). > > If there is any blocker/critical PR please backport to branch-3.4 and > > branch-3.4.0 or sync to me or hadoop-3.4.0 RM Shilun Fan. > > > > If any reported issues are not ready in time please wait for the next > > release. > > > > Thanks all. > > > > Best Regards, > > - He Xiaoqiao > > > > > > > > On Mon, Jan 22, 2024 at 10:43 AM slfan1989 wrote: > > > >> Thank you for the feedback! > >> > >> I apologize for updating partial information in the Hadoop module. > >> > >> Today, I will complete the rollback of the modified JIRA and add back > the > >> 3.4.0 version. > >> > >> Best > >> > >> On Mon, Jan 22, 2024 at 10:38 AM Xiaoqiao He > >> wrote: > >> > >>> Thanks all for your input. Connected to Shilun offline yesterday, and > he > >>> will > >>> update or recover the fix version tag before 3.4.0-RC1. > >>> > >>> Best Regards, > >>> - He Xiaoqiao > >>> > >>> > >>> On Mon, Jan 22, 2024 at 9:53 AM Masatake Iwasaki > > >>> wrote: > >>> > >>> > > As I mentioned in my comment on HADOOP-18045, I think 3.4.0 should > >>> still > >>> > be > >>> > > included in the Fix versions, > >>> > > even if it was already released in 3.3.x. If I understand > correctly, > >>> this > >>> > > is usually our practice. > >>> > > >>> > +1. > >>> > We can not assume 3.4.x contains all fixes of 3.3.y since we are > >>> > maintaining both branch-3.4 and branch-3.3. > >>> > > >>> > On Sun, Jan 21, 2024 at 2:45 PM Takanobu Asanuma < > tasan...@apache.org> > >>> > wrote: > >>> > > > >>> > > Hi Shilun, > >>> > > > >>> > > Thank you for leading the 3.4.0 release. > >>> > > > >>> > > > 2. In JIRA issues where other release versions have been > released, > >>> > remove > >>> > > > the 3.4.0 entry from the fix version. > >>> > > > >>> > > As I mentioned in my comment on HADOOP-18045, I think 3.4.0 should > >>> still > >>> > be > >>> > > included in the Fix versions, > >>> > > even if it was already released in 3.3.x. If I understand > correctly, > >>> this > >>> > > is usually our practice. > >>> > > > >>> > > Thanks, > >>> > > - Takanobu > >>> > > > >>> > > 2024年1月21日(日) 13:56 slfan1989 : > >>> > > > >>> > > > Hi All, > >>> > > > > >>> > > > I am currently preparing to release hadoop-3.4.0-RC1 and need to > >>> > perform > >>> > > > some operations on the JIRA issues related to HADOOP, HDFS, YARN, > >>> and > >>> > > > MAPREDUCE. Specifically, the tasks include: > >>> > > > > >>> > > > 1. For JIRA issues with target version set to 3.4.0 and marked as > >>> > > > non-blocker, update the target version to 3.5.0. > >>> > > > > >>> > > > 2. In JIRA issues where other release versions have been > released, > >>> > remove > >>> > > > the 3.4.0 entry from the fix version. > >>> > > > > >>> > > > 3. For JIRA issues with target version set to 3.4.0, fix version > >>> set to > >>> > > > 3.4.0, and status set to > >>> > > > RESOLVED, if Affects Version/s, Component/s, and Hadoop Flags are > >>> not > >>> > set, > >>> > > > complete the information. > >>> > > > > >>> > > > Best Regards, > >>> > > > - Shilun Fan. > >>> > > > > >>> > > > On Fri, Jan 19, 2024 at 3:23 PM Xiaoqiao He > > >>> > wrote: > >>> > > > > >>> > > > > Hi All, > >>> > > > > > >>> > > > > Branch trunk has been set to 3.5.0-SNAPSHOT and branch-3.4 is > >>> > created[1]. > >>> > > > > > >>> > > > > Please set the proper fix version while committing jira, 3.5.0 > >>> should > >>> > > > > be priority. If there is any blocker/critical please also > >>> backport to > >>> > > > > branch-3.4 or sync to me or RM Shilun Fan. > >>> > > > > > >>> > > > > Shilun will start 3.4.0 RC1 voting in the next few days. > >>> > > > > > >>> > > > > Thanks. > >>> > > > > > >>> > > > > Best Regards, > >>> > > > > - He Xiaoqiao > >>> > > > > > >>> > > > > [1] https://github.com/apache/hadoop/commits/branch-3.4 > >>> > > > > > >>> > > > > >>> > > >>> > - > >>> > To unsubscribe, e-mail: private-unsubscr...@hadoop.apache.org > >>> > For additional commands, e-mail: private-h...@hadoop.apache.org > >>> > > >>> > > >>> > >> >
Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86_64
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/ [Jan 21, 2024, 7:00:34 PM] (github) HADOOP-19046. S3A: update AWS V2 SDK to 2.23.5; v1 to 1.12.599 (#6467) [Jan 21, 2024, 7:14:54 PM] (github) HADOOP-18883. [ABFS]: Expect-100 JDK bug resolution: prevent multiple server calls (#6022) -1 overall The following subsystems voted -1: blanks hadolint pathlen xml The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: XML : Parsing Error(s): hadoop-common-project/hadoop-common/src/test/resources/xml/external-dtd.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-excerpt.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-missing-tags.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-missing-tags2.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-sample-output.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/fair-scheduler-invalid.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/yarn-site-with-invalid-allocation-file-ref.xml cc: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/results-compile-cc-root.txt [96K] javac: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/results-compile-javac-root.txt [12K] blanks: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/blanks-eol.txt [15M] https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/blanks-tabs.txt [2.0M] checkstyle: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/results-checkstyle-root.txt [13M] hadolint: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/results-hadolint.txt [24K] pathlen: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/results-pathlen.txt [16K] pylint: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/results-pylint.txt [20K] shellcheck: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/results-shellcheck.txt [24K] xml: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/xml.txt [24K] javadoc: https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1479/artifact/out/results-javadoc-javadoc-root.txt [244K] Powered by Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
[jira] [Created] (HDFS-17350) update AWS SDK to support S3 Access Grants in S3A
Jason Han created HDFS-17350: Summary: update AWS SDK to support S3 Access Grants in S3A Key: HDFS-17350 URL: https://issues.apache.org/jira/browse/HDFS-17350 Project: Hadoop HDFS Issue Type: Improvement Components: fs/s3 Affects Versions: 3.3.6 Reporter: Jason Han Fix For: 3.3.6 In order to support S3 Access Grants(https://aws.amazon.com/s3/features/access-grants/) in S3A, we need to update AWS SDK in hadooop package. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
[jira] [Created] (HDFS-17351) Add S3 Access Grants Support in S3A
Jason Han created HDFS-17351: Summary: Add S3 Access Grants Support in S3A Key: HDFS-17351 URL: https://issues.apache.org/jira/browse/HDFS-17351 Project: Hadoop HDFS Issue Type: New Feature Components: fs/s3 Reporter: Jason Han Add support for S3 Access Grants (https://aws.amazon.com/s3/features/access-grants/) in S3A. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
Re: [INFO] Hadoop-3.4 Release Update
branch-3.4/branch-3.4.0 was created from the trunk branch, including the changes from branch-3.3. Best Regards, Shilun Fan. On Tue, Jan 23, 2024 at 12:58 AM Brahma Reddy Battula wrote: > Thanks for driving this. > > One query: > Does all the jiras from 3.3 are part of the 3.4? > > > > > On Mon, 22 Jan 2024 at 11:50 AM, slfan1989 wrote: > >> Thank you very much for specifying the frozen time for the >> Branch-3.4.0. @Xiaoqiao >> He >> >> If there is a need to backport any PRs to branch-3.4/branch-3.4.0, please >> feel free to contact me. >> >> Best Regards, >> Shilun Fan. >> >> On Mon, Jan 22, 2024 at 1:58 PM Xiaoqiao He >> wrote: >> >> > Hi All, >> > >> > Branch-3.4.0 will be frozen this Thursday (UTC 00:00 Jan 25, 2024). >> > If there is any blocker/critical PR please backport to branch-3.4 and >> > branch-3.4.0 or sync to me or hadoop-3.4.0 RM Shilun Fan. >> > >> > If any reported issues are not ready in time please wait for the next >> > release. >> > >> > Thanks all. >> > >> > Best Regards, >> > - He Xiaoqiao >> > >> > >> > >> > On Mon, Jan 22, 2024 at 10:43 AM slfan1989 >> wrote: >> > >> >> Thank you for the feedback! >> >> >> >> I apologize for updating partial information in the Hadoop module. >> >> >> >> Today, I will complete the rollback of the modified JIRA and add back >> the >> >> 3.4.0 version. >> >> >> >> Best >> >> >> >> On Mon, Jan 22, 2024 at 10:38 AM Xiaoqiao He >> >> wrote: >> >> >> >>> Thanks all for your input. Connected to Shilun offline yesterday, and >> he >> >>> will >> >>> update or recover the fix version tag before 3.4.0-RC1. >> >>> >> >>> Best Regards, >> >>> - He Xiaoqiao >> >>> >> >>> >> >>> On Mon, Jan 22, 2024 at 9:53 AM Masatake Iwasaki < >> iwasak...@apache.org> >> >>> wrote: >> >>> >> >>> > > As I mentioned in my comment on HADOOP-18045, I think 3.4.0 should >> >>> still >> >>> > be >> >>> > > included in the Fix versions, >> >>> > > even if it was already released in 3.3.x. If I understand >> correctly, >> >>> this >> >>> > > is usually our practice. >> >>> > >> >>> > +1. >> >>> > We can not assume 3.4.x contains all fixes of 3.3.y since we are >> >>> > maintaining both branch-3.4 and branch-3.3. >> >>> > >> >>> > On Sun, Jan 21, 2024 at 2:45 PM Takanobu Asanuma < >> tasan...@apache.org> >> >>> > wrote: >> >>> > > >> >>> > > Hi Shilun, >> >>> > > >> >>> > > Thank you for leading the 3.4.0 release. >> >>> > > >> >>> > > > 2. In JIRA issues where other release versions have been >> released, >> >>> > remove >> >>> > > > the 3.4.0 entry from the fix version. >> >>> > > >> >>> > > As I mentioned in my comment on HADOOP-18045, I think 3.4.0 should >> >>> still >> >>> > be >> >>> > > included in the Fix versions, >> >>> > > even if it was already released in 3.3.x. If I understand >> correctly, >> >>> this >> >>> > > is usually our practice. >> >>> > > >> >>> > > Thanks, >> >>> > > - Takanobu >> >>> > > >> >>> > > 2024年1月21日(日) 13:56 slfan1989 : >> >>> > > >> >>> > > > Hi All, >> >>> > > > >> >>> > > > I am currently preparing to release hadoop-3.4.0-RC1 and need to >> >>> > perform >> >>> > > > some operations on the JIRA issues related to HADOOP, HDFS, >> YARN, >> >>> and >> >>> > > > MAPREDUCE. Specifically, the tasks include: >> >>> > > > >> >>> > > > 1. For JIRA issues with target version set to 3.4.0 and marked >> as >> >>> > > > non-blocker, update the target version to 3.5.0. >> >>> > > > >> >>> > > > 2. In JIRA issues where other release versions have been >> released, >> >>> > remove >> >>> > > > the 3.4.0 entry from the fix version. >> >>> > > > >> >>> > > > 3. For JIRA issues with target version set to 3.4.0, fix version >> >>> set to >> >>> > > > 3.4.0, and status set to >> >>> > > > RESOLVED, if Affects Version/s, Component/s, and Hadoop Flags >> are >> >>> not >> >>> > set, >> >>> > > > complete the information. >> >>> > > > >> >>> > > > Best Regards, >> >>> > > > - Shilun Fan. >> >>> > > > >> >>> > > > On Fri, Jan 19, 2024 at 3:23 PM Xiaoqiao He < >> xq.he2...@gmail.com> >> >>> > wrote: >> >>> > > > >> >>> > > > > Hi All, >> >>> > > > > >> >>> > > > > Branch trunk has been set to 3.5.0-SNAPSHOT and branch-3.4 is >> >>> > created[1]. >> >>> > > > > >> >>> > > > > Please set the proper fix version while committing jira, 3.5.0 >> >>> should >> >>> > > > > be priority. If there is any blocker/critical please also >> >>> backport to >> >>> > > > > branch-3.4 or sync to me or RM Shilun Fan. >> >>> > > > > >> >>> > > > > Shilun will start 3.4.0 RC1 voting in the next few days. >> >>> > > > > >> >>> > > > > Thanks. >> >>> > > > > >> >>> > > > > Best Regards, >> >>> > > > > - He Xiaoqiao >> >>> > > > > >> >>> > > > > [1] https://github.com/apache/hadoop/commits/branch-3.4 >> >>> > > > > >> >>> > > > >> >>> > >> >>> > >> - >> >>> > To unsubscribe, e-mail: private-unsubscr...@hadoop.apache.org >> >>> > For additional commands, e-mail: private-h...@hadoop.apache.org >> >>> > >> >>> > >> >>> >>
[jira] [Created] (HDFS-17352) Add configuration to control whether DN delete this replica from disk when client requests a missing block
Haiyang Hu created HDFS-17352: - Summary: Add configuration to control whether DN delete this replica from disk when client requests a missing block Key: HDFS-17352 URL: https://issues.apache.org/jira/browse/HDFS-17352 Project: Hadoop HDFS Issue Type: Improvement Components: datanode Reporter: Haiyang Hu Assignee: Haiyang Hu -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
