Closed xdxxxdx closed 9 months ago
Hi @xdxxxdx , Although this issue is still there, the reality is that this has very little impact on current customers. Everyone who used a ldes-server older than ~june 2023 might have this behaviour. But the worst thing that could come of this, is that a few members are fragmented out of order.
However since we don't have any more onboarders who haven't migrated yet. This is to be a non issue
Prerequisites
To Reproduce
curl -X POST "http://localhost:8081/admin/api/v1/pipeline/halt"
docker compose rm --stop --force --volumes old-ldes-server
docker compose up new-ldes-server -d docker logs --tail 1000 -f $(docker ps -q --filter "name=new-ldes-server$")
curl -X POST "http://localhost:8081/admin/api/v1/pipeline/resume"
Current behavior 851 NEW LDES members are ingested to the new LDES Server, together with the OLD 315 LDES members. => 1165 LDES members are in the
iow_devices.ingest_ldesmember
table The end of thesequenceNr
is 851 instead of 1165The
sequenceNr
is restarted from 1 from the new ingest members of the new LDES ServerTable dump: iow_devices.ingest_ldesmember.zip
Expected behavior All 1165 ldes members should be in a continuously sequence?. e.g. from 1 to 1165