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

Celery chord_unlock Loop #3126

Closed
rajadain opened this issue Jul 17, 2019 · 2 comments
Closed

Celery chord_unlock Loop #3126

rajadain opened this issue Jul 17, 2019 · 2 comments
Assignees
Labels

Comments

@rajadain
Copy link
Member

@rajadain rajadain commented Jul 17, 2019

This was always hard to recreate, but can be observed more and more post the Django Upgrade. Usually happens when a lot of Celery Tasks are fired at once, such as when Analyzing a large shape.

In the past this has been remedied by upgrading Celery.

Ensure this is really happening, and once confirmed, remedy it.

@rajadain rajadain added the tech-debt label Jul 17, 2019
@rajadain rajadain mentioned this issue Jul 17, 2019
1 of 1 task complete
@rajadain rajadain added the WPF label Jul 25, 2019
@rajadain rajadain self-assigned this Aug 5, 2019
@rajadain

This comment has been minimized.

Copy link
Member Author

@rajadain rajadain commented Aug 5, 2019

I've tried running very large shapes, subbasin on a HUC-8, drawing large custom shapes, and have been unable to reproduce the chord_unlock behavior. It is possible that the occurrences observed during the upgrade were caused by the interstitial states of the VMs, and now that everything is upgraded and provisioned the behavior is gone.

@rajadain

This comment has been minimized.

Copy link
Member Author

@rajadain rajadain commented Aug 5, 2019

Moving this to Verified until it resurfaces again.

@rajadain rajadain closed this Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.