Investigate potential problems with big amount of alphabet nodes #295
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#295
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
frostfs-adm has tests for deploying 1, 4 and 7 nodes. These numbers are the most frequent. I would like to add the biggest amount of alphabet nodes (all letters), just to check our limits.
There are 2 potential problems here, which we can look for:
.
in their string representation. This can play not nicely with NNS domains registration.Currently the test passes with up to 15 nodes.
Using 16 or more nodes runs into the following limit in Stage 5:
And running with many more nodes (e.g. 31 or more) hits a transaction limit in Stage 1:
Ok, let's fix everything incrementally, I will create tasks.
I consider the task done, there are limits in neo-go now.