[
https://issues.apache.org/jira/browse/SENTRY-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kolbasov resolved SENTRY-1440.
----------------------------------------
Resolution: Won't Fix
Assignee: Alexander Kolbasov
Fix Version/s: sentry-ha-redesign
We are no longer using fencing
> 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
> Fix For: sentry-ha-redesign
>
>
> 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)
