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

userExecutor usage and internalExecutor usages mixed up #8651

Closed
ihsandemir opened this issue Aug 2, 2016 · 1 comment
Closed

userExecutor usage and internalExecutor usages mixed up #8651

ihsandemir opened this issue Aug 2, 2016 · 1 comment

Comments

@ihsandemir
Copy link
Contributor

@ihsandemir ihsandemir commented Aug 2, 2016

Client near cache implementation uses userExecutor which is also used by other purposes such as making callbacks to lifecycle listeners. A client may block operation of near cache updates by a slow lifecycle listener. This needs to be addressed.

@sancar sancar self-assigned this Feb 14, 2017
@sancar sancar added this to the 3.8.1 milestone Feb 14, 2017
@sancar sancar added the Type: Defect label Feb 14, 2017
@sancar sancar removed their assignment Feb 14, 2017
@sancar
Copy link
Member

@sancar sancar commented Mar 10, 2017

This change seems like caused by a refactoring done here #7939

It seems like it does not affect just near cache but almost all executor usages. Changing the title accordingly.

@sancar sancar changed the title Client Near cache userExecutor usage userExecutor usage and internalExecutor usages mixed up Mar 10, 2017
@sancar sancar self-assigned this Mar 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

3 participants
You can’t perform that action at this time.