[SENTRY-2113] MSentryHmsNotification should also hold the notification hash

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Component/s: Sentry
• Assignee: Krishna Kalyan
• Reporter: Krishna Kalyan
• Created: 02/Jan/18 16:44
• Updated: 08/Jan/18 17:17

Description

Currently MSentryHmsNotification is holding notification-id but it should be extended to hold the notification hash.

We are currently using MSentryPathChange to get the notification hash but this information is not reliable as MSentryPathChange will store all the notifications the HMSFollower gets from HMS. MSentryPathChange will only store the notifications that needed to sync HDFS ACL's.

Unlike MSentryPathChange, MSentryHmsNotification is designed to record the information of all the notifications that HMSFollower receives from HMS.

Issue Links

• is depended upon by: SENTRY-2109 Fix the logic of identifying HMS out of Sync and handle gaps and out-of-sequence notifications.