-
Notifications
You must be signed in to change notification settings - Fork 823
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
KeyError: 10 in io-loop #789
Comments
Hi @phoet, |
created a gist with the complete stack trace: https://gist.github.com/phoet/7bb0b898b59e4603e6a00e95278a4d63 |
@phoet does this still happen to you with a recent version? |
unfortunately, i'm not working on that project any more. maybe @sbstjn want's to take over? |
Seems like a file descriptor is being closed, ( the fd 10 ) but is still registered in tornado. |
yeah but isn't this a tornado interna part or are we messing with tornado? It doesn't look like (starting the ioloop and using 2 callbacks, but one had an issue which is fixed in #808 ) |
What is raising the KeyError is |
what I mean was: is this a thumbor bug or a tornado bug? :) |
@savar Not sure, probably a tornado bug but might be induced by Thumbor. Thumbor relies on so many third-party dependencies it's hard to know why something fails. |
so we need more information from @sbstjn which version is he using.. except the threadpool part I don't see any chance to mess around with tornado (but I didn't check everything) |
We have not seen the |
so @sbstjn should we close the issue and re-open it in case you have this issue again? |
Yes, feel free to close the issue :) |
thx anyways |
This link provide good details about this issue: |
we are running a recent version of thumbor (f813c18) and once and a while we see huge stack traces where i don't have a clue for how to debug it. unfortunately we don't see which image is causing this as we have many thousand requests on that app.
it looks like this is killing the whole tornado io-loop, wreak havoc and leaving the instance unhealthy.
The text was updated successfully, but these errors were encountered: