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

Introduce configuration options for ClusterCommandExecutor via Jedis #2166

Open
he7g opened this issue Sep 15, 2021 · 2 comments
Open

Introduce configuration options for ClusterCommandExecutor via Jedis #2166

he7g opened this issue Sep 15, 2021 · 2 comments
Labels
type: enhancement A general enhancement

Comments

@he7g
Copy link

he7g commented Sep 15, 2021

see

ThreadPoolTaskExecutor threadPoolTaskExecutor = new ThreadPoolTaskExecutor();

why use coreSize 1 by default? when exec unlink keys, will use the executor, it's single thread, so so so slowly!!

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Sep 15, 2021
@mp911de mp911de changed the title why ClusterCommandExecutor executor coreSize use 1? Why ClusterCommandExecutor executor coreSize use 1? Sep 15, 2021
@mp911de mp911de changed the title Why ClusterCommandExecutor executor coreSize use 1? Introduce configuration options for ClusterCommandExecutor via Jedis Sep 20, 2021
@mp911de
Copy link
Member

mp911de commented Sep 20, 2021

We should also move off the thread pool when using Lettuce as lettuce is async out of the box.

@mp911de mp911de added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 20, 2021
@he7g
Copy link
Author

he7g commented Sep 22, 2021

Good, I agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

3 participants