[
https://issues.apache.org/jira/browse/KUDU-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803378#comment-17803378
]
ASF subversion and git services commented on KUDU-3252:
-------------------------------------------------------
Commit 2810e635cc72aa5279a9dc787b6becad6e0098a9 in kudu's branch
refs/heads/master from Mahesh Reddy
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=2810e635c ]
KUDU-3252: Follow up to replica placement bug
This patch addresses the feedback left on
patch [1].
ReservoirSample is refactored to accept an
unsigned integer rather than a signed integer.
A new test is added to verify the functionality
of the tiebreaker scenarios of
PlacementPolicy::SelectReplica().
[1] https://github.com/apache/kudu/commit/a84c8376a
Change-Id: I28582cae538ca27fa26fbfae84460b3b264ddb86
Reviewed-on: http://gerrit.cloudera.org:8080/20827
Tested-by: Alexey Serbin <ale...@apache.org>
Reviewed-by: Alexey Serbin <ale...@apache.org>
> 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.20.10#820010)
