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.

Sign up for GitHub

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

Jump to bottom

[Ropsten] Unable to Get Traces #15

Open
patrick-ogrady opened this issue Nov 23, 2020 · 1 comment
Open

[Ropsten] Unable to Get Traces #15

patrick-ogrady opened this issue Nov 23, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@patrick-ogrady
Copy link
Contributor

When running rosetta-ethereum on Ropsten, I ran across an error where I could not get traces for certain blocks:
image

This is 99% likely to be caused by too short of a trace timeout and/or geth response timeout (where response time is elevated due to concurrent fetches).
@patrick-ogrady patrick-ogrady added the bug Something isn't working label Nov 23, 2020
@patrick-ogrady patrick-ogrady changed the title [Ropsten] Missing Traces [Ropsten] Unable to Get Traces Nov 23, 2020
@patrick-ogrady
Copy link
Contributor Author

patrick-ogrady commented Nov 23, 2020 •
edited
Loading

Previously, I was making 32 concurrent fetches. I've reduced this to 8 to see if it fixes the issue. Even with such a small concurrency, populating the trace response is consuming all CPU resources (on a 48 core box):
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Milestone
No milestone
Development

No branches or pull requests
1 participant
@patrick-ogrady