[HIVE-20349] Implement Retry Logic in HiveDruidSplit for Scan Queries

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Component/s: Druid integration
• Assignee: Nishant Bangarwa
• Reporter: Nishant Bangarwa
• Created: 09/Aug/18 12:35
• Updated: 27/Feb/24 22:23
• Resolved: 19/Sep/18 14:38

Description

while distributing druid scan query we check where the segments are loaded and then each HiveDruidSplit directly queries the historical node.
There are few cases when we need to retry and refetch the segments.

1. The segment is loaded on multiple historical nodes and one of them went down. in this case when we do not get response from one segment, we query the next replica.
2. The segment was loaded onto a realtime task and was handed over, when we query the realtime task has already finished. In this case there is no replica. The Split needs to query the broker again for the location of the segment and then send the query to correct historical node.

This is also the root cause of failure of druidkafkamini_basic.q test, where the segment handover happens before the scan query is executed.

Note: This is not a problem when we are directly querying Druid brokers as the broker handles the retry logic.

Issue Links

• causes: HIVE-19552 Enable TestMiniDruidKafkaCliDriver#druidkafkamini_basic.q
• links to: review link