Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

With the sentry node setup, forging node do not get block on time #6300

Closed
shuse2 opened this issue Apr 6, 2021 · 1 comment · Fixed by #6328
Closed

With the sentry node setup, forging node do not get block on time #6300

shuse2 opened this issue Apr 6, 2021 · 1 comment · Fixed by #6328

Comments

@shuse2
Copy link
Collaborator

shuse2 commented Apr 6, 2021

Expected behavior

With sentry nodes setup, the forging node behind the sentry nodes should get block update on time.

Actual behavior

The forging node do not get blocks on time occasionally.

Steps to reproduce

Start 2 sentry node and run 1 forging node behind, and check if forging node is always up to date with height

Which version(s) does this affect? (Environment, OS, etc...)

5.0.4-

@shuse2
Copy link
Collaborator Author

shuse2 commented Apr 8, 2021

Reproduced on betanet with

{
  "network": {
    "seedPeers": [],
    "fixedPeers": [
      {
              "ip": "51.15.39.236",
              "port": 5001
      },
      {
              "ip": "168.119.152.120",
              "port": 5001
      }
    ],
    "maxOutboundConnections": 2,
    "maxInboundConnections": 0
  }
}

Propagation seems unstable if it only has 2 outgoing connection

@shuse2 shuse2 changed the title With the sentry node setup, forging information do not get block on time With the sentry node setup, forging node do not get block on time Apr 12, 2021
@sridharmeganathan sridharmeganathan added this to the Sprint 42 milestone Apr 12, 2021
shuse2 added a commit that referenced this issue Apr 19, 2021
With the sentry node setup, forging node do not get block on time - Closes #6300
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants