Skip to content
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.

Listener on Rinkeby issues very large volume of web3 requests #4157

Closed
franckc opened this issue Dec 17, 2019 · 3 comments
Closed

Listener on Rinkeby issues very large volume of web3 requests #4157

franckc opened this issue Dec 17, 2019 · 3 comments
Labels
bug Something isn't working as intended listener Event listener P2 Small number of users are affected, major cosmetic issue
Milestone
🛍 11/20/19-12/3/19

Comments

@franckc
Copy link
Contributor

franckc commented Dec 17, 2019

We had an instance on Rinkeby of the listener issuing 195 qps worth of web3 requests (mostly eth_getBlockByNumber and eth_blockNumber calls).

Here is an excerpt of the logs at the time it was happening:
Screen Shot 2019-12-17 at 2 30 34 PM

Restarting the process fixed it and the web3 calls volume went down to about 3qps.
@franckc franckc added bug Something isn't working as intended P2 Small number of users are affected, major cosmetic issue listener Event listener labels Dec 17, 2019
@franckc
Copy link
Contributor Author

franckc commented Dec 17, 2019

CC @mikeshultz in case he has any insights into this...

@franckc
Copy link
Contributor Author

franckc commented Dec 17, 2019

Actually after further investigation it could have been that the testing we did on T3 caused this. Still looking...

@franckc
Copy link
Contributor Author

franckc commented Dec 18, 2019

Was a bug in T3 distribution. And Alchemy stats have a delay which is why shutting down T3 did not immediately get reflected in the stats making me think it was not the culprit.
Closing for now.

@franckc franckc closed this as completed Dec 18, 2019
@micahalcorn micahalcorn added this to the 🛍 11/20/19-12/3/19 milestone Jan 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working as intended listener Event listener P2 Small number of users are affected, major cosmetic issue
Projects
None yet
Milestone
🛍 11/20/19-12/3/19
Development

No branches or pull requests
2 participants
@micahalcorn @franckc