Skip to content
This repository was archived by the owner on Aug 2, 2022. It is now read-only.

Fix SHIP block delay - develop - #8927

Merged
heifner merged 1 commit into
developfrom
fix-ship-delay-dev
Apr 18, 2020
Merged

heifner merged 1 commit into
developfrom
fix-ship-delay-dev

Conversation

@heifner

@heifner heifner commented Apr 9, 2020 •

Copy link
Copy Markdown
Contributor

Change Description

  • Fix for state_history_plugin sending blocks out on a one block delay (500ms).
  • Use block_state of accepted_block signal instead of chain.head_block_num() as head is not updated at the time of the signal.
  • Result last_irreversible.block_num & last_irreversible.block_id still lags by 500ms even with this change. See state_history_plugin LIB notification lags LIBΒ #8951.

Consensus Changes

  • Consensus Changes

API Changes

  • API Changes

Documentation Additions

  • Documentation Additions

@heifner
heifner requested review from kj4ezj and tbfleming April 9, 2020 00:56
@tbfleming

Copy link
Copy Markdown
Contributor

Is there any possibility of reentering ship (e.g. a socket event) between on_accepted_block and the head being updated?

@kj4ezj kj4ezj left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automation was able to verify that this pull request eliminated the unexpected 500 millisecond delay we were experiencing in our stack. Great work, and thanks for the incredibly fast turnaround time!!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants