[scheduled-executor] ScheduledTaskDescriptor.stopForMigration Nullpointer #11047
Comments
Thanks for the detailed report @Batter2014 . Yes the fix should be very trivial, but I was wondering if you could share the logs as well, to see what action led to this result. Nevertheless, i will try to push a fix in a bit, but I would rather have a solid reproducer as a test. |
I don't have anything special, just two hosts with code:
When i start both of them, one after another i will always get that exception Full stack:
|
@Batter2014 I posted a fix for 3.9 which i will also backport once merged to 3.8 (the version you are using). However, I wasn't able to reproduce it not even once, and since you said that you see this always, I wanted to make sure I am not missing sth. Your finding is absolutely valid, it is just the always part that got my attention. Would you be able to share your (or part of) the Runnable code ? Also logs of the nodes would also help, to see if there is sth wrong going on during migration of things between the nodes that cause this misbehaviour. |
Guys,
i'm currently getting:
When trying to schedule the Task:
I have looked to the fix you have here (#10604) and it doesn't look safe and could cause issue i have.
You had:
And now:
Where descriptor.stopForMigration() has:
And in old code :
Which has:
This look way safer.
Nullpointer i have on 2 machines which have code you can see above.
The text was updated successfully, but these errors were encountered: