[SENTRY-1605] SENTRY-1508 need to be fixed because of Kerberos initialization issue

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.0
• Fix Version/s: 1.8.0
• Assignee: Vadim Spector
• Reporter: Vadim Spector
• Created: 20/Jan/17 23:25
• Updated: 10/Jul/17 20:19
• Resolved: 07/Feb/17 22:52

Description

SENTRY-1508 performs full Sentry HDFS sync at the construction time. Turns out, it does not work with Kerberos on, because the Hive code initialized Kerberos client only AFTER instantiating MetastorePlugin. Fix is pretty straightforward: MetastorePlugin should not attempt synchronization with Sentry from the constructor. It should rely on the housekeeping thread's SyncTask to ultimately succeed in pushing the first full update. The subtle point is that until it happens, all partial updates going through MetastorePlugin should skip Sentry notification step while keeping updating the MetastorePlugin's local cache as usual.

Issue Links

• relates to: SENTRY-1831 The MetastorePlugin SyncTask is leaking connection threads when read timed out issues are thrown
• links to: Code review link