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

Indexing stuck in Preparing state #357

Closed
finnove opened this issue Sep 20, 2023 · 2 comments · Fixed by #374
Closed

Indexing stuck in Preparing state #357

finnove opened this issue Sep 20, 2023 · 2 comments · Fixed by #374
Assignees

Comments

@finnove
Copy link

finnove commented Sep 20, 2023

Description

When an unsupported SIARD is loaded, the indexing can stop at a specific table.
The status will be stuck in "Preparing".
Problem: Its not possible to delete this database entry easily, and multiple efforts can make it worse.

Previous workaround tried:

  • Used swagger-ui to find a curl command to delete the collection. Then the status will change, and I can delete the database in the GUI as before.
  • Removing tables that are problematic, with a siard-to-siard conversion (but the old efforts are still visible in the catalog)

Context

DBPTK Enterprise

Suggested solution

  • Please make it possible to delete a database that is stuck in the "Preparing" state from the GUI
  • swagger-ui is turned off in recent versions. how to enable, or find the proper curl commands / api documentation?
  • or remind us of the proper curl command for this situation
@hmiguim
Copy link
Member

hmiguim commented Nov 24, 2023

It was agreed to on every DBPTK initialization looking for databases that were in INGESTING state and marked as ERROR so it can be deleted via WUI

@AntonioG70 AntonioG70 linked a pull request Nov 29, 2023 that will close this issue
@finnove finnove changed the title Indexing stuck in pending state Indexing stuck in Preparing state Dec 1, 2023
@hmiguim
Copy link
Member

hmiguim commented Dec 13, 2023

release on version 2.8.0

@hmiguim hmiguim closed this as completed Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants