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
An operation log for file moves was introduced to help with data consistency issues (#2877) in #4361, but it too has realistic cases which impact data availability.
The move operation works by first moving the file and then changing the path in the database. There are no locks on the asset row during this operation, which presents two problems:
There is a race condition where assets will be unavailable for brief periods during a storage migration.
Assets will be unavailable for extended periods of time if the asset row is not updated. It will eventually fix itself, but availability is impacted until then.
The OS that Immich Server is running on
N/A
Version of Immich Server
v1.82.0
Version of Immich Mobile App
N/A
Platform with the issue
Server
Web
Mobile
Your docker-compose.yml content
N/A
Your .env content
N/A
Reproduction steps
N/A
Additional information
N/A
The text was updated successfully, but these errors were encountered:
This is a non-issue when the storage template is disabled (and it is off by default now). There are no plans to support this level of availability while the storage migration is enabled.
The bug
An operation log for file moves was introduced to help with data consistency issues (#2877) in #4361, but it too has realistic cases which impact data availability.
The move operation works by first moving the file and then changing the path in the database. There are no locks on the asset row during this operation, which presents two problems:
The OS that Immich Server is running on
N/A
Version of Immich Server
v1.82.0
Version of Immich Mobile App
N/A
Platform with the issue
Your docker-compose.yml content
N/A
Your .env content
Reproduction steps
Additional information
N/A
The text was updated successfully, but these errors were encountered: