dshackle icon indicating copy to clipboard operation
dshackle copied to clipboard

Fallback when all other nodes are "SYNCING"

Open MysticRyuujin opened this issue 5 years ago • 1 comments

I'm not sure if this is the behavior I'm seeing or not, but...

I have 1 local node and 1 fallback node (Infura)

When my local node is restarted, it seems to drop back a few hundred blocks or so...so it's in the "SYCNING" stage for a little while (maybe 10 minutes?)

It seems like dshackle doesn't fallback onto the fallback node in this case. I'm not sure how to validate my suspicion? I was hoping you might know the expected behavior...

On a side note, is there a way to turn on additional logging? To see what requests are sent to what node? Thanks

MysticRyuujin avatar Sep 28 '20 16:09 MysticRyuujin

If that's the case, it's a bug. I didn't do extensive testing with fallback, but even without it the Dshackle shouldn't use a SYNCING node. I'll take a look

splix avatar Sep 28 '20 19:09 splix