-
Notifications
You must be signed in to change notification settings - Fork 7
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
Explorer crashes when requesting an address with too many transactions #379
Comments
Investigation shows the host os did not go down, but OOM killed server processes before killing the tfchain daemon. An active ssh connection also hung for about 10 mins before eventually recovering, though logs do not show why this happened |
Currently the server handles the load fine (with curl). cpu about 30-40 %. Memory is also more than fine. The response for the call causing the daeomon to be OOM'd returns about 252MB worth of json. Another call currently returning about 520MB worth of json also seems to run fine |
pfew, 520 MB of json for an http call, if it were only the website, we could easily add paging but I'm afraid of the Mobicage wallet. |
Such huge amounts is only a problem for block creator wallets. No block creator wallet is used by a Mobicage wallet user. And we know for sure it won't be used ever. Paginating for the explorer could also be done, but I prefer to not spent more effort on the old explorer it until we know for sure we want to keep that alive. For now I am of the opinion we want to migrate to a new explorer as soon as possible. But I guess we can agree on those things by the end of this week, beginning of next week, after we played all well enough and iterated on the new explorer MVP. |
The caddy logs show that around the time the explorer crashed a lot of hash lookups came in simultaniously:
Source IP removed |
Regardless of the new explorer, paging does not seem like a bad idea |
Even crasges the host os
The text was updated successfully, but these errors were encountered: