Process Crash and Restarts

[Snarik]

Hey all, Having a blast with LNX so far. Really remarkable what you folks have built. Im bumping up against an issue I was hoping to get some clarity on.

Im running lnx in a docker container with a persistent mounted volume. Something vaguely like:

	docker run -p 8080:8000 --name=textDB -v /tmp/lnx-db:/index --rm  -d chillfish8/lnx:latest

It works well if the process exits gracefully, however if I sigkill the process it leaves a hanging Writelock on the process that prevents a new one from starting up again:

2023-03-13T06:52:22.106904Z ERROR error during lnx runtime: failed to load existing indexes due to error Failed to acquire Lockfile: LockBusy. Some("Failed to acquire index lock. If you are using a regular directory, this means there is already an `IndexWriter` working on this `Directory`, in this process or in a different process.")

I get that this is a fairly alpha product, but is there any guidance on how I might be able to fix the lock without trashing my index? It's unlikely but I envision a case where the host this is running on dies or reboots spontaneously and I am unable to restart the process even though the index is still on disk.

Any thoughts would be greatly appreciated.

[Snarik]

I feel like I should spend slightly longer diving deep before posting questions.

Anyway if anyone else comes to this problem the answer is that Tantivy writes a lockfile to the index directory at /index/index-storage/<indexHash>/data/.tantive-writer.lock

Just rm that file and your process will start.