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

Less impact on web server when using supervisor export script #30

Open
chfoo opened this issue Feb 18, 2015 · 0 comments
Open

Less impact on web server when using supervisor export script #30

chfoo opened this issue Feb 18, 2015 · 0 comments

Comments

@chfoo
Copy link
Member

chfoo commented Feb 18, 2015

Right now the supervisor export script sets a sentinel flag file telling the web server to return status 512, drains the results table into a text file, removes the flag file, sorts the text file, formats, and then uploads. During this time, the web service is unavailable for 30 minutes.

Instead, it could slowly drain the results table into another database to avoid blocking the web server and then continue from there. It would also provide some way of resuming in case of failure.

Edit: It could also just check for the current export json file, drain into appending the text file, but allow resuming in case of failure.

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

No branches or pull requests

1 participant