Re: Hadoop 3.1.0 release discussion
What's the status on resource profiles? I believe there are still a couple of open JIRAs to rethink some of the design choices. Daniel On 1/17/18 11:33 AM, Wangda Tan wrote: Hi All, Since we're fast approaching previously proposed feature freeze date (Jan 30, about 13 days from today). If you've any features which live in a branch and targeted to 3.1.0, please reply this email thread. Ideally, we should finish branch merging before feature freeze date. Here's an updated 3.1.0 feature status: 1. Merged & Completed features: * (Sunil) YARN-5881: Support absolute value in CapacityScheduler. * (Wangda) YARN-6223: GPU support on YARN. Features in trunk and works end-to-end. * (Jian) YARN-5079,YARN-4793,YARN-4757,YARN-6419 YARN native services. * (Steve Loughran): HADOOP-13786: S3Guard committer for zero-rename commits. * (Suma): YARN-7117: Capacity Scheduler: Support Auto Creation of Leaf Queues While Doing Queue Mapping. * (Chris Douglas) HDFS-9806: HDFS Tiered Storage. 2. Features close to finish: * (Zhankun) YARN-5983: FPGA support. Majority implementations completed and merged to trunk. Except for UI/documentation. * (Uma) HDFS-10285: HDFS SPS. Majority implementations are done, some discussions going on about implementation. * (Arun Suresh / Kostas / Wangda). YARN-6592: New SchedulingRequest and anti-affinity support. Close to finish, on track to be merged before Jan 30. 3. Tentative features: * (Arun Suresh). YARN-5972: Support pausing/freezing opportunistic containers. Only one pending patch. Plan to finish before Jan 7th. * (Haibo Chen). YARN-1011: Resource overcommitment. Looks challenging to be done before Jan 2018. * (Anu): HDFS-7240: Ozone. Given the discussion on HDFS-7240. Looks challenging to be done before Jan 2018. * (Varun V) YARN-5673: container-executor write. Given security refactoring of c-e (YARN-6623) is already landed, IMHO other stuff may be moved to 3.2. Thanks, Wangda On Fri, Dec 15, 2017 at 1:20 PM, Wangda Tan wrote: Hi all, Congratulations on the 3.0.0-GA release! As we discussed in the previous email thread [1], I'd like to restart 3.1.0 release plans. a) Quick summary: a.1 Release status We started 3.1 release discussion on Sep 6, 2017 [1]. As of today, there’re 232 patches loaded on 3.1.0 alone [2], besides 6 open blockers and 22 open critical issues. a.2 Release date update Considering delays of 3.0-GA release by month-and-a-half, I propose to move the dates as follows - feature freeze date from Dec 15, 2017, to Jan 30, 2018 - last date for any branches to get merged too; - code freeze (blockers & critical only) date to Feb 08, 2018; - release voting start by Feb 18, 2018, leaving time for at least two RCx - release date from Jan 15, 2018, to Feb 28, 2018; Unlike before, I added an additional milestone for release-vote-start so that we can account for voting time-period also. This overall is still 5 1/2 months of release-timeline unlike the faster cadence we hoped for, but this, in my opinion, is the best-updated timeline given the delays of the final release of 3.0-GA. b) Individual feature status: I spoke to several feature owners and checked the status of un-finished features, following are status of features planned to 3.1.0: b.1 Merged & Completed features: * (Sunil) YARN-5881: Support absolute value in CapacityScheduler. * (Wangda) YARN-6223: GPU support on YARN. Features in trunk and works end-to-end. * (Jian) YARN-5079,YARN-4793,YARN-4757,YARN-6419 YARN native services. * (Steve Loughran): HADOOP-13786: S3Guard committer for zero-rename commits. * (Suma): YARN-7117: Capacity Scheduler: Support Auto Creation of Leaf Queues While Doing Queue Mapping. b.2 Features close to finish: * (Chris Douglas) HDFS-9806: HDFS Tiered Storage. Being voting now. * (Zhankun) YARN-5983: FPGA support. Majority implementations completed and merged to trunk. Except for UI/documentation. * (Uma) HDFS-10285: HDFS SPS. Majority implementations are done, some discussions going on about implementation. b.3 Tentative features: * (Arun Suresh). YARN-5972: Support pausing/freezing opportunistic containers. Only one pending patch. Plan to finish before Jan 7th. * (Haibo Chen). YARN-1011: Resource overcommitment. Looks challenging to be done before Jan 2018. * (Arun Suresh / Kostas / Wangda). YARN-6592: New SchedulingRequest and anti-affinity support. Tentative will figure out by Jan 1st. * (Anu): HDFS-7240: Ozone. Given the discussion on HDFS-7240. Looks challenging to be done before Jan 2018. * (Varun V) YARN-5673: container-executor write. Given security refactoring of c-e (YARN-6623) is already landed, IMHO other stuff may be moved to 3.2. b.4 Additional release drivers * More exhaustive upgrade testing from 2.x to 3.x. c) Regarding branch cut: We will keep pointing trunk to 3.1 and cut branch-3.1 until: A. some feature planned to 3.2 has to be landed on trunk or B. After feature freeze date, whichever comes first. I've also talked offline with Vinod to get
Re: Hadoop 3.1.0 release discussion
HI Wangda, Thank you for the head-up mail. We are in the branch (HDFS-10285) and trying to push the tasks sooner before the deadline. Regards, Uma On 1/17/18, 11:35 AM, "Wangda Tan" wrote: Hi All, Since we're fast approaching previously proposed feature freeze date (Jan 30, about 13 days from today). If you've any features which live in a branch and targeted to 3.1.0, please reply this email thread. Ideally, we should finish branch merging before feature freeze date. Here's an updated 3.1.0 feature status: 1. Merged & Completed features: * (Sunil) YARN-5881: Support absolute value in CapacityScheduler. * (Wangda) YARN-6223: GPU support on YARN. Features in trunk and works end-to-end. * (Jian) YARN-5079,YARN-4793,YARN-4757,YARN-6419 YARN native services. * (Steve Loughran): HADOOP-13786: S3Guard committer for zero-rename commits. * (Suma): YARN-7117: Capacity Scheduler: Support Auto Creation of Leaf Queues While Doing Queue Mapping. * (Chris Douglas) HDFS-9806: HDFS Tiered Storage. 2. Features close to finish: * (Zhankun) YARN-5983: FPGA support. Majority implementations completed and merged to trunk. Except for UI/documentation. * (Uma) HDFS-10285: HDFS SPS. Majority implementations are done, some discussions going on about implementation. * (Arun Suresh / Kostas / Wangda). YARN-6592: New SchedulingRequest and anti-affinity support. Close to finish, on track to be merged before Jan 30. 3. Tentative features: * (Arun Suresh). YARN-5972: Support pausing/freezing opportunistic containers. Only one pending patch. Plan to finish before Jan 7th. * (Haibo Chen). YARN-1011: Resource overcommitment. Looks challenging to be done before Jan 2018. * (Anu): HDFS-7240: Ozone. Given the discussion on HDFS-7240. Looks challenging to be done before Jan 2018. * (Varun V) YARN-5673: container-executor write. Given security refactoring of c-e (YARN-6623) is already landed, IMHO other stuff may be moved to 3.2. Thanks, Wangda On Fri, Dec 15, 2017 at 1:20 PM, Wangda Tan wrote: > Hi all, > > Congratulations on the 3.0.0-GA release! > > As we discussed in the previous email thread [1], I'd like to restart > 3.1.0 release plans. > > a) Quick summary: > a.1 Release status > We started 3.1 release discussion on Sep 6, 2017 [1]. As of today, > there’re 232 patches loaded on 3.1.0 alone [2], besides 6 open blockers and > 22 open critical issues. > > a.2 Release date update > Considering delays of 3.0-GA release by month-and-a-half, I propose to > move the dates as follows > - feature freeze date from Dec 15, 2017, to Jan 30, 2018 - last date for > any branches to get merged too; > - code freeze (blockers & critical only) date to Feb 08, 2018; > - release voting start by Feb 18, 2018, leaving time for at least two RCx > - release date from Jan 15, 2018, to Feb 28, 2018; > > Unlike before, I added an additional milestone for release-vote-start so > that we can account for voting time-period also. > > This overall is still 5 1/2 months of release-timeline unlike the faster > cadence we hoped for, but this, in my opinion, is the best-updated timeline > given the delays of the final release of 3.0-GA. > > b) Individual feature status: > I spoke to several feature owners and checked the status of un-finished > features, following are status of features planned to 3.1.0: > > b.1 Merged & Completed features: > * (Sunil) YARN-5881: Support absolute value in CapacityScheduler. > * (Wangda) YARN-6223: GPU support on YARN. Features in trunk and works > end-to-end. > * (Jian) YARN-5079,YARN-4793,YARN-4757,YARN-6419 YARN native services. > * (Steve Loughran): HADOOP-13786: S3Guard committer for zero-rename > commits. > * (Suma): YARN-7117: Capacity Scheduler: Support Auto Creation of Leaf > Queues While Doing Queue Mapping. > > b.2 Features close to finish: > * (Chris Douglas) HDFS-9806: HDFS Tiered Storage. Being voting now. > * (Zhankun) YARN-5983: FPGA support. Majority implementations completed > and merged to trunk. Except for UI/documentation. > * (Uma) HDFS-10285: HDFS SPS. Majority implementations are done, some > discussions going on about implementation. > > b.3 Tentative features: > * (Arun Suresh). YARN-5972: Support pausing/freezing opportunistic > containers. Only one pending patch. Plan to finish before Jan 7th. > * (Haibo Chen). YARN-1011: Resource overcommitment. Looks challenging to > be done before Jan 2018. > * (Arun Suresh / Kostas / Wangda). YARN-6592: New SchedulingRequest and > anti-affinity support. Tentative will figure out by Jan 1st. > * (Anu): HDFS-7240: Ozone. Given the discussion on HDFS-
[jira] [Created] (HDFS-13029) /.reserved/raw/.reserved/.inodes/ is not resolvable.
Rushabh S Shah created HDFS-13029:
-
Summary: /.reserved/raw/.reserved/.inodes/ is not
resolvable.
Key: HDFS-13029
URL: https://issues.apache.org/jira/browse/HDFS-13029
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs
Environment: Namenode cannot resolve
{{/.reserved/raw/.reserved/.inodes/}} path.
Reporter: Rushabh S Shah
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
[jira] [Created] (HDFS-13028) RBF: Fix spurious TestRouterRpc#testProxyGetStats
Íñigo Goiri created HDFS-13028: -- Summary: RBF: Fix spurious TestRouterRpc#testProxyGetStats Key: HDFS-13028 URL: https://issues.apache.org/jira/browse/HDFS-13028 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Íñigo Goiri -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
Re: Hadoop 3.1.0 release discussion
Hi All, Since we're fast approaching previously proposed feature freeze date (Jan 30, about 13 days from today). If you've any features which live in a branch and targeted to 3.1.0, please reply this email thread. Ideally, we should finish branch merging before feature freeze date. Here's an updated 3.1.0 feature status: 1. Merged & Completed features: * (Sunil) YARN-5881: Support absolute value in CapacityScheduler. * (Wangda) YARN-6223: GPU support on YARN. Features in trunk and works end-to-end. * (Jian) YARN-5079,YARN-4793,YARN-4757,YARN-6419 YARN native services. * (Steve Loughran): HADOOP-13786: S3Guard committer for zero-rename commits. * (Suma): YARN-7117: Capacity Scheduler: Support Auto Creation of Leaf Queues While Doing Queue Mapping. * (Chris Douglas) HDFS-9806: HDFS Tiered Storage. 2. Features close to finish: * (Zhankun) YARN-5983: FPGA support. Majority implementations completed and merged to trunk. Except for UI/documentation. * (Uma) HDFS-10285: HDFS SPS. Majority implementations are done, some discussions going on about implementation. * (Arun Suresh / Kostas / Wangda). YARN-6592: New SchedulingRequest and anti-affinity support. Close to finish, on track to be merged before Jan 30. 3. Tentative features: * (Arun Suresh). YARN-5972: Support pausing/freezing opportunistic containers. Only one pending patch. Plan to finish before Jan 7th. * (Haibo Chen). YARN-1011: Resource overcommitment. Looks challenging to be done before Jan 2018. * (Anu): HDFS-7240: Ozone. Given the discussion on HDFS-7240. Looks challenging to be done before Jan 2018. * (Varun V) YARN-5673: container-executor write. Given security refactoring of c-e (YARN-6623) is already landed, IMHO other stuff may be moved to 3.2. Thanks, Wangda On Fri, Dec 15, 2017 at 1:20 PM, Wangda Tan wrote: > Hi all, > > Congratulations on the 3.0.0-GA release! > > As we discussed in the previous email thread [1], I'd like to restart > 3.1.0 release plans. > > a) Quick summary: > a.1 Release status > We started 3.1 release discussion on Sep 6, 2017 [1]. As of today, > there’re 232 patches loaded on 3.1.0 alone [2], besides 6 open blockers and > 22 open critical issues. > > a.2 Release date update > Considering delays of 3.0-GA release by month-and-a-half, I propose to > move the dates as follows > - feature freeze date from Dec 15, 2017, to Jan 30, 2018 - last date for > any branches to get merged too; > - code freeze (blockers & critical only) date to Feb 08, 2018; > - release voting start by Feb 18, 2018, leaving time for at least two RCx > - release date from Jan 15, 2018, to Feb 28, 2018; > > Unlike before, I added an additional milestone for release-vote-start so > that we can account for voting time-period also. > > This overall is still 5 1/2 months of release-timeline unlike the faster > cadence we hoped for, but this, in my opinion, is the best-updated timeline > given the delays of the final release of 3.0-GA. > > b) Individual feature status: > I spoke to several feature owners and checked the status of un-finished > features, following are status of features planned to 3.1.0: > > b.1 Merged & Completed features: > * (Sunil) YARN-5881: Support absolute value in CapacityScheduler. > * (Wangda) YARN-6223: GPU support on YARN. Features in trunk and works > end-to-end. > * (Jian) YARN-5079,YARN-4793,YARN-4757,YARN-6419 YARN native services. > * (Steve Loughran): HADOOP-13786: S3Guard committer for zero-rename > commits. > * (Suma): YARN-7117: Capacity Scheduler: Support Auto Creation of Leaf > Queues While Doing Queue Mapping. > > b.2 Features close to finish: > * (Chris Douglas) HDFS-9806: HDFS Tiered Storage. Being voting now. > * (Zhankun) YARN-5983: FPGA support. Majority implementations completed > and merged to trunk. Except for UI/documentation. > * (Uma) HDFS-10285: HDFS SPS. Majority implementations are done, some > discussions going on about implementation. > > b.3 Tentative features: > * (Arun Suresh). YARN-5972: Support pausing/freezing opportunistic > containers. Only one pending patch. Plan to finish before Jan 7th. > * (Haibo Chen). YARN-1011: Resource overcommitment. Looks challenging to > be done before Jan 2018. > * (Arun Suresh / Kostas / Wangda). YARN-6592: New SchedulingRequest and > anti-affinity support. Tentative will figure out by Jan 1st. > * (Anu): HDFS-7240: Ozone. Given the discussion on HDFS-7240. Looks > challenging to be done before Jan 2018. > * (Varun V) YARN-5673: container-executor write. Given security > refactoring of c-e (YARN-6623) is already landed, IMHO other stuff may be > moved to 3.2. > > b.4 Additional release drivers > * More exhaustive upgrade testing from 2.x to 3.x. > > c) Regarding branch cut: > > We will keep pointing trunk to 3.1 and cut branch-3.1 until: A. some > feature planned to 3.2 has to be landed on trunk or B. After feature freeze > date, whichever comes first. > > I've also talked offline with Vinod to get help on release-management > given this is my first r
[jira] [Created] (HDFS-13027) Handle NPE due to deleted blocks in race condition
Vinayakumar B created HDFS-13027:
Summary: Handle NPE due to deleted blocks in race condition
Key: HDFS-13027
URL: https://issues.apache.org/jira/browse/HDFS-13027
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Reporter: Vinayakumar B
Since File deletions and Block removal from BlocksMap done in separate locks,
there are possibilities of NPE due to calls of
{{blockManager.getBlockCollection(block)}} returning null.
Handle all possibilities of NPEs due to this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
[jira] [Created] (HDFS-13026) Ozone: TestContainerPersistence is failing becaue of container data mismatch
Mukul Kumar Singh created HDFS-13026:
Summary: Ozone: TestContainerPersistence is failing becaue of
container data mismatch
Key: HDFS-13026
URL: https://issues.apache.org/jira/browse/HDFS-13026
Project: Hadoop HDFS
Issue Type: Sub-task
Components: ozone
Affects Versions: HDFS-7240
Environment: TestContainerPersistence fails because of the following
error.
{code}
[INFO] Running
org.apache.hadoop.ozone.container.common.impl.TestContainerPersistence
[ERROR] Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.386
s <<< FAILURE! - in
org.apache.hadoop.ozone.container.common.impl.TestContainerPersistence
[ERROR]
testMultipleWriteSingleRead(org.apache.hadoop.ozone.container.common.impl.TestContainerPersistence)
Time elapsed: 2.294 s <<< FAILURE!
org.junit.ComparisonFailure:
expected:<[76626052b877b37503fdb052dfd8f73398643a02f9f7432b4e3a7f8b69b85915]>
but was:<[940c05649be7c86ab3993aa708f3d30311ebc0b68723465ac9c90460a23e6e58]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.hadoop.ozone.container.common.impl.TestContainerPersistence.testMultipleWriteSingleRead(TestContainerPersistence.java:586)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)
at
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
{code}
Reporter: Mukul Kumar Singh
Assignee: Mukul Kumar Singh
Fix For: HDFS-7240
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
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: branch2+JDK7 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/107/ [Jan 16, 2018 3:31:02 AM] (rohithsharmaks) YARN-6736. Consider writing to both ats v1 & v2 from RM for smoother [Jan 16, 2018 10:59:13 AM] (brahma) HDFS-8693. refreshNamenodes does not support adding a new standby to a -1 overall The following subsystems voted -1: asflicense unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: Unreaped Processes : hadoop-hdfs:42 bkjournal:8 hadoop-yarn-client:5 hadoop-yarn-applications-distributedshell:1 hadoop-mapreduce-client-jobclient:2 hadoop-distcp:3 Failed junit tests : hadoop.hdfs.server.namenode.snapshot.TestSnapshottableDirListing hadoop.hdfs.server.namenode.ha.TestPipelinesFailover hadoop.hdfs.server.balancer.TestBalancer hadoop.hdfs.server.namenode.TestQuotaByStorageType hadoop.hdfs.server.namenode.ha.TestHAMetrics hadoop.hdfs.server.blockmanagement.TestSlowDiskTracker hadoop.hdfs.server.namenode.TestSecurityTokenEditLog hadoop.hdfs.server.namenode.TestFileLimit hadoop.hdfs.server.namenode.ha.TestFailureToReadEdits hadoop.hdfs.server.namenode.snapshot.TestCheckpointsWithSnapshots hadoop.hdfs.server.namenode.TestFSImageWithAcl hadoop.hdfs.server.namenode.TestFavoredNodesEndToEnd hadoop.hdfs.server.namenode.TestListOpenFiles hadoop.hdfs.server.namenode.ha.TestEditLogsDuringFailover hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup hadoop.hdfs.server.namenode.TestStreamFile hadoop.hdfs.server.blockmanagement.TestNameNodePrunesMissingStorages hadoop.hdfs.server.namenode.snapshot.TestDisallowModifyROSnapshot hadoop.hdfs.server.namenode.TestDecommissioningStatus hadoop.hdfs.server.namenode.TestAuditLogger hadoop.hdfs.server.namenode.TestGenericJournalConf hadoop.hdfs.server.namenode.TestTransferFsImage hadoop.hdfs.server.namenode.ha.TestBootstrapStandbyWithQJM hadoop.hdfs.server.mover.TestMover hadoop.hdfs.server.blockmanagement.TestUnderReplicatedBlocks hadoop.hdfs.server.namenode.TestAclConfigFlag hadoop.hdfs.server.namenode.ha.TestDelegationTokensWithHA hadoop.hdfs.server.namenode.TestSecondaryWebUi hadoop.hdfs.server.namenode.snapshot.TestNestedSnapshots hadoop.hdfs.server.namenode.snapshot.TestSnapshotBlocksMap hadoop.hdfs.server.namenode.ha.TestXAttrsWithHA hadoop.hdfs.server.namenode.snapshot.TestXAttrWithSnapshot hadoop.hdfs.server.namenode.web.resources.TestWebHdfsDataLocality hadoop.hdfs.server.datanode.TestStorageReport hadoop.hdfs.server.federation.router.TestNamenodeHeartbeat hadoop.hdfs.server.namenode.TestCacheDirectives hadoop.hdfs.server.namenode.TestProtectedDirectories hadoop.hdfs.server.namenode.TestLargeDirectoryDelete hadoop.hdfs.server.namenode.TestXAttrConfigFlag hadoop.hdfs.server.blockmanagement.TestBlockStatsMXBean hadoop.hdfs.server.namenode.snapshot.TestAclWithSnapshot hadoop.hdfs.server.namenode.ha.TestDNFencingWithReplication hadoop.hdfs.server.namenode.snapshot.TestSnapshot hadoop.hdfs.server.namenode.TestBackupNode hadoop.hdfs.server.balancer.TestBalancerWithSaslDataTransfer hadoop.hdfs.server.namenode.ha.TestHarFileSystemWithHA hadoop.hdfs.server.federation.router.TestRouterRpcMultiDestination hadoop.hdfs.server.namenode.TestStartup hadoop.hdfs.server.namenode.snapshot.TestFileContextSnapshot hadoop.hdfs.server.namenode.snapshot.TestSnapshotNameWithInvalidCharacters hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFS hadoop.hdfs.server.blockmanagement.TestNodeCount hadoop.hdfs.server.namenode.ha.TestDFSUpgradeWithHA hadoop.hdfs.server.namenode.ha.TestHAStateTransitions hadoop.hdfs.server.namenode.TestSaveNamespace hadoop.hdfs.server.namenode.TestNameNodeRpcServerMethods hadoop.hdfs.server.namenode.snapshot.TestOpenFilesWithSnapshot hadoop.hdfs.server.federation.store.driver.TestStateStoreFileSystem hadoop.hdfs.server.namenode.TestDeadDatanode hadoop.hdfs.server.namenode.ha.TestEditLogTailer hadoop.hdfs.server.balancer.TestBalancerRPCDelay hadoop.hdfs.server.namenode.ha.TestStateTransitionFailure hadoop.hdfs.server.namenode.TestNameNodeResourceChecker hadoop.hdfs.server.namenode.snapshot.TestSnapshotDeletion hadoop.hdfs.server.blockmanagement.TestReplicationPolicyWithUpgradeDomain hadoop.hdfs.server.namenode.snapshot.TestSnaps
