You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
qdrant 1.12.4 @qdrant/qdrant-js 1.12.0
localhost not remote server
I'm sure there must be some issues within the interface
Previously, when I used upsert, it caused a random Internal Server Error, but it returned to normal after the second retry
But now I have encountered this problem again, not upsert but deleteCollection, and the current triggering probability is 100% collectionExists always succeeds and is true, but once deleteCollection is run, it immediately fails
And similarly, if I execute it again, it will be successful
The magic is that each delete command needs to be executed twice, for example, after 'a collection' is executed twice, 'b collection' also needs to be executed twice before deletion (the first time will report an error)
I know this issue may be difficult to reproduce on other machines, but currently it is stably reproducing on my machine. Can we increase the number of retries to ensure this?
This is my premise issue, and I think the two may be the same problem #84
The text was updated successfully, but these errors were encountered:
qdrant
1.12.4@qdrant/qdrant-js
1.12.0localhost not remote server
I'm sure there must be some issues within the interface
Previously, when I used upsert, it caused a random
Internal Server Error
, but it returned to normal after the second retryBut now I have encountered this problem again, not
upsert
butdeleteCollection
, and the current triggering probability is 100%collectionExists
always succeeds and is true, but oncedeleteCollection
is run, it immediately failsAnd similarly, if I execute it again, it will be successful
The magic is that each delete command needs to be executed twice, for example, after 'a collection' is executed twice, 'b collection' also needs to be executed twice before deletion (the first time will report an error)
error
I know this issue may be difficult to reproduce on other machines, but currently it is stably reproducing on my machine. Can we increase the number of retries to ensure this?
This is my premise issue, and I think the two may be the same problem
#84
The text was updated successfully, but these errors were encountered: