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

Caching Issue causing exit 139 (segmentation fault) #5

Open
GabHoo opened this issue Dec 2, 2024 · 1 comment
Open

Caching Issue causing exit 139 (segmentation fault) #5

GabHoo opened this issue Dec 2, 2024 · 1 comment

Comments

@GabHoo
Copy link

GabHoo commented Dec 2, 2024

Hi!
I am experiencing problem with old requests since they are stored somehow. This happened once when I stopped the docker container but my script was still running and kept sending requests. Later, after I restarted the server etc, my celery workers restarted from old pending requests, even if at that point, my script was not running anymore. I can see how this behavior is desirable in some situations, but in my case I would like to free the cache, and have the workers available and free when I start the container fresh.
How to do that?

Thank you for your work!

@GabHoo GabHoo changed the title Caching Issue Caching Issue causing exit 139 (segmentation fault) Dec 11, 2024
@GabHoo
Copy link
Author

GabHoo commented Dec 11, 2024

EDIT:
I also realized that when restarting, it will happens that 2 workers start working on the same document, maybe because the queue of the document from this storage is not properly handled. But because they start working on the same document (it only happens after a couple of jobs are done) they then exit with code 139, which as suggested here could be cause by trying to access memory same memory address by different processes

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

1 participant