Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase session length at Rialto #1215

Closed
svyatonik opened this issue Nov 16, 2021 · 2 comments
Closed

Increase session length at Rialto #1215

svyatonik opened this issue Nov 16, 2021 · 2 comments
Labels
A-chores Something that has to be done, as part of regular maintenance Good First Issue Good for newcomers Help Wanted An external contribution is desired.

Comments

@svyatonik
Copy link
Contributor

Right now session/epoch length on Rialto is 4 blocks (around 24 seconds) - see this and this. This is one of possible reasons of why we have seen 2 test deployments stalls recently. The reason of last one was that block production has stalled (last generated block was 67 for the almost whole day) && iirc if BABE authorities fail to produce blocks for 2 sessions, it stalls. The reason is maybe our overloaded test deployments machine && short session time.

The suggestion is to increase session time (e.g. x2) && see if it helps. We shall not make session on Rialto too long, because (iirc) it affects parachain onboarding time.

@svyatonik svyatonik added Good First Issue Good for newcomers Help Wanted An external contribution is desired. A-chores Something that has to be done, as part of regular maintenance labels Nov 16, 2021
@svyatonik svyatonik added this to the When Thou Have Spare Hour milestone Nov 16, 2021
@svyatonik
Copy link
Contributor Author

Just got this locally and the error message is:

rialto-alice:  �[2m2021-11-17 13:24:36.001�[0m �[33m WARN�[0m tokio-runtime-worker babe: Unable to fetch epoch data at block 0x4601cd64aa1d49d696a13c48a342a16e72c42f77af61be88639fc59d352664fe: InvalidAuthoritiesSet    
rialto-alice:  �[2m2021-11-17 13:24:36.049�[0m �[33m WARN�[0m tokio-runtime-worker sync: � Verification failed for block 0xb8a5a2abcc9dff2c72e5d8caf18ceaff7283055cc2a7e34c94463ae9f09ae25c received from peer: 12D3KooWSEpHJj29HEzgPFcRYVc5X3sEuP3KgiUoqJNCet51NiMX, "Could not fetch epoch at 0x4601cd64aa1d49d696a13c48a342a16e72c42f77af61be88639fc59d352664fe"    
...
rialto-alice:  �[2m2021-11-17 13:24:36.057�[0m �[33m WARN�[0m tokio-runtime-worker sync: � Verification failed for block 0xb8a5a2abcc9dff2c72e5d8caf18ceaff7283055cc2a7e34c94463ae9f09ae25c received from peer: 12D3KooWP2mdXenJaZ4ngNrddwMaFBvnJcPuCkixmbCwybxzKvGK, "Could not fetch epoch at 0x4601cd64aa1d49d696a13c48a342a16e72c42f77af61be88639fc59d352664fe"    

@svyatonik
Copy link
Contributor Author

Not reproduced during last 3 months => closing

svyatonik pushed a commit that referenced this issue Jul 17, 2023
Bumps [nix](https://github.com/nix-rust/nix) from 0.24.0 to 0.24.1.
- [Release notes](https://github.com/nix-rust/nix/releases)
- [Changelog](https://github.com/nix-rust/nix/blob/master/CHANGELOG.md)
- [Commits](nix-rust/nix@v0.24.0...v0.24.1)

---
updated-dependencies:
- dependency-name: nix
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-chores Something that has to be done, as part of regular maintenance Good First Issue Good for newcomers Help Wanted An external contribution is desired.
Projects
None yet
Development

No branches or pull requests

1 participant