-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Annotations Lost After Network failure for around 2 mins. #6675
Comments
Hello, This is when you have target storage setup? or it just source storage that causes these issue? I would also suggest: Switch to a PostgreSQL Database:
Thank you,
|
Hi , I also have azure blob container in the same storage account as target storage. |
Hello, The problem may be related to using SQLite as the backend database. SQLite is suitable for small projects and testing purposes but can encounter issues with larger datasets and network instability. Since you're working with over 10,000 tasks, switching to a more robust database like PostgreSQL is highly recommended. Let us know how that goes. Thank you,
|
Hi I have around 10000 images in an azure blob storage container. There are intermittent network connection issues and some times the the call to azure blob store fails. But during that time some of the annotations are lost.
To Reproduce
Steps to reproduce the behaviour:
Setup data import form azure blob store. Use a container prefix path.
Annotate a few files.
Simulate a network error (Turn off the internet connection so that the get request from azure blob fails)
Upto 50% of the annotations will be missing after refreshing.
My assumption was that all the annotations will be persisted in the sql lite database in my local storage. Losing half of the data that I annotated is causing great pain. During the first network connection error the task number I was annotating was 2003. Then after refresh the annotated task numbers where from 1 to 500 only. Rest of the tasks did not have any annotations.
OS: Macos
Label Studio Version 1.14.0.post0
The text was updated successfully, but these errors were encountered: