You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2016/09/28 19:12:20 UTC

[jira] [Commented] (SENTRY-1440) Fencing implementation in sentry-ha can create two fencing tables

    [ https://issues.apache.org/jira/browse/SENTRY-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530575#comment-15530575 ] 

Alexander Kolbasov commented on SENTRY-1440:
--------------------------------------------

Most likely we are not going to use Fencing at all so this can be closed once we drop Fencing. Let's keep it around until then.

> Fencing implementation in sentry-ha can create two fencing tables
> -----------------------------------------------------------------
>
>                 Key: SENTRY-1440
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1440
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Alexander Kolbasov
>            Assignee: Alexander Kolbasov
>            Priority: Minor
>
> The fencing code in sentry-ha has a logic that creates a fencing table when it doesn't exist. The problem is that this code isn't atomic. It is possible for two processes to create their fencing table at the same time. This is rather bad because the remaining fencing code checks that only one such table exists and fails otherwise.
> Note that for this to happen the fencing table shouldn't exist and both processes should decide to become active, so this isn't something that is likely to happen, but it is still good to fix.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)