Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

Expand readiness check to check peer count and sync state #1568

Merged
merged 4 commits into from
Jun 18, 2019

Conversation

ajsutton
Copy link
Contributor

PR description

Readiness check now by default requires a peer to be connected and the node to be within 2 blocks of its best peer (2 block tolerance allows for the delays that can incur with receiving and importing blocks after sync is complete).

No peers are required if p2p is disabled.

Query params can be used to adjust the number of peers required and number of blocks tolerance to be considered in sync.

…ode being in sync.

Query params can be used to adjust the number of peers required and number of blocks tolerance to be considered in sync.
…s-api

# Conflicts:
#	ethereum/jsonrpc/src/main/java/tech/pegasys/pantheon/ethereum/jsonrpc/health/ReadinessService.java
#	ethereum/jsonrpc/src/main/java/tech/pegasys/pantheon/ethereum/jsonrpc/internal/methods/NetPeerCount.java
@ajsutton ajsutton requested a review from AbdelStark June 18, 2019 05:48
Copy link
Contributor

@AbdelStark AbdelStark left a comment

Choose a reason for hiding this comment

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

Ltgm

@ajsutton ajsutton merged commit 0e4f596 into PegaSysEng:master Jun 18, 2019
@ajsutton ajsutton deleted the readiness-api branch June 18, 2019 09:32
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.

2 participants