Comments (2)
Thanks for this report too :)
It seems that this is an effect of increasing the gossip_interval
in the config to 300_000
(i.e. 5 minutes). We overlooked the fact that the node's consensus component requires there to have been some consensus messages within 5 minutes of the component being constructed or else it deems itself non-functioning and kills the node.
To receive consensus messages, the node must have some incoming connections (the peers listed via the /status
endpoint could be incoming or outgoing ones). To get an incoming connection, the node must gossip its public address, and remote peers receiving this will then try and connect to it.
By only having peers gossip their addresses on a 5 minute interval, there's no chance for a node joining the network to establish incoming connections in time to satisfy the consensus requirement.
The simplest fix (which worked when we tried on one of our own nodes) is to reduce the config setting back down. We opted to change it to:
gossip_interval = 120_000
Manually making that config change and restarting the node should allow it to join successfully.
I'll leave this issue open until we fix that setting in our release packages.
from casper-node.
Fixed by #707
from casper-node.
Related Issues (20)
- Re-examine channel splits
- Close connection on ban HOT 2
- Tune Juliet networking settings
- Evaluate difficulty of threading through request/response pattern from networking to rest of the system [ Timeboxed ] HOT 1
- Remove stale metrics
- Remove P dependency of networking component
- Ensure that networking Tickets are threaded through the node as well as possible
- The DeployConfig chainspec setting for max dependencies should be removed along with all mentions of same.
- Cleanup RPC status and peers endpoints
- Add a test validating a block without any deploys, but with a signature that cannot be fetched
- Error encountered while running a freshly compiled NCTL network from feat-2.0.
- Rust toolchain failure observed with CEP18 contract.
- Fix Juliet test HOT 1
- Add a flag for enabling speculative exec into the binary port and disable it by default
- Add a dictionary item request to the binary port
- Move ReactorState from casper-types to the node and replace it with a String in NodeStatus
- Rename Transform types
- Review max_request_size_bytes and max_response_size_bytes binary port config
- Send custom error message payloads in the binary port
- Investigate potentially flaky Highway Zug rewards tests
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from casper-node.