Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.4.0, 3.2.4, 3.3.6, 3.5.0
-
Reviewed
Description
I found some places calling SchedulerNode#getReservedContainer to get reservedContainer (returned value) but not do sanity(not-null) check before calling internal methods of it, which can have a risk to raise NullPointerException if it's null.
Most of these places have a premise that node has reserved container a few moments ago, but may getting null by calling SchedulerNode#getReservedContainer in the next moment, since the reservedContainer can be updated to null concurrently in scheduling and monitoring(preemption) thread. So that not-null check should be done before calling internal methods of the reservedContainer.
Attachments
Issue Links
- links to