You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "kalyan kumar kalvagadda (JIRA)" <ji...@apache.org> on 2017/05/24 11:57:04 UTC
[jira] [Comment Edited] (SENTRY-1774) HMSFollower should always
depend on persisted information to decide is full snapshot is needed
[ https://issues.apache.org/jira/browse/SENTRY-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022757#comment-16022757 ]
kalyan kumar kalvagadda edited comment on SENTRY-1774 at 5/24/17 11:56 AM:
---------------------------------------------------------------------------
[~akolb]
[~spena] is working on that as part of SENTRY-1760. When that decision is taken HMSFollower clears appropriate tables and returns.
Changes submitted as part of this jira would come in effect in the next run of HMSFollower
was (Author: kkalyan):
[~spena] is working on that as part of SENTRY-1760. When that decision is taken HMSFollower clears appropriate tables and returns.
Changes submitted as part of this jira would come in effect in the next run of HMSFollower
> HMSFollower should always depend on persisted information to decide is full snapshot is needed
> ----------------------------------------------------------------------------------------------
>
> Key: SENTRY-1774
> URL: https://issues.apache.org/jira/browse/SENTRY-1774
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Priority: Blocker
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1774.001-sentry-ha-redesign.patch
>
>
> HMSFollower should always depend on persisted information to decide is full snapshot is needed instead of depending on in-memory information.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)