[
https://issues.apache.org/jira/browse/KUDU-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907197#comment-17907197
]
ASF subversion and git services commented on KUDU-3591:
-------------------------------------------------------
Commit 50eaddfa9448c188008939a4b8c1439e9d4c95d6 in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=50eaddfa9 ]
KUDU-3591 a few extra options to speed up RocksDB bootstrapping
Even with changelist [1], RocksDB-specific flavors of the
FsManagerTestBase.TestAddRemoveDataDirsFuzz scenario still fail from
time to time even in non-sanitized DEBUG builds due to running out of
time allowance.
This patch introduces a couple of extra flags for the "logr" block
manager to use in test scenarios like that and tweaks already existing
flags to speed up bootstrapping of the embedded RocksDB instance.
Also, the number of iterations for the scenario has decreased 4 times.
As a quick validation of the scenario's runtime before and after this
patch, I ran the following multiple times:
time KUDU_ALLOW_SLOW_TESTS=1 ./bin/fs_manager-test
--gtest_filter='BlockManagerTypes/FsManagerTestBase.TestAddRemoveDataDirsFuzz/4'
--gtest_repeat=10 > /dev/null 2>&1
There is high variation in run times due to the stochastic nature
of the test scenario, but after running it many times I found that the
numbers below provide a good sense of the corresponding run times.
Before:
real 1m1.831s
user 0m36.494s
sys 0m16.228s
After:
real 0m10.237s
user 0m5.945s
sys 0m2.872s
This is a follow-up to [1].
[1] https://github.com/apache/kudu/commit/4116941c0
Change-Id: If95282d0e5ef3f5c1bd20e04dd24ac0a14374cee
Reviewed-on: http://gerrit.cloudera.org:8080/22232
Reviewed-by: Abhishek Chennaka <achenn...@cloudera.com>
Tested-by: Alexey Serbin <ale...@apache.org>
> FsManagerTestBase.TestAddRemoveDataDirsFuzz fails from time to time with
> RocksDB
> --------------------------------------------------------------------------------
>
> Key: KUDU-3591
> URL: https://issues.apache.org/jira/browse/KUDU-3591
> Project: Kudu
> Issue Type: Bug
> Components: fs, test
> Reporter: Alexey Serbin
> Priority: Major
> Attachments: fs_manager-test.txt.xz
>
>
> The fuzz test scenario FsManagerTestBase.TestAddRemoveDataDirsFuzz from time
> to time fails when run with the RocksDB option. I'm not sure whether the
> failure is just due to very long runtime, or something has stuck -- that's to
> be triaged. Below are a few lines from the log: they came just before the
> dump of the threads' stacks. The test was declared as failed because of
> exceeding the maximum unit test's run time. The full log is attached.
> {noformat}
> W20240713 01:16:21.454174 31297 fs_manager.cc:538] unable to create missing
> filesystem roots: Already present: FSManager roots already exist:
> /tmp/dist-test-taskLd2saP/test-tmp/fs_manager-test.0.BlockManagerTypes_FsManagerTestBase.TestAddRemoveDataDirsFuzz_7.1720832511594434-31297-0/new_data_849
> W20240713 01:16:21.635000 31297 dir_manager.cc:228] Invalid argument: could
> not initialize
> /tmp/dist-test-taskLd2saP/test-tmp/fs_manager-test.0.BlockManagerTypes_FsManagerTestBase.TestAddRemoveDataDirsFuzz_7.1720832511594434-31297-0/new_data_654/data:
> open RocksDB failed, path:
> /tmp/dist-test-taskLd2saP/test-tmp/fs_manager-test.0.BlockManagerTypes_FsManagerTestBase.TestAddRemoveDataDirsFuzz_7.1720832511594434-31297-0/new_data_654/data/rdb:
> Invalid argument:
> /tmp/dist-test-taskLd2saP/test-tmp/fs_manager-test.0.BlockManagerTypes_FsManagerTestBase.TestAddRemoveDataDirsFuzz_7.1720832511594434-31297-0/new_data_654/data/rdb/CURRENT:
> does not exist (create_if_missing is false)
> ...
> F20240713 01:16:37.134395 31300 test_main.cc:63] Maximum unit test time
> exceeded (870 sec)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
