KAFKA-19697: Fix unregistering connectorStatusMetrics NPE if tasks fa… #20564
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PR fixed an NPE when connectorStatusMetrics unregistering task. The issue will happen if a connector has more than 1 task on one worker and these tasks fail to start. For example, if the DNS cant resolve producer URL, tasks will fail to build. If these tasks failing to start, ConnectorStatusMetricsGroup will unregister them. After first task unregistered , connectorStatusMetrics removed connector. When second task calles recordTaskRemoved(), connectorStatusMetrics is empty, so connectorStatusMetrics.get(connectorTaskId.connector()).close(); will throw NPE.
Like in method recordTaskAdded(), this fix checkes connectorStatusMetrics at the beginning of method recordTaskRemoved().