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

Consider using a database for pool accounts mappings management on PEP server #4

Open
andreaceccanti opened this issue Nov 9, 2015 · 0 comments

Comments

@andreaceccanti
Copy link
Contributor

Currently the Argus PEP server relies on the gridmap dir as the "database" for pool account mappings.
When replicating the pep-server, the gridmap dir must be shared across NFS, and this can become a bootleneck for pep-server scalability in large sites.

The code that manages the pool account mapping should be changed to allow for a different backend for storing pool account mappings, e.g. REDIS, which maintains information in memory but can be configured to periodically persist the database on disk.

@andreaceccanti andreaceccanti changed the title PEP Server uses a database for pool accounts mappings management Consider using a database for pool accounts mappings management on PEP server Nov 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant