-
Notifications
You must be signed in to change notification settings - Fork 160
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
Large logs cause mongo to error out #129
Comments
You know I'm not even entirely convinced it's the logs being big? I was debugging the job in question today and looking at the logs for it and they really dont seem that huge. I can't share it publicly, but I pasted one into a text editor and saved it, its 489k, about 3000 log lines. Not really sure what's expected for log size, but I have a feeling the issue is less with size and more with the sort call for some reason |
I can't recall whether we ever establish indexes in Mongo. Sounds like we should, can you try adding an index on save_date and see if that makes it go away? |
We've added the index, I'll report back if it works. we're rerunning the job to get what we missed so I should know by EOD. |
Adding an index to save_date fixed it! Now the question is how do we make sure this index is added programatically to mongo (and add it to existing installations) |
Pymongo makes this really easy, it's just a one-liner to |
Forking from #76, which is the same underlying issue, but causing a different error (SMTP error there, mongo issue here)
We have one particular job that generates a large log output for one task. We started noticing that no completion email would be sent. It turns out that this error is the error that eventually caused the initial conditions for #126 by causing an exception before
_on_completion
finished.The error looks generally like this:
In case the line numbers are off because the current version of dagobah running on our server is slightly off from master, here's the ling in question (the
last_run = ...
line)And the relevant mongo code:
It seems like others with similar issues are being told to index what you're sorting, not sure if this helps:
I'm not super good with mongo so I'm just showing what I've found so far.
The text was updated successfully, but these errors were encountered: