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
[BUG] JobRunrException: MigrateFromV6toV7Task #1036
Comments
We'll try to reproduce it this week. First we thought it caused no problem, but later we found that no job could have been started after the exception occurred. We managed to delete the old batch jobs from the db, and it solved the problem. |
Hi @uben01, is it possible to share the JSON of the BatchJob causing the issue with us? |
Sadly we only deleted the related jobs from the db, but I'll try to reproduce the issue later |
We were not able to reproduce it, but we found a different stacktrace as well. It might shed some light to the events: Some additional context, that we have multiple pods running the same application. There might have been a problem with migrations running in a wrong order.
|
@uben01 I don't think this is related to the previous issue. The latter issue is probably caused by the fact that not all your pods are on v7 yet (as pointed out by other users):
Regarding the initial issue; could you tell us which version of JobRunr you were running in production? |
We were upgrading from v6.3.5 to v7.1.1 |
Do you have a backup of your db before the upgrade? That way, it should be reproducible? |
We just double checked and we can't see what is happening to be honest. We have an integration test for this exact scenario which is green. If you encounter it again, feel free to reopen but we do need a copy of the JSON of the BatchJob in such a case. Then we should be able te reproduce the issue really easy. |
JobRunr Version
7.1.1
JDK Version
OpenJDK 17.0.11
Your SQL / NoSQL database
Postgres 14
What happened?
After a successful stage deploy, we've got an exception from the production.
We've got no idea what the relevant parts are from the code, but everything seems to be normal after the exception.The production deployment broke, and no jobs could be started until the related jobs were deleted from the db.
How to reproduce?
Relevant log output
The text was updated successfully, but these errors were encountered: