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

Pools Still Not Recording Versions Correctly #2848

Closed
BrokenEagle opened this issue Jan 17, 2017 · 2 comments
Closed

Pools Still Not Recording Versions Correctly #2848

BrokenEagle opened this issue Jan 17, 2017 · 2 comments

Comments

@BrokenEagle
Copy link
Collaborator

BrokenEagle commented Jan 17, 2017

Referring to issue #2844.

Just tested this and it is still not recording pool versions correctly.

http://danbooru.donmai.us/pool_versions?search%5Bpool_id%5D=5205

That is a pool where the last several edits have not been recorded, including edits by myself. I attempted to remove and then readd those same posts to try to trigger a new version without any success.

I also checked the raw JSON and discovered that pool 5205 had 359 posts, whereas the latest pool version only had 356 posts.

http://danbooru.donmai.us/pools/5205.json
http://danbooru.donmai.us/pool_versions.json?search%5Bpool_id%5D=5205&limit=1

@r888888888
Copy link
Collaborator

Sorry. The postgres instance was saturated on open connections (since every web server connects to it) and so the sqs queue was backlogged. I've increased the connection limit and the queue has cleared up now.

@BrokenEagle
Copy link
Collaborator Author

Got it... just checked the above and everything seems to be corrected. Thanks for the quick response.

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

3 participants