PANKAJ KUMAR 047c7340ab Adding retries to update the metadata store instead of failure (#15141) ... Currently, If 2 tasks are consuming from the same partitions, try to publish the segment and update the metadata, the second task can fail because the end offset stored in the metadata store doesn't match with the start offset of the second task. We can fix this by retrying instead of failing. AFAIK apart from the above issue, the metadata mismatch can happen in 2 scenarios: - when we update the input topic name for the data source - when we run 2 replicas of ingestion tasks(1 replica will publish and 1 will fail as the first replica has already updated the metadata). Implemented the comparable function to compare the last committed end offset and new Sequence start offset. And return a specific error msg for this. Add retry logic on indexers to retry for this specific error msg. Updated the existing test case.		2024-01-10 12:30:54 +05:30
..
src	Adding retries to update the metadata store instead of failure (#15141)	2024-01-10 12:30:54 +05:30
pom.xml	Prepare master for Druid 29 (#15121)	2023-10-11 10:33:45 +05:30