diff options
| author | Morris Jobke <hey@morrisjobke.de> | 2016-03-04 15:42:35 +0100 |
|---|---|---|
| committer | Morris Jobke <hey@morrisjobke.de> | 2016-03-04 15:52:23 +0100 |
| commit | 138219d74a2a98f9fcc3e875658c3b6c259340d9 (patch) | |
| tree | b4f0639767f0eac7f3b10e5325618ab368c175c0 /apps/files/appinfo/update.php | |
| parent | 8be6054e5ce8aeffd6e305317e57e2747f7909ea (diff) | |
| download | nextcloud-server-138219d74a2a98f9fcc3e875658c3b6c259340d9.tar.gz nextcloud-server-138219d74a2a98f9fcc3e875658c3b6c259340d9.zip | |
Run cleanup of expired DB file locks to background job
* fixes #22819
The old way fired a DELETE statement on each destruction of the
DBLockingProvider. Which could cause a lot of queries. It's enough
to run this every 5 minutes in a background job, which in the end
could result in file locks that exists 5 minutes longer - in the
worst case and for not properly released locks.
This makes the DB based locking a lot more performant and could
result in a similar performance to the Redis based locking provider.
Diffstat (limited to 'apps/files/appinfo/update.php')
| -rw-r--r-- | apps/files/appinfo/update.php | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/apps/files/appinfo/update.php b/apps/files/appinfo/update.php index e4f8f8f29d7..72aff4cd0d4 100644 --- a/apps/files/appinfo/update.php +++ b/apps/files/appinfo/update.php @@ -102,3 +102,4 @@ if ($installedVersion === '1.1.9' && ( // Add cron job for scanning user storages \OC::$server->getJobList()->add('OCA\Files\BackgroundJob\ScanFiles'); \OC::$server->getJobList()->add('OCA\Files\BackgroundJob\DeleteOrphanedItems'); +\OC::$server->getJobList()->add('OCA\Files\BackgroundJob\CleanupFileLocks'); |