Closed LucaPrete closed 4 years ago
Turns out it's a known issue with azurefires, which uses cifs 3 to expose the fs. There's an issue opened here
Meanwhile, we've moved the db from an azurefile-based PVC to an azuredisk-based PVC, which is a WRO block storage. The only downside of this is that multiple containers cannot read from the same storage, so rolling updates are not possible. This causes downtime for users while the container gets updated.
We'll close the issue for now, but we'll keep investigating with Microsoft on a possible solution.
The application keeps a lock on the database for its entire life-span. This blocks writes on the database.
For example, every time a user tries to update a municipality takeover, the following error is returned:
To reproduce
At server side, the following error is returned:
This is also true for DB updates from the sqlite CLI.
The error disappears as soon as the application is turned off. This is a known workaround to manually update data.