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 2017/01/20 03:30:27 UTC

[jira] [Resolved] (SENTRY-1441) Error during fencing table rename can disable master

     [ https://issues.apache.org/jira/browse/SENTRY-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Kolbasov resolved SENTRY-1441.
----------------------------------------
    Resolution: Won't Fix
      Assignee: Alexander Kolbasov

We are not using fencing any more

> Error during fencing table rename can disable master
> ----------------------------------------------------
>
>                 Key: SENTRY-1441
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1441
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Alexander Kolbasov
>            Assignee: Alexander Kolbasov
>             Fix For: sentry-ha-redesign
>
>
> The code that handles fencing table renames handles errors by throwing exceptions. These exceptions are propagated all the way to the caller, so the leader will not re-try the table rename and will never be able to do any other DB operation. The only recovery is to switch back and forth between master and slave.



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