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

Zebra lags behind the best tip on testnet #1941

Closed
teor2345 opened this issue Mar 25, 2021 · 0 comments · Fixed by #1950
Closed

Zebra lags behind the best tip on testnet #1941

teor2345 opened this issue Mar 25, 2021 · 0 comments · Fixed by #1950
Labels
A-rust Area: Updates to Rust code C-bug Category: This is a bug I-hang A Zebra component stops responding to requests I-slow Problems with performance or responsiveness S-needs-investigation Status: Needs further investigation
Milestone

Comments

@teor2345
Copy link
Contributor

Version

zebrad 1.0.0-alpha.5 with PR #1940

Platform

Linux ... 5.4.96 #1-NixOS SMP Sun Feb 7 14:35:50 UTC 2021 x86_64 GNU/Linux

Description

Testnet instances lag a few hundred blocks behind the tip synced by zcashd.

The zcashd tip is 1338659, and the Zebra tip is 1338519, a difference of 140 blocks.

We've had this bug before, it's possibly due to either network code hangs or peer issues (#1905), or the small number of peers on testnet (#704). I haven't seen it happen on mainnet since the late 2020 / early 2021 network fixes.

Commands

zebrad start with an epemeral testnet config with some local peers

Logs

Mar 25 17:17:05.551  INFO {zebrad="98726b0c" net="Test"}:peer{addr=127.0.0.1:38233}:msg_as_req{msg=getblocks}:state: zebra_state::service: responding to peer GetBlocks or GetHeaders final_height=Height(1338519) response_len=0 chain_tip_height=Height(1338519) stop_height=None intersection_height=Some(Height(1338519))
Mar 25 17:17:07.593  INFO {zebrad="98726b0c" net="Test"}:sync: zebrad::components::sync: exhausted prospective tip set
Mar 25 17:17:07.593  INFO {zebrad="98726b0c" net="Test"}:sync: zebrad::components::sync: waiting to restart sync timeout=61s
Mar 25 17:18:08.595  INFO {zebrad="98726b0c" net="Test"}:sync: zebrad::components::sync: starting sync, obtaining new tips
Mar 25 17:18:08.595  INFO {zebrad="98726b0c" net="Test"}:sync:obtain_tips:state: zebra_state::util: created block locator tip_height=Height(1338519) min_locator_height=1338420 locators=[Height(1338519), Height(1338518), Height(1338517), Height(1338515), Height(1338511), Height(1338503), Height(1338487), Height(1338455), Height(1338420)]
Mar 25 17:18:08.595  INFO {zebrad="98726b0c" net="Test"}:sync:obtain_tips: zebrad::components::sync: trying to obtain new chain tips tip=block::Hash("003e1b484c2c14ef29691c3640a7d5d66c4454029d7fb731a5b7c5111bad6fc4")
Mar 25 17:18:12.554  INFO {zebrad="98726b0c" net="Test"}:peer{addr=127.0.0.1:38233}:msg_as_req{msg=getblocks}:state: zebra_state::service: responding to peer GetBlocks or GetHeaders final_height=Height(1338519) response_len=0 chain_tip_height=Height(1338519) stop_height=None intersection_height=Some(Height(1338519))
Mar 25 17:18:14.597  INFO {zebrad="98726b0c" net="Test"}:sync: zebrad::components::sync: exhausted prospective tip set
Mar 25 17:18:14.597  INFO {zebrad="98726b0c" net="Test"}:sync: zebrad::components::sync: waiting to restart sync timeout=61s
@teor2345 teor2345 added C-bug Category: This is a bug A-rust Area: Updates to Rust code S-needs-triage Status: A bug report needs triage S-needs-investigation Status: Needs further investigation P-Medium I-hang A Zebra component stops responding to requests I-slow Problems with performance or responsiveness labels Mar 25, 2021
@mpguerra mpguerra removed the S-needs-triage Status: A bug report needs triage label Apr 6, 2021
@mpguerra mpguerra added this to the 2021 Sprint 6 milestone Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-rust Area: Updates to Rust code C-bug Category: This is a bug I-hang A Zebra component stops responding to requests I-slow Problems with performance or responsiveness S-needs-investigation Status: Needs further investigation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants