[ https://issues.apache.org/jira/browse/KUDU-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293375#comment-17293375 ]
Andrew Wong commented on KUDU-3252: ----------------------------------- If the issue is the absence of file locking, an implementation of WAL instance files (as might be a part of KUDU-2975) that leverages {{DirInstanceMetadataFiles}} (see [https://github.com/apache/kudu/blob/master/src/kudu/fs/dir_util.h#L74)] could help prevent this. > FsManager initialized contention if two tserver instances try to call > CreateInitialFileSystemLayout on the same folder > ----------------------------------------------------------------------------------------------------------------------- > > Key: KUDU-3252 > URL: https://issues.apache.org/jira/browse/KUDU-3252 > Project: Kudu > Issue Type: Bug > Reporter: Redriver > Priority: Critical > > {color:#1d1c1d}I scanned the Kudu source code for DeleteDir invocation, there > are 2 places: > {color}[https://github.com/apache/kudu/blob/master/src/kudu/fs/fs_manager.cc#L384]{color:#1d1c1d} > and > {color}[https://github.com/apache/kudu/blob/master/src/kudu/fs/fs_manager.cc#L485]{color:#1d1c1d}.{color} > {color:#1d1c1d}Imagine, I start kudu-tserver twice by mistake, finally only > one kudu-tserver started, is it possible that its folder may be removed by > another kudu-tserver since it failed to start.{color} -- This message was sent by Atlassian Jira (v8.3.4#803005)