The logs arent hugely helpful and I realise i've a...
# community-help
h
The logs arent hugely helpful and I realise i've accidentally cleared the ones showing what looks like the issue 😢 But essentially uploading a set of JSONL documents, where on is invalid using:
/collections/stackoverflow/documents/import?dirty_values=coerce_or_drop
and then doing an abrupt stop in docker, causes typesense to just get stuck trying to recover and it cant?
k
Have you been able to reproduce the issue?
Are you saying that Typesense server is just stuck and not able to finish loading docs on startup?
h
Looks like it
well, Looked*
k
Then how did it resolve?
h
it didnt. I just wiped the container
unless it did start up correctly, and something else blocked it from being 'ready'
Would It be helpful If I send the docker volume that was causing it to get stuck in the given state?
Thought I had removed it but turns out I haven't 👍 So should be useful to debug
k
Yes any form of reproduceable artifact is good
The key thing to notice when you get that lag message is to see if the local sequence number in the logs -- to see whether it's increasing.
h
Just bundling the volume up, it's reasonably chunky at about 6GB so might take a little bit
k
No worries, it's pretty late here so I'll probably be able to download and look only in the morning.
h
Fair enough, shall send once it's done (or more likely might go into a blob store)
Sorry, I realise I completely forgot about this 😅 Unfortunately I wasn't able to retrieve the volume data, something wasn't happy about me trying to copy it across and cleared everything 😕