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

KeyspaceManager is not threadsafe #66

Open
andrewswan opened this issue Oct 10, 2012 · 0 comments
Open

KeyspaceManager is not threadsafe #66

andrewswan opened this issue Oct 10, 2012 · 0 comments

Comments

@andrewswan
Copy link
Contributor

As discussed on the Google group, the KeyspaceManager class is not threadsafe, by virtue of extending ManagerOperand, which uses a single class-scoped IConnection.

Making KeyspaceManager threadsafe would make it much more usable in multi-threaded environments, e.g. when listing all keyspaces currently defined in the cluster. Currently the workaround is to instantiate a new KeyspaceManager for each invocation, which is expensive.

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

No branches or pull requests

1 participant