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

Block close issue #86

Open
SurfingNerd opened this issue Jun 26, 2021 · 1 comment
Open

Block close issue #86

SurfingNerd opened this issue Jun 26, 2021 · 1 comment

Comments

@SurfingNerd
Copy link
Collaborator

Setup

1 Moc + 6 Nodes + 1 RPC Node.
Started with 7, switched contract setting to 4 Validators.
1 Node got flagged as unavailable, because it could not write parts of it's transactions.
This leaves 5 potential validators .
4 Nodes got selected as a pending validator, but they are unable to write there ACKS (reason unknown, not part of this issue)

expected behavor:

All 4 Nodes get flagged as unavailable, leaving 1 available node behind that becomes the one and only pending validator.
The one node that is able to take over, is also a current node.

actual behavior:

The contract call crashes.

@SurfingNerd SurfingNerd changed the title Block close issue with backup node Block close issue Jul 8, 2021
@SurfingNerd
Copy link
Collaborator Author

SurfingNerd commented Jul 8, 2021

could reproduce the issue with the following setup:
new feature automatic sweet spot targeting is active.
had a testnet running well with 6 nodes for a while.
because of the sweet spot rule, it always just picks 4 random nodes.
i added on purpuse 1 additional node, to have the system switching to 7 nodes,
failing it's part creation - and switching back to a new validator set of 4 / 6 nodes.

The switch to 4 nodes happened as expected,
but the nodes could not write their ACKS.

In this case, the system still would have the ability to fall back to 2 other nodes as Validators,
but instead the "reward" call seems to crash.

image
logs.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant