[ 
https://issues.apache.org/jira/browse/HDDS-5766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-5766:
---------------------------------
    Labels: pull-request-available  (was: )

> Speed up some OM tests by skipping SCM safemode check
> -----------------------------------------------------
>
>                 Key: HDDS-5766
>                 URL: https://issues.apache.org/jira/browse/HDDS-5766
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 1.2.0
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>              Labels: pull-request-available
>
> Many of the OzoneManager integration tests do not really use SCM or the 
> datanodes. Therefore we can skip the safemode check in SCM and start zero 
> datanodes to make the mini-cluster come up faster.
> With just this change, on my laptop:
> ```
> TestOzoneManagerConfiguration went from 6min -> 3min 40s.
> TestOzoneManagerHAMetadataOnly went from 4min 19s -> 1min 9s.
> TestOzoneManagerListVolumes went from 40s -> 20s
> TestOMMetrics went from 2min 6 -> 39s 55s
> ```
> The runtime for these tests on Github is:
> ```
> [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 273.591 s - in org.apache.hadoop.ozone.om.TestOzoneManagerConfiguration
> Warning:  Tests run: 10, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 
> 363.67 s - in org.apache.hadoop.ozone.om.TestOzoneManagerHAMetadataOnly
> [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 181.937 s - in org.apache.hadoop.ozone.om.TestOmMetrics
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 50.156 
> s - in org.apache.hadoop.ozone.om.TestOzoneManagerListVolumes
> ```



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to