-
Notifications
You must be signed in to change notification settings - Fork 379
Cannot add second collator to parachain (Collation failure: timeout) #27
Comments
I began to suspect that the second collator was not syncing the previous parachain blocks because it only had a single peer (a relay chain node). I decided to add the first collator as a bootnode and then realized that the collator actually gives two node identities (probably related to #19). Adding both identities of the first collator plus the relay chain node for a total of three bootnodes, does cause the second colaltor to intermittently gain a second peer, but does not start it collating. |
At @bkchr 's suggestion (in a private chat) I removed this line https://github.com/paritytech/cumulus/blob/master/test/parachain/src/cli.rs#L86 and tried again manually specifying to first collator as a bootnode. Now the collators can peer together and sync the parachain blocks. Thus they can both author parachain blocks. |
* Create binary for cumulus testing node * Fix call to wrong method * Fix iterator bug * Add real networking to polkadot node * Allow using of file chain specs * Implement export of wasm blob and genesis state * Add parachain id to test service export * Remove debug logs * Fix main.rs * Do not use cli from polkadot-collator * Add tracing dependency * Improve cli structure * Use struct instead of enum for export commands * Add missing license header * Fix benchmark * add build-spec subcommand (#19) * add build-spec subcommand * reorder args * Fix formatting * Add zombienet test (#26) * add migrated tests * rename test files * uncomment args and remove extra collator node * Fix indentation (#27) * add migrated tests * rename test files * uncomment args and remove extra collator node * fix identation * Review comments * Remove unwanted version changes Co-authored-by: Sebastian Kunert <[email protected]> Co-authored-by: Javier Viola <[email protected]>
Following the instructions in the readme (along with the workaround described in #25). I'm able to start a collator and register it with the relay chain.
I then try to start a second collator by running the same command with a different data directory. The first collator continues to work as well as it ever did (see #26). But the second collator is not able to collate. It give the log message
Collation failure: timeout
.Full logs:
The text was updated successfully, but these errors were encountered: