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

Investigation of double distribution occurance #4783

Closed
cielf opened this issue Nov 14, 2024 · 8 comments
Closed

Investigation of double distribution occurance #4783

cielf opened this issue Nov 14, 2024 · 8 comments
Assignees

Comments

@cielf
Copy link
Collaborator

cielf commented Nov 14, 2024

Summary

Investigation of the issue covered in the support log at Nov 12, 2024, 11:17.

Please check into the logs and see if there are any further clues there.

We had thought this was a double-click on the distribution confirmation, but there has been a fix put in to cover off that situation.

Things to consider

No response

Criteria for Completion

Investigate and report back to the Sunday planning meeting.

@dorner
Copy link
Collaborator

dorner commented Nov 17, 2024

I am definitely seeing multiple requests coming in at the exact same time.

This seems to be because the request timed out. I'm seeing a request taking over 48 seconds and nginx returns an error 499. I'll bet that this causes the button to re-enable and the user clicks again at that point.

We need to fix our slow queries.

EDIT: Validated that when this happens the user actually gets an error screen. They can then click back and go back to the request page and do everything again since at that point the request hasn't been fulfilled yet. That seems to be what happened.

@dorner
Copy link
Collaborator

dorner commented Nov 17, 2024

I'm wondering if this has something to do with vacuuming - maybe it happens to be going on at that exact moment.

@cielf
Copy link
Collaborator Author

cielf commented Nov 18, 2024

Noting that during the planning meeting we determined that vacuuming wasn't happening at the time of the issue.

Copy link
Contributor

This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.

Copy link
Contributor

Automatically unassigned after 7 days of inactivity.

@cielf cielf removed the stale label Dec 28, 2024
Copy link
Contributor

This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.

@github-actions github-actions bot added the stale label Jan 28, 2025
Copy link
Contributor

github-actions bot commented Feb 5, 2025

Automatically unassigned after 7 days of inactivity.

@dorner
Copy link
Collaborator

dorner commented Feb 7, 2025

Going to close this for now since the weirdo query times are still showing up on Newrelic but don't seem to affect app times. If we see this problem again, we can open a new issue for it.

@dorner dorner closed this as completed Feb 7, 2025
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

2 participants