Add Connector Name and Task ID in the Table Monitor Thread Name #1509
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.
Problem
CC-32766 - Exposing the threadIds of new threads created by the JDBC Connector apart from the task thread.
There are few other threads which are created apart from the task thread by the connector in order to monitor or perform another actions. Tracking these threads would be difficult as it cannot be identified of which connector they belong to.
In order to track these threads, it is required to have threadIds for these threads such that it would be easier to monitor them in case of any thread leaks/high resource consumption.
Solution
Add the connector name and the task Id for the newly created threads if any in the JDBC Connectors (both Source & Sink).
Does this solution apply anywhere else?
If yes, where?
Test Strategy
Testing done:
Release Plan