[ https://issues.apache.org/jira/browse/KUDU-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175778#comment-17175778 ]
Alexey Serbin edited comment on KUDU-3119 at 8/11/20, 6:44 PM: --------------------------------------------------------------- I changed the priority to BLOCKER in the context of cutting a new release soon. It would be great to clarify on this: # If this is a real race, could this affect data consistency, leading to data corruption or alike in the long run? # If this is a race that could cause a corruption (done either by the {{kudu}} CLI tool or by kudu tablet server), I think it should be fixed before cutting next release. was (Author: aserbin): I changed the priority to BLOCKER in the context of cutting a new release soon. It would be great to clarify on this: # If this is a real race, could this affect data consistency, leading to data corruption or alike in the long run? # If this is a race that could cause a corruption (done either by the {{kudu}} CLI tool or by kudu tablet server,) it should be fixed before cutting the upcoming release. > ToolTest.TestFsAddRemoveDataDirEndToEnd reports race under TSAN > --------------------------------------------------------------- > > Key: KUDU-3119 > URL: https://issues.apache.org/jira/browse/KUDU-3119 > Project: Kudu > Issue Type: Bug > Components: CLI, test > Reporter: Alexey Serbin > Priority: Blocker > Attachments: kudu-tool-test.20200709.txt.xz, kudu-tool-test.3.txt.xz, > kudu-tool-test.log.xz > > > Sometimes the {{TestFsAddRemoveDataDirEndToEnd}} scenario of the {{ToolTest}} > reports races for TSAN builds: > {noformat} > /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) > ... > {noformat} > The log is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)