Re: HADOOP-15124 review

[Andrew Wang]

I think it's fine to ask for review help on the dev list, sometimes JIRAs
are missed or get stuck. It also helps sometimes to git blame the files
you're touching and see who is a likely reviewer, and then pinging them on
JIRA to ask for a review.

Igor, hopefully a committer takes interest in your JIRA and helps you get
it integrated.

Best,
Andrew

On Tue, Jun 26, 2018 at 9:27 PM Igor Dvorzhak 
wrote:

> Hi Yiqun,
>
> Thank you for the explanation. I didn't know that this is not appropriate
> and will not do so in future.
>
> Thanks,
> Igor
>
>
> On Tue, Jun 26, 2018 at 7:18 PM Lin,Yiqun(vip.com) <
> yiqun01@vipshop.com> wrote:
>
>> Hi Igor,
>>
>> It’s not appropriate to ask for a review request in dev mailing list. Dev
>> mailing list is mainly used for discussing and answering user’s questions.
>> You can ask for the review under specific JIRA, that will be seen by
>> committers or others. If they have time, they will help take the review.
>>
>> Yiqun
>> Thanks
>>
>> 发件人: Igor Dvorzhak [mailto:i...@google.com.INVALID]
>> 发送时间: 2018年6月26日 23:52
>> 收件人: hdfs-dev@hadoop.apache.org; common-...@hadoop.apache.org
>> 主题: Re: HADOOP-15124 review
>>
>> +common-...@hadoop.apache.org
>>
>> On Tue, Jun 26, 2018 at 8:49 AM Igor Dvorzhak > i...@google.com>> wrote:
>> Hello,
>>
>> I have a patch that
>> improves FileSystem.Statistics implementation and I would like to commit it.
>>
>> May somebody review it?
>>
>> Best regards,
>> Igor Dvorzhak
>> 本电子邮件可能为保密文件。如果阁下非电子邮件所指定之收件人，谨请立即通知本人。敬请阁下不要使用、保存、复印、打印、散布本电子邮件及其内容，或将其用于其他任何目的或向任何人披露。谢谢您的合作！
>> This communication is intended only for the addressee(s) and may contain
>> information that is privileged and confidential. You are hereby notified
>> that, if you are not an intended recipient listed above, or an authorized
>> employee or agent of an addressee of this communication responsible for
>> delivering e-mail messages to an intended recipient, any dissemination,
>> distribution or reproduction of this communication (including any
>> attachments hereto) is strictly prohibited. If you have received this
>> communication in error, please notify us immediately by a reply e-mail
>> addressed to the sender and permanently delete the original e-mail
>> communication and any attachments from all storage devices without making
>> or otherwise retaining a copy.
>>
>

Re: HADOOP-15124 review

[Igor Dvorzhak]

Hi Yiqun,

Thank you for the explanation. I didn't know that this is not appropriate
and will not do so in future.

Thanks,
Igor


On Tue, Jun 26, 2018 at 7:18 PM Lin,Yiqun(vip.com) 
wrote:

> Hi Igor,
>
> It’s not appropriate to ask for a review request in dev mailing list. Dev
> mailing list is mainly used for discussing and answering user’s questions.
> You can ask for the review under specific JIRA, that will be seen by
> committers or others. If they have time, they will help take the review.
>
> Yiqun
> Thanks
>
> 发件人: Igor Dvorzhak [mailto:i...@google.com.INVALID]
> 发送时间: 2018年6月26日 23:52
> 收件人: hdfs-dev@hadoop.apache.org; common-...@hadoop.apache.org
> 主题: Re: HADOOP-15124 review
>
> +common-...@hadoop.apache.org
>
> On Tue, Jun 26, 2018 at 8:49 AM Igor Dvorzhak  i...@google.com>> wrote:
> Hello,
>
> I have a patch that
> improves FileSystem.Statistics implementation and I would like to commit it.
>
> May somebody review it?
>
> Best regards,
> Igor Dvorzhak
> 本电子邮件可能为保密文件。如果阁下非电子邮件所指定之收件人，谨请立即通知本人。敬请阁下不要使用、保存、复印、打印、散布本电子邮件及其内容，或将其用于其他任何目的或向任何人披露。谢谢您的合作！
> This communication is intended only for the addressee(s) and may contain
> information that is privileged and confidential. You are hereby notified
> that, if you are not an intended recipient listed above, or an authorized
> employee or agent of an addressee of this communication responsible for
> delivering e-mail messages to an intended recipient, any dissemination,
> distribution or reproduction of this communication (including any
> attachments hereto) is strictly prohibited. If you have received this
> communication in error, please notify us immediately by a reply e-mail
> addressed to the sender and permanently delete the original e-mail
> communication and any attachments from all storage devices without making
> or otherwise retaining a copy.
>


smime.p7s
Description: S/MIME Cryptographic Signature

答复: HADOOP-15124 review

[Lin,Yiqun(vip.com)]

Hi Igor,

It’s not appropriate to ask for a review request in dev mailing list. Dev 
mailing list is mainly used for discussing and answering user’s questions. You 
can ask for the review under specific JIRA, that will be seen by committers or 
others. If they have time, they will help take the review.

Yiqun
Thanks

发件人: Igor Dvorzhak [mailto:i...@google.com.INVALID]
发送时间: 2018年6月26日 23:52
收件人: hdfs-dev@hadoop.apache.org; common-...@hadoop.apache.org
主题: Re: HADOOP-15124 review

+common-...@hadoop.apache.org

On Tue, Jun 26, 2018 at 8:49 AM Igor Dvorzhak 
mailto:i...@google.com>> wrote:
Hello,

I have a patch that 
improves FileSystem.Statistics implementation and I would like to commit it.

May somebody review it?

Best regards,
Igor Dvorzhak
本电子邮件可能为保密文件。如果阁下非电子邮件所指定之收件人，谨请立即通知本人。敬请阁下不要使用、保存、复印、打印、散布本电子邮件及其内容，或将其用于其他任何目的或向任何人披露。谢谢您的合作！
 This communication is intended only for the addressee(s) and may contain 
information that is privileged and confidential. You are hereby notified that, 
if you are not an intended recipient listed above, or an authorized employee or 
agent of an addressee of this communication responsible for delivering e-mail 
messages to an intended recipient, any dissemination, distribution or 
reproduction of this communication (including any attachments hereto) is 
strictly prohibited. If you have received this communication in error, please 
notify us immediately by a reply e-mail addressed to the sender and permanently 
delete the original e-mail communication and any attachments from all storage 
devices without making or otherwise retaining a copy.

[jira] [Created] (HDDS-196) PipelineManager should choose datanodes based on ContainerPlacementPolicy

[Xiaoyu Yao (JIRA)]

Xiaoyu Yao created HDDS-196:
---

 Summary: PipelineManager should choose datanodes based on 
ContainerPlacementPolicy 
 Key: HDDS-196
 URL: https://issues.apache.org/jira/browse/HDDS-196
 Project: Hadoop Distributed Data Store
  Issue Type: Bug
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao


This is somehow not connected now after refactoring. This ticket is opened to 
fix it.



--
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-13703) Avoid allocation of CorruptedBlocks hashmap when no corrupted blocks are hit

[Todd Lipcon (JIRA)]

Todd Lipcon created HDFS-13703:
--

 Summary: Avoid allocation of CorruptedBlocks hashmap when no 
corrupted blocks are hit
 Key: HDFS-13703
 URL: https://issues.apache.org/jira/browse/HDFS-13703
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: performance
Reporter: Todd Lipcon
Assignee: Todd Lipcon


The DFSClient creates a CorruptedBlocks object, which contains a HashMap, on 
every read call. In most cases, a read will not hit any corrupted blocks, and 
this hashmap is not used. It seems the JIT isn't smart enough to eliminate this 
allocation. We would be better off avoiding it and only allocating in the rare 
case when a corrupt block is hit.

Removing this allocation reduced CPU usage of a TeraValidate job by about 10%.



--
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] (HDDS-195) Create generic CommandWatcher utility

[Elek, Marton (JIRA)]

Elek, Marton created HDDS-195:
-

 Summary: Create generic CommandWatcher utility
 Key: HDDS-195
 URL: https://issues.apache.org/jira/browse/HDDS-195
 Project: Hadoop Distributed Data Store
  Issue Type: Improvement
Reporter: Elek, Marton
 Fix For: 0.2.1


In some cases we need a class which can track the status of the outgoing 
commands.

The commands should be resent after a while except a status message is received 
about command completion.

On high level, we need a builder factory, which takes the following parameters:

* (destination) event type and the payload of the command which should be 
repeated.
* the ID of the command/event
* The event/topic of the completion messages. If a EventWithIdentifier is 
received on this topic, the specific event is done and don't need to resend it. 



--
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-13702) HTrace hooks taking 10-15% CPU in DFS client when disabled

[Todd Lipcon (JIRA)]

Todd Lipcon created HDFS-13702:
--

 Summary: HTrace hooks taking 10-15% CPU in DFS client when disabled
 Key: HDFS-13702
 URL: https://issues.apache.org/jira/browse/HDFS-13702
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: performance
Affects Versions: 3.0.0
Reporter: Todd Lipcon


I am seeing DFSClient.newReaderTraceScope take ~15% CPU in a teravalidate 
workload even when HTrace is disabled. This is because it stringifies several 
integers. We should avoid all allocation and stringification when htrace is 
disabled.



--
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-13701) Removal of logging guards regressed performance

[Todd Lipcon (JIRA)]

Todd Lipcon created HDFS-13701:
--

 Summary: Removal of logging guards regressed performance
 Key: HDFS-13701
 URL: https://issues.apache.org/jira/browse/HDFS-13701
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: performance
Affects Versions: 3.0.0
Reporter: Todd Lipcon


HDFS-8971 removed various logging guards from hot methods in the DFS client. In 
theory using a format string with {} placeholders is equivalent, but in fact 
it's not equivalent when one or more of the variable arguments are primitives. 
To be passed as part of the varargs array, the primitives need to be boxed. I 
am seeing Integer.valueOf() inside BlockReaderLocal.read taking ~3% of CPU.



--
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-15124 review

[Igor Dvorzhak]

+common-...@hadoop.apache.org

On Tue, Jun 26, 2018 at 8:49 AM Igor Dvorzhak  wrote:

> Hello,
>
> I have a patch  that
> improves FileSystem.Statistics implementation and I would like to commit it.
>
> May somebody review it?
>
> Best regards,
> Igor Dvorzhak
>


smime.p7s
Description: S/MIME Cryptographic Signature

HADOOP-15124 review

[Igor Dvorzhak]

Hello,

I have a patch  that
improves FileSystem.Statistics implementation and I would like to commit it.

May somebody review it?

Best regards,
Igor Dvorzhak


smime.p7s
Description: S/MIME Cryptographic Signature

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

[Apache Jenkins Server]

For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/

[Jun 25, 2018 1:38:57 PM] (stevel) HADOOP-14396. Add builder interface to 
FileContext. Contributed by  Lei
[Jun 25, 2018 4:50:27 PM] (inigoiri) HADOOP-15458. 
TestLocalFileSystem#testFSOutputStreamBuilder fails on
[Jun 25, 2018 5:38:03 PM] (rohithsharmaks) YARN-8457. Compilation is broken 
with -Pyarn-ui.
[Jun 25, 2018 8:05:22 PM] (aengineer) HDDS-191. Queue SCMCommands via 
EventQueue in SCM. Contributed by Elek,
[Jun 25, 2018 8:59:41 PM] (mackrorysd) HADOOP-15423. Merge fileCache and 
dirCache into ine single cache in
[Jun 25, 2018 10:36:45 PM] (todd) HADOOP-15550. Avoid static initialization of 
ObjectMappers
[Jun 25, 2018 10:47:54 PM] (miklos.szegedi) YARN-8438. 
TestContainer.testKillOnNew flaky on trunk. Contributed by




-1 overall


The following subsystems voted -1:
asflicense findbugs pathlen 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:

Failed junit tests :

   hadoop.hdfs.server.datanode.TestDirectoryScanner 
   hadoop.hdfs.web.TestWebHdfsTimeouts 
   
hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageEntities 
   
hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowActivity 
   hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRun 
   hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageApps 
   
hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRunCompaction
 
   
hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageSchema 
   
hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageDomain 
   
hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage
 
   hadoop.yarn.applications.distributedshell.TestDistributedShell 
   hadoop.mapred.TestMRTimelineEventHandling 
  

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/diff-compile-cc-root.txt
  [4.0K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/diff-compile-javac-root.txt
  [352K]

   checkstyle:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/diff-checkstyle-root.txt
  [4.0K]

   pathlen:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/pathlen.txt
  [12K]

   pylint:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/diff-patch-pylint.txt
  [24K]

   shellcheck:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/diff-patch-shellcheck.txt
  [20K]

   shelldocs:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/diff-patch-shelldocs.txt
  [16K]

   whitespace:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/whitespace-eol.txt
  [9.4M]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/whitespace-tabs.txt
  [1.1M]

   xml:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/xml.txt
  [4.0K]

   findbugs:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-hdds_client.txt
  [56K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-hdds_container-service.txt
  [48K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-hdds_server-scm.txt
  [56K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-hdds_tools.txt
  [12K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-ozone_client.txt
  [4.0K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-ozone_common.txt
  [24K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-ozone_objectstore-service.txt
  [4.0K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-ozone_ozone-manager.txt
  [4.0K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-ozone_ozonefs.txt
  [8.0K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/branch-findbugs-hadoop-ozone_tools.txt
  [4.0K]

   javadoc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/823/artifact/out/diff-javadoc-javadoc-root.txt
  [760K]

   unit:

   

[jira] [Created] (HDFS-13700) The process of loading image can be done in a pipeline model

[zhouyingchao (JIRA)]

zhouyingchao created HDFS-13700:
---

 Summary: The process of loading image can be done in a pipeline 
model
 Key: HDFS-13700
 URL: https://issues.apache.org/jira/browse/HDFS-13700
 Project: Hadoop HDFS
  Issue Type: Improvement
Reporter: zhouyingchao


The process of loading a file system image involves reading inodes section, 
deserializing inodes, initializing inodes, adding inodes to the global map, 
reading directories section, adding inodes to their parents' map, cache name 
etc. These steps can be done in a pipeline model to reduce the total duration. 



--
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: trunk+JDK8 on Windows/x64

[Apache Jenkins Server]

For more details, see https://builds.apache.org/job/hadoop-trunk-win/509/

[Jun 25, 2018 1:15:31 AM] (wwei) YARN-8443. Total #VCores in cluster metrics is 
wrong when




-1 overall


The following subsystems voted -1:
compile mvninstall pathlen unit


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc javac


The following subsystems are considered long running:
(runtime bigger than 1h 00m 00s)
unit


Specific tests:

Failed junit tests :

   hadoop.crypto.TestCryptoStreamsWithOpensslAesCtrCryptoCodec 
   hadoop.fs.contract.rawlocal.TestRawlocalContractAppend 
   hadoop.fs.TestFileUtil 
   hadoop.fs.TestFsShellCopy 
   hadoop.fs.TestFsShellList 
   hadoop.fs.TestLocalFileSystem 
   hadoop.http.TestHttpServer 
   hadoop.http.TestHttpServerLogs 
   hadoop.io.nativeio.TestNativeIO 
   hadoop.ipc.TestIPC 
   hadoop.ipc.TestSocketFactory 
   hadoop.metrics2.impl.TestStatsDMetrics 
   hadoop.security.TestSecurityUtil 
   hadoop.security.TestShellBasedUnixGroupsMapping 
   hadoop.security.token.TestDtUtilShell 
   hadoop.util.TestDiskCheckerWithDiskIo 
   hadoop.util.TestNativeCodeLoader 
   hadoop.hdfs.qjournal.server.TestJournalNode 
   hadoop.hdfs.qjournal.server.TestJournalNodeSync 
   hadoop.hdfs.server.blockmanagement.TestNameNodePrunesMissingStorages 
   hadoop.hdfs.server.datanode.fsdataset.impl.TestProvidedImpl 
   hadoop.hdfs.server.datanode.TestBlockPoolSliceStorage 
   hadoop.hdfs.server.datanode.TestBlockScanner 
   hadoop.hdfs.server.datanode.TestDataNodeFaultInjector 
   hadoop.hdfs.server.datanode.TestDataNodeVolumeFailure 
   hadoop.hdfs.server.datanode.TestDirectoryScanner 
   hadoop.hdfs.server.diskbalancer.TestDiskBalancerRPC 
   hadoop.hdfs.server.namenode.ha.TestDFSUpgradeWithHA 
   hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA 
   hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics 
   hadoop.hdfs.server.namenode.TestDecommissioningStatus 
   hadoop.hdfs.server.namenode.TestNameNodeMXBean 
   hadoop.hdfs.TestDatanodeStartupFixesLegacyStorageIDs 
   hadoop.hdfs.TestDecommissionWithStriped 
   hadoop.hdfs.TestDFSShell 
   hadoop.hdfs.TestDFSStripedInputStream 
   hadoop.hdfs.TestDFSStripedInputStreamWithRandomECPolicy 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailureWithRandomECPolicy 
   hadoop.hdfs.TestDFSUpgradeFromImage 
   hadoop.hdfs.TestFetchImage 
   hadoop.hdfs.TestHDFSFileSystemContract 
   hadoop.hdfs.TestPread 
   hadoop.hdfs.TestReadStripedFileWithDecodingCorruptData 
   hadoop.hdfs.TestReconstructStripedFile 
   hadoop.hdfs.TestReconstructStripedFileWithRandomECPolicy 
   hadoop.hdfs.TestSecureEncryptionZoneWithKMS 
   hadoop.hdfs.TestTrashWithSecureEncryptionZones 
   hadoop.hdfs.tools.TestDFSAdmin 
   hadoop.hdfs.web.TestWebHDFS 
   hadoop.hdfs.web.TestWebHdfsUrl 
   hadoop.fs.http.server.TestHttpFSServerWebServer 
   
hadoop.yarn.server.nodemanager.containermanager.launcher.TestContainerLaunch 
   hadoop.yarn.server.nodemanager.containermanager.TestAuxServices 
   hadoop.yarn.server.nodemanager.containermanager.TestContainerManager 
   hadoop.yarn.server.nodemanager.recovery.TestNMLeveldbStateStoreService 
   hadoop.yarn.server.nodemanager.TestContainerExecutor 
   hadoop.yarn.server.nodemanager.TestNodeManagerResync 
   hadoop.yarn.server.webproxy.amfilter.TestAmFilter 
   
hadoop.yarn.server.applicationhistoryservice.TestApplicationHistoryServer 
   
hadoop.yarn.server.timeline.security.TestTimelineAuthenticationFilterForV1 
   hadoop.yarn.server.resourcemanager.metrics.TestSystemMetricsPublisher 
   
hadoop.yarn.server.resourcemanager.scheduler.capacity.conf.TestFSSchedulerConfigurationStore
 
   
hadoop.yarn.server.resourcemanager.scheduler.capacity.conf.TestLeveldbConfigurationStore
 
   
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler 
   
hadoop.yarn.server.resourcemanager.scheduler.constraint.TestPlacementProcessor 
   
hadoop.yarn.server.resourcemanager.scheduler.fair.TestAllocationFileLoaderService
 
   hadoop.yarn.server.resourcemanager.TestResourceTrackerService 
   
hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesAppsModification 
   hadoop.yarn.client.api.impl.TestNMClient 
   hadoop.yarn.client.TestHedgingRequestRMFailoverProxyProvider 
   hadoop.yarn.server.timeline.TestEntityGroupFSTimelineStore 
   
hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage
 
   
hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowActivity 
   hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRun