not enough nodes to SELECT from
answer on the dev-env
In general, that error could occur not only on the 1st epoch but also when a network map has had not enough nodes on the previous two epochs (fact checking needed)
@a-savchuk Could you share benchmark setup and code?
I added them in the first comment
I collected an off-CPU profile as I was advised by @dstepanov-yadro *thanks*. Here's what I found
Off-CPU profile (for 10.000 parts only)
Data: [off_cpu_10000_parts.pb.gz](/attachments/68…
I've decided to write a benchmark for the (*StorageEngine).Inhume
method. I ran it for 1, 10, 100, 1.000, and 10.000 addresses in a tombstone, and I collected a CPU profile and memory profile…
Inhume
when there's many addresses
(*testEngineWrapper).setInitializedShards
subject not found
error
Made the PR description more detailed:
The affected function
isContainerNode
is used for determining if an actor is a container role when checking an APE rule. It's guaranteed that the policy…
not enough nodes to SELECT from
answer on the dev-env
I noticed that the problem occurs only when the -g
flag is used