-
Notifications
You must be signed in to change notification settings - Fork 8
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
deleting and recreating ledger with different schema errors, still holds old data #98
Comments
Saw this again today with the same repro steps with ledger version 1 and db version 1.0.0-rc33, except that it also happens when the schema does not change. I see this error on the ledger container logs when transacting the schema onto the recreated ledger: We are trying to delete a ledger and recreate it from data we have, but it looks like ledgers can't be recreated via the programmatic API right now. Our workaround is to shut down the fluree container and delete the volume data for it. |
Hi @filipesilva I'll update our internal tracking with this information. If you shut down the Fluree container and then restart it, without physical deletion of the volume data, does Fluree recognize that the ledger is deleted & allow you to re-create the ledger? |
@ldw1007 if I restart the ledger container right after If I restart the ledger after the delete, recreate, and schema transact (so after seeing an error), the ledger fails to start with the following message:
So it seems like shutting down the ledger container will effect the delete, but recreating without a shutdown will leave the ledger container with data that breaks it. |
Hi there 👋
I think there might be a problem when recreating a deleted a ledger with a different schema. I've uploaded a repro you can run by following these steps:
git clone https://github.com/filipesilva/fluree-ledger-create-delete-create
cd fluree-ledger-create-delete-create
docker compose up fluree
repro
comment formThe repro ns is as follows:
The most significant parts are
;; fluree on docker errors here, with log
and;; Query still shows old data from the deleted ledger there.
.The text was updated successfully, but these errors were encountered: