You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@dolphinscheduler.apache.org by "tasier (via GitHub)" <gi...@apache.org> on 2025/07/09 06:23:50 UTC

Re: [PR] [Bug][Master]serial_wait strategy workflow unable to wake up [dolphinscheduler]

tasier commented on PR #15270:
URL: https://github.com/apache/dolphinscheduler/pull/15270#issuecomment-3051286299

   💥 Issue Summary
   We observed a case of duplicate process instance creation due to concurrent command consumption across masters.
   
   🧪 Root Cause
   The method performTransactionalUpsert is executed within a new transaction, which does not participate in the caller's transactional context.
   
   A slot reallocation caused the same command to be consumed by two different master nodes simultaneously.
   
   Both masters attempted to delete the command concurrently:
   
   One deletion succeeded.
   
   The other failed due to the record already being removed.
   
   Despite the deletion conflict, both transactions independently persisted a process instance into MySQL, resulting in duplicate instances.


-- 
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@dolphinscheduler.apache.org

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