Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some interfaces may have error #87

Open
wszgrcy opened this issue Nov 25, 2024 · 2 comments
Open

Some interfaces may have error #87

wszgrcy opened this issue Nov 25, 2024 · 2 comments

Comments

@wszgrcy
Copy link

wszgrcy commented Nov 25, 2024

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)

     let store = await this.#store$$;
      console.log(this.#graphCollectionName$$());

      let { exists } = await store.collectionExists(
        this.#graphCollectionName$$(),
      );

      if (exists) {
        await store.deleteCollection(this.#graphCollectionName$$());
      }

error

ApiError: Internal Server Error
    at Object.fun [as deleteCollection] (c:\code\my-project\ts-test\node_modules\@qdrant\openapi-typescript-fetch\dist\cjs\fetcher.js:172:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async QdrantClient.deleteCollection (c:\code\my-project\ts-test\node_modules\@qdrant\js-client-rest\dist\cjs\qdrant-client.js:876:26)
    at <anonymous> (c:\code\my-project\ts-test\qd-test.ts:24:10) {
  headers: Headers {
    [Symbol(guard)]: 'immutable',
    [Symbol(headers list)]: HeadersList {
      cookies: null,
      [Symbol(headers map)]: Map(5) {
        'transfer-encoding' => { name: 'transfer-encoding', value: 'chunked' },
        'content-type' => { name: 'content-type', value: 'application/json' },
        'vary' => {
          name: 'vary',
          value: 'accept-encoding, Origin, Access-Control-Request-Method, Access-Control-Request-Headers'
        },
        'content-encoding' => { name: 'content-encoding', value: 'gzip' },
        'date' => { name: 'date', value: 'Tue, 26 Nov 2024 09:06:31 GMT' }
      },
      [Symbol(headers map sorted)]: null
    },
    [Symbol(realm)]: null
  },
  url: 'http://127.0.0.1:6333/collections/test1',
  status: 500,
  statusText: 'Internal Server Error',
  data: {
    status: { error: 'Service internal error: 拒绝访问。 (os error 5)' },
    time: 0.0452989
  }
}

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

@wszgrcy
Copy link
Author

wszgrcy commented Nov 25, 2024

use webui delete collection same error
image

@wszgrcy
Copy link
Author

wszgrcy commented Nov 27, 2024

1.12.3 Running normally 1.12.4 Occurrence of the above abnormalities

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant