Re: [I] Failed to publish segments because of [java.lang.RuntimeException: Aborting transaction!]. (druid)

["AmatyaAvadhanula (via GitHub)" <gi...@apache.org>]

AmatyaAvadhanula commented on issue #15054:
URL: https://github.com/apache/druid/issues/15054#issuecomment-1748139074

   > When multiple replicas of ingestion tasks are running, only one replica will successfully update the metadata, and other replicas will fail. So there's no point in retrying in this case as well. It will be hard to differentiate between this case and the above issue I faced, as in both, the metadata mismatch happens because the end offset in the metadata store doesn't match the new start state.
   
   Shouldn't it be possible to distinguish such cases by looking at the metadata that is being committed?
   If the existing metadata end is less than or equal to the new commit's start, we can retry.
   Otherwise, we know that the metadata being committed is definitely invalid


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org