Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

mysql unack cause sub_workflow executed twice

See original GitHub issue

processAllUnacks schedule thread set popped=false before this message was acked by SystemTaskExecutor. below are timeline:

2020-09-07 17:41:07.025 insert new sub_workflow task
2020-09-07 17:41:07.095 thread A poll task and got one
2020-09-07 17:41:07.148 thread B pool task and got the same one
2020-09-07 17:41:08.113 thread A set popped = true
2020-09-07 17:41:08.142 QueueDao Scheduler set popped = false
2020-09-07 17:41:08.168 thread B set popped =true
2020-09-07 17:41:08.249 thread A remove message

I don’t understand this sql : UPDATE queue_message SET popped = false WHERE popped = true AND TIMESTAMPADD(SECOND,60,CURRENT_TIMESTAMP) > deliver_on should it be TIMESTAMPADD(SECOND,-60,CURRENT_TIMESTAMP) > deliver_on? not add but minus?

@apanicker-nflx

Issue Analytics

State:
Created 3 years ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

rickfishcommented, Sep 18, 2020

@HenryLauu @apanicker-nflx @deluxor I created PR #1875 to fix this. Unfortunately, it caused the MySQLQueueDAOTest.processUnacksTest to fail. I will have to look into it.

0reactions

HenryLauucommented, Sep 18, 2020

Hello @rickfish @apanicker-nflx this is obviously concurrent bug which need to be fixed. Please make a consideration.