HDDS-3284. ozonesecure-mr test fails due to lack of disk space

[adoroszlai]

What changes were proposed in this pull request?

Disable YARN disk utilization check in ozonesecure-mr acceptance test.

Plenty of disk space is available in CI, but more than 90% of the disk is used:

Filesystem      Size  Used Avail Use% Mounted on
...
/dev/sda1        84G   75G  8.3G  91% /

Thus directory checker marks it as invalid:

WARN  DirectoryCollection:418 - Directory /tmp/hadoop-hadoop/nm-local-dir error, used space above threshold of 90.0%, removing from list of valid directories
WARN  DirectoryCollection:418 - Directory /opt/hadoop/logs/userlogs error, used space above threshold of 90.0%, removing from list of valid directories

https://issues.apache.org/jira/browse/HDDS-3284

How was this patch tested?

https://github.com/adoroszlai/hadoop-ozone/runs/535925282

==============================================================================
Execute PI calculation                                                | PASS |
------------------------------------------------------------------------------
Execute WordCount                                                     | PASS |
------------------------------------------------------------------------------
ozonesecure-mr-mapreduce :: Execute MR jobs                           | PASS |

[sodonnel]

Thanks for looking into this. +1 on this from me, pending CI, but some of the "it-*" tests are a bit flaky.

[adoroszlai]

Thanks @sodonnel. Since it only changes acceptance tests, I think we can merge it even if it-client happens to fail.

[sodonnel]

Yea, I have seen random failures on it-client. As this is a yarn only change, I cannot see how it could impact the integration tests, so I think we are good to merge it.

[vivekratnavel]

+1 LGTM.

[hanishakoneru]

Thanks @adoroszlai for working on this. I will go ahead and merge this as the change is only in acceptance tests.
Thanks @sodonnel and @vivekratnavel for the reviews.

[adoroszlai]

Thanks @sodonnel and @vivekratnavel for the review, and @hanishakoneru for merging it.