-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
got 2 log errors every minute in latest 1.10.x #6784
Comments
Which database do you use? See #6729, only applied to the dev branch, where it was needed to do the But, we must be careful, it seems that we still need (at least with sqlce & sql server) to do a Best. |
compact ce |
Let's revert the fix for now if it's creating another issue, and reopen the initial bug |
So I am lost, the PostreSQL fix is only on dev, can everyone repro the issue on 1.10.x ? Since which commit then? |
IT was NOT good ON 1.10 RELEASE |
So, i think the issue of @infofromca is on 1.10 but before this fix #6737 by @sfmskywalker. So, not related with #6729 only applied to dev. I mentioned #6729 in case @infofromca would use e.g a |
it has been from 1.10 to 1.10.x today. which means not relate with #6737 this is today's 1.10.x |
Oh yes, i think i understand and i can simulate the use case in last 1.10.x. So, it works as long as a lock record is acquired then deleted after the related job ended. But if a lock record is not deleted this way (this is my simulation), the following code added in #6737 will try to remove it before creating a new one:
So, if you already have a lock record, i think the issue is that we can't delete a lock record and create a new one with the same index in the same transaction. Best |
Then, because we are already in a new transaction, so i think we can add a flush after the delete. Then, it seems to work.
Best. |
@jtkech @sebastienros |
Even though Flush is usually not the solution, here it is correct. |
PR please |
If @infofromca want to do it, otherwise i can do it. |
Another solution would be to use another transaction as in the Or just an idea on the fly: not delete the record but only update the valid time. Best. |
so this give me a idea: |
The text was updated successfully, but these errors were encountered: