emeraldpay / emeraldpay/dshackle

Fallback when all other nodes are "SYNCING"

Open
#60 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Rust
Stars
350
Forks
57
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.