Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not inject Netty's EventLoopGroup as a primary ExecutorService #4004

Closed
dstepanov opened this issue Sep 2, 2020 · 3 comments · Fixed by #5560
Closed

Do not inject Netty's EventLoopGroup as a primary ExecutorService #4004

dstepanov opened this issue Sep 2, 2020 · 3 comments · Fixed by #5560
Assignees
Labels
priority: high High priority
Milestone

Comments

@dstepanov
Copy link
Contributor

It's caused by @Primary annotation added for default EventLoopGroup in DefaultEventLoopGroupRegistry.

Would it be possible to allow specifying something like @Primary(of = EventLoopGroup.class)? That would restrict injecting ExecutorService as a primary implementation.

@graemerocher graemerocher added the status: under consideration The issue is being considered, but has not been accepted yet label Sep 2, 2020
@jameskleeh
Copy link
Contributor

@dstepanov Can you describe what issue is being caused by the current behavior?

@dstepanov
Copy link
Contributor Author

@jameskleeh #3868 I wouldn't expect Netty executor to be injected as a default one it probably can cause some performance problems if it's used to execute long-running tasks.

@jameskleeh jameskleeh added this to the 3.0.0 milestone Mar 11, 2021
@jameskleeh
Copy link
Contributor

We will remove the primary qualifier

@graemerocher graemerocher added priority: high High priority and removed status: under consideration The issue is being considered, but has not been accepted yet labels Mar 11, 2021
@jameskleeh jameskleeh self-assigned this Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high High priority
Projects
None yet
3 participants