Open kziemianek opened 3 months ago
we always initialize shards explicitly upon first run. But I agree that we need more clarity in implementation and docs about this. Indeed, auto-initialize was the aim at the line you point to. I'll need to look into this.
the easy workaround is the -c
flag at first start
I tried to run local setup using
local-setup/launch.py
script but the worker panics during the initialization:My understanding is that
init-shard
command isDEPRECATED
and this line should init new shard for primary worker but it never reaches that point.Local changes:
So I've removed
--clean-reset
flag:Launch command:
./local-setup/launch.py local-setup/config/one-worker.json
If I go to
tmp/w1/
and run./integritee-service -d /tmp/data-dir/ init-shard
then worker starts properly.