Closed kevinlu1248 closed 1 year ago
Don't mind upgrading the instance since we have lots of free credits but want to make sure that's not the root cause of the problem.
Is there more log output here? I don't see a segfault trace.
You could run out of ram - but want to confirm
Line 3 has a seg fault but no trace.
Our code looks something like
collection.add(
documents=documents,
metadatas=metadatas,
ids=ids,
)
so I believe it means they are being stored?
How many "clusters" do you have? I am trying to understand the total data size on one machine.
I mean collection sorry. I think at the time when it crashed we only had like 5.
Closing this as it is stale. Please let me know if anything else pops up here and we can re-open it.
@jeffchuber it's not stale, the issue was never really addressed nor fixed.
@kevinlu1248 chroma 0.4 introduced a wholesale rewrite of the backend which I suspect addresses this issue. Do you want to give it a spin?
Hello,
Still got the same issue when adding already embedded data to my chroma db
Using
def add(ids: OneOrMany[ID],
embeddings: Optional[OneOrMany[Embedding]] = None,
metadatas: Optional[OneOrMany[Metadata]] = None,
documents: Optional[OneOrMany[Document]] = None) -> None
What happened?
The database seg faulted a few times in deployment. I upgraded the instance recently too.
Versions
Docker image with hash 0e50c7589afc. Docker version 23.0.6, build ef23cbc. Running Vultr with 4vCPU and 8Gb of RAM (should I upgrade further?).
Relevant log output