[SENTRY-1721] Unit test failures in TestSentryStore due to changeId miscount

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: Sentry
• Labels: test
• Flags: Important
• Assignee: Na Li
• Reporter: Na Li
• Created: 25/Apr/17 20:52
• Updated: 24/Jul/17 14:51
• Resolved: 27/Apr/17 23:57

Description

We encounter multiple incidents of unit test failures. They are mainly TestSentryStore.testPrivilegesWithPermUpdate and TestPrivilegeOperatePersistence.testGrantPrivilegeExternalComponentInvalidConf

These tests fail more often when HMSFollower is created after SentryService.Start() is called. And less frequent when HMSFollower is created in SentryService constructor. Need investigation on whether this is just a bug in test cases or reflect issues in synchronization between Sentry HMS metastore.

Issue Links

• blocks: SENTRY-1722 Create HMSFollower when SentryService.Start() is called
• Parent Feature: SENTRY-872 Uber jira for HMS HA + Sentry HA redesign
• relates to: SENTRY-1587 Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change
• links to: Review Board Link for this case