[HIVE-19219] Incremental REPL DUMP should throw error if requested events are cleaned-up.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.1.0, 3.0.0
• Component/s: HiveServer2, repl
• Labels: DR pull-request-available replication
• Target Version/s: 3.0.0
• Assignee: Sankar Hariappan
• Reporter: Sankar Hariappan
• Created: 16/Apr/18 06:08
• Updated: 22/May/18 23:13
• Resolved: 23/Apr/18 04:31

Description

This is the case where the events were deleted on source because of old event purging and hence min(source event id) > target event id (last replicated event id).

Repl dump should fail in this case so that user can drop the database and bootstrap again.

Cleaner thread is concurrently removing the expired events from NOTIFICATION_LOG table. So, it is necessary to check if the current dump missed any event while dumping. After fetching events in batches, we shall check if it is fetched in contiguous sequence of event id. If it is not in contiguous sequence, then likely some events missed in the dump and hence throw error.

Issue Links

• links to: GitHub Pull Request #334