[KUDU-3119] ToolTest.TestFsAddRemoveDataDirEndToEnd reports race under TSAN

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.12.0
• Component/s: CLI, test
• Assignee: Unassigned
• Reporter: Alexey Serbin
• Created: 12/May/20 05:14
• Updated: 26/Aug/20 01:20
• Resolved: 26/Aug/20 01:20

Description

Sometimes the TestFsAddRemoveDataDirEndToEnd scenario of the ToolTest reports races for TSAN builds:

/data0/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/tools/kudu-tool-test.cc:266: Failure
Failed
Bad status: Runtime error: /tmp/dist-test-taskIZqSmU/build/tsan/bin/kudu: process exited with non-ze
ro status 66
Google Test trace:
/data0/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/tools/kudu-tool-test.cc:265: W0506 17:5
6:02.744191  4432 flags.cc:404] Enabled unsafe flag: --never_fsync=true
I0506 17:56:02.780252  4432 fs_manager.cc:263] Metadata directory not provided
I0506 17:56:02.780442  4432 fs_manager.cc:269] Using write-ahead log directory (fs_wal_dir) as metad
ata directory
I0506 17:56:02.789638  4432 fs_manager.cc:399] Time spent opening directory manager: real 0.007s
        user 0.005s     sys 0.002s
I0506 17:56:02.789986  4432 env_posix.cc:1676] Not raising this process' open files per process limi
t of 1048576; it is already as high as it can go
I0506 17:56:02.790426  4432 file_cache.cc:465] Constructed file cache lbm with capacity 419430
==================
WARNING: ThreadSanitizer: data race (pid=4432)
...

The log is attached.