Update NIO event loop creation to use Netty 4.2 API #3584 #3585
+110
−6
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.
Description
This PR fixes the incomplete Netty 4.2 migration for NIO event loop creation.
After upgrading to Netty 4.2 in #3405, the NIO event loop creation in
DefaultEventLoopGroupProviderstill used the old Netty 4.1 API (new NioEventLoopGroup()), which creates event loops incompatible with applications using Netty 4.2's new IO model.Changes
NioProvider: Following the same pattern asEpollProvider,KqueueProvider, andIOUringProviderDefaultEventLoopGroupProvider: Now usesNioProvider.getResources()to create NIO event loop groupsMultiThreadIoEventLoopGroupwithNioIoHandler.newFactory()Impact
This ensures that NIO event loop creation is consistent with the other transports and compatible with Netty 4.2's new IO model. Applications using Netty 4.2 event loops will no longer encounter
IllegalStateException: incompatible event loop typeerrors when using Lettuce.Testing
Fixes #3584