[
https://issues.apache.org/jira/browse/KUDU-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-3527.
---------------------------------
Fix Version/s: 1.18.0
Resolution: Fixed
> Fix BlockManagerTest.TestMetadataOkayDespiteFailure on rhel 8.8 graviton
> -------------------------------------------------------------------------
>
> Key: KUDU-3527
> URL: https://issues.apache.org/jira/browse/KUDU-3527
> Project: Kudu
> Issue Type: Bug
> Reporter: Zoltan Martonka
> Assignee: Zoltan Martonka
> Priority: Major
> Fix For: 1.18.0
>
>
> BlockManagerTest.TestMetadataOkayDespiteFailure might fail on systems where
> fs_block_size=64k.
> *Cause:*
> Currently tablets fail to load if one metadata is missing but there is still
> a non-empty ".data" file. If FLAGS_env_inject_eio is not zero, then there is
> a chance that, when we delete the container file, we only delete the ".meta",
> but leave the ".data" file.
> In the current test on systems with fs_block_size=4k deletion never occurs.
> Changing to kNumAppends=64 will cause the test to randomly fail on x86
> systems too, although only with a 2-3% chance (at least on my ubuntu20
> machine).
> *Solution:*
> This test was not intended to test the file deletion itself (as it does not
> do it on x86_64 or 4k arm kernels). It only occurs, because
> _FLAGS_log_container_max_size = 256 * 1024;_ is _not "large enought"._
> _We should just set_ FLAGS_log_block_manager_delete_dead_container = false;
> to restore the original scope of the test.
> There is a separate issue for the root cause (which is not arm specific at
> all):
> https://issues.apache.org/jira/browse/KUDU-3528
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
