emeraldpay
I don't think role: fallback is working correctly anymore
I am using Infura and a few other providers with role: fallback and disable-validation: true but I'm seeing a lot of queries being sent to these nodes despite the fact that my local (non-fallback) nodes are operating just fine.
In the same time frame over on Alchemy I've got this:
I think disable-validation: true is working, based on the API calls being sent, but role: fallback seems to not be honored here.
Hi @MysticRyuujin, sorry for the delay. I believe it's honored actually. I also use Infura as a backup and I see a dramatic drop of requests stat when role: fallback is enabled.
Though I agree it still makes more requests that it should. It seems it fetches a block data once Dshackle sees block header through websockets. In this case it the request usually go to a first upstream that produced that notification, and that may be fallback node. Also it seems there are few other cases when an internal request may go to a fallback upstream directly. I'm going to improve those parts.
Ah, so it's likely the WebSocket notifications causing most of it. Good to know. I can just disable that on the quotad providers! I could go back test, but I'll leave it alone 🙂