Add a SelectorProvider that reuses custom provider implementations.
Tasks:
- [x] Add a custom SelectorProvider.
- [x] Update Selector to utilize the custom SelectorProvider.
Changes:
The SelectorProvider fixes an issue where the static method Selector.open() would create a system-wide default SelectorProvider object whereas in our case we need a custom SelectorProvider.
This implementation utilizes ThreadLocal so that each thread can reuse the configured provider within its' own context.
The Selector code is updated to use our custom SelectorProvider from org.apache.kafka.common.network.
A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the triage label
should be removed to prevent this automation from happening again.
This PR is being marked as stale since it has not had any activity in 90 days. If you would like to keep this PR alive, please leave a comment asking for a review. If the PR has merge conflicts, update it with the latest from the base branch.
If you are having difficulty finding a reviewer, please reach out on the [mailing list](https://kafka.apache.org/contact).
If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed.
A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the triage label
should be removed to prevent this automation from happening again.
This PR is being marked as stale since it has not had any activity in 90 days. If you would like to keep this PR alive, please leave a comment asking for a review. If the PR has merge conflicts, update it with the latest from the base branch.
If you are having difficulty finding a reviewer, please reach out on the [mailing list](https://kafka.apache.org/contact).
If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed.
This pull rquest is still relevant. Could you please review it?
This PR will help us updating to more recent Kafka clients versions as we have some own SelectorProvider we use, and the integration will be much easier. Thx!
A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the triage label
should be removed to prevent this automation from happening again.