Weaviate migrate to 1.24: start service error

[garance]

Hi, I tried to migrate Weaviate 1.22.11 to 1.24.0, Weaviate is on AWS ECS. When I started the service, I got the error:

 "error": "init shard \"test_X6mCkorqyK9u\": init shard \"test_X6mCkorqyK9u\": init per property indices: init properties on shard 'test_X6mCkorqyK9u': create property 'document_type' value index on shard 'test_X6mCkorqyK9u': init disk segments: invalid compacted segment file name \"segment-1709661156235385913.db.tmp\"",
    "level": "error",
    "msg": "Unable to load shard X6mCkorqyK9u: init shard \"test_X6mCkorqyK9u\": init shard \"test_X6mCkorqyK9u\": init per property indices: init properties on shard 'test_X6mCkorqyK9u': create property 'document_type' value index on shard 'test_X6mCkorqyK9u': init disk segments: invalid compacted segment file name \"segment-1709661156235385913.db.tmp\""

Weaviate service can’t be started.

How could I do? Should I return to old version and delete my class, or there is a better solution? Thanks.

[DudaNogueira]

Hi!

I believe this is a similar error:

Startup Failure

Hi @msj242, this error init segment segment-1705570724834516877.db: mmap file: invalid argument" may be caused by a corrupted .db file, it could be due to a reboot or unexpected crash (also during compaction) when using a version lower than v1.24 where integrity of files was improved. Was that data created in an older version?

[jeronimo_irazabal]

In this case it’s due to the existence of temporary files during, those were not handled before 1.24, but those files could be deleted before upgrading to 1.24 (it’s recommendable to still do a backup of those files anyways).