[FLUME-2983] Handle offset migration in the new Kafka Source

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.7.0
• Assignee: Grant Henke
• Reporter: Grant Henke
• Created: 30/Aug/16 15:58
• Updated: 01/Sep/16 02:59
• Resolved: 01/Sep/16 02:00

Description

Similar to FLUME-2972, Offsets tracking the position in Kafka consumers change from using zookeeper for offset storage to Kafka when moving from 0.8.x to 0.9.x.
FLUME-2821 makes the client change in the Kafka Source but does not ensure existing offsets get migrated in order to continue consuming where it left off.
Flume should have some automated logic on startup to check if Kafka offsets exist, if not and migration is enabled (by default) then copy the offsets from Zookeeper and commit them to Kafka.

This change should also fix the backwards incompatibility caused by removing the zookeeperConnect property. The bootstrap can be looked up if zookeeperConnect is used.

Issue Links

• blocks: FLUME-2980 Automated concurrent Kafka offset migration test
• is related to: FLUME-2985 Consider consolidating Kafka offset migration code
• relates to: FLUME-2821 Flume-Kafka Source with new Consumer
• relates to: FLUME-2972 Handle offset migration in the new Kafka Channel
• links to: Review Board