-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fix replication tree with sharding #668
Conversation
945f553
to
5a32469
Compare
How to ? |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(develop branch latest commit -1) code + 5 Nodes + mix dev.lbench
+ Archethic.Utils.Regression.Benchmark.EndToEndValidation.plan(["127.0.0.1"],[])
+ git patch
serialization errors
No serialization error, seen with
(develop branch latest commit -1) code + prcode+ 5 Nodes + mix dev.lbench
+ Archethic.Utils.Regression.Benchmark.EndToEndValidation.plan(["127.0.0.1"],[])
+ git patch
Unit Test cases is required.
1247950
to
5d6cd59
Compare
This is used to say we don't expect minimal availability ratio per geo patch. |
36, 248, 98, 108, 241, 114, 47, 102, 176, 212>>, | ||
protocol_version: ArchethicCase.current_protocol_version() | ||
}, | ||
replication_tree: %{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we include dynamic creation of replication tree?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In storage constraint if the number of nodes is between 0 and 10 we are returning the list of nodes instead of the number of nodes
do: nodes |
Yes indeed , to do like in the patch |
5d6cd59
to
50967c0
Compare
50967c0
to
807fdee
Compare
807fdee
to
5e5f8f1
Compare
Description
This PR aims to resolve a problem of serialization when the size of the replication tree is different from the chain replicas & beacon replicas
Fixes #663
Type of change
How Has This Been Tested?
You can apply this patch, with more than 5 running nodes
Checklist: