briaugenreich commented on PR #4853: URL: https://github.com/apache/hbase/pull/4853#issuecomment-1294854365
FWIW i wonder if this invalid statue occurs due to the [connection bug](https://github.com/apache/hbase/pull/2514) that was in 2.5.0 and remediated in 2.5.1. I would think that could lead us to a weird spot where there is a task not fully initialized with a status. Here's how I got to this simple null check: Each task has a status <img width="382" alt="image" src="https://git.hubteam.com/storage/user/3299/files/4b0674aa-6477-4189-9e81-eacbc5f9ac92";> The task is implemented in two spots... looking at those two spots its only needs to have a null check in one place `MontioredRpcHandler` -> <img width="915" alt="image" src="https://git.hubteam.com/storage/user/3299/files/a857c39e-e8e9-4a54-831f-bbaebceb3c5e";> and `MonitoredTaskImpl` which is the super reference in the call above <img width="406" alt="image" src="https://git.hubteam.com/storage/user/3299/files/b939e75e-89c4-43af-b5d3-97320fbf982b";> A monitored task status is initially null... something needs to call set status <img width="672" alt="image" src="https://git.hubteam.com/storage/user/3299/files/5641543a-aab3-476f-8207-ced962d7ada8";> We can see here its done in many places and is just a string var <img width="944" alt="image" src="https://git.hubteam.com/storage/user/3299/files/36760495-1226-4779-bffa-425501ca9cf3";> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
