From issues-return-12927-archive-asf-public=cust-asf.ponee.io@sentry.apache.org Thu Feb 1 23:54:41 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 4BD08180652 for ; Thu, 1 Feb 2018 23:54:41 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3B499160C57; Thu, 1 Feb 2018 22:54:41 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 80CA5160C44 for ; Thu, 1 Feb 2018 23:54:40 +0100 (CET) Received: (qmail 77706 invoked by uid 500); 1 Feb 2018 22:54:02 -0000 Mailing-List: contact issues-help@sentry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@sentry.apache.org Received: (qmail 77684 invoked by uid 99); 1 Feb 2018 22:54:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2018 22:54:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id AC4C61A698D for ; Thu, 1 Feb 2018 22:54:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 8N4VfuSL6IE9 for ; Thu, 1 Feb 2018 22:54:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id AF29F5F2C3 for ; Thu, 1 Feb 2018 22:54:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5A6A3E0153 for ; Thu, 1 Feb 2018 22:54:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 22FAD21E86 for ; Thu, 1 Feb 2018 22:54:00 +0000 (UTC) Date: Thu, 1 Feb 2018 22:54:00 +0000 (UTC) From: "kalyan kumar kalvagadda (JIRA)" To: issues@sentry.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync and handle gaps and out-of-sequence notifications. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: -------------------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) > Fix the logic of identifying HMS out of Sync and handle gaps and out-of-sequence notifications. > ----------------------------------------------------------------------------------------------- > > Key: SENTRY-2109 > URL: https://issues.apache.org/jira/browse/SENTRY-2109 > Project: Sentry > Issue Type: Bug > Components: Sentry > Affects Versions: 2.1.0 > Reporter: kalyan kumar kalvagadda > Assignee: kalyan kumar kalvagadda > Priority: Major > Fix For: 2.1.0 > > Attachments: SENTRY-2109.001.patch, SENTRY-2109.002.patch, SENTRY-2109.003.patch, SENTRY-2109.004.patch, SENTRY-2109.005.patch, SENTRY-2109.006.patch, SENTRY-2109.007.patch, SENTRY-2109.008.patch, SENTRY-2109.009.patch, SENTRY-2109.010.patch, SENTRY-2109.010.patch, SENTRY-2109.011.patch, SENTRY-2109.012.patch, SENTRY-2109.012.patch, SENTRY-2109.012.patch, Screenshot_HMS_NOTIFICATION_LOG.png > > > Currently HMSFollower proactively checks if sentry is out of sync with HMS and initiates full snapshot, if needed. > There will be false positives with the current logic if there are gaps in the event-id in the notification log sequence. > This jira is aimed at making that logic robust. -- This message was sent by Atlassian JIRA (v7.6.3#76005)