File locks are never removed from the system, so they keep increasing in
the locks directory, which can become problematic.
In this patch we start trying to delete these lock files when we delete
a volume or a snapshot.
This affects the 2 type of file locks we currently have:
- Using oslo lockutils synchronized with external=True
- Using coordination.synchronized when deployed in Active-Passive and no
DLM
This will alleviate the ever increasing files in the locks directory.
Deployment tools should implement a service that runs when the host is
booting and cleans of the locks directory before the OpenStack services
are started.
Reviewed: https:/ /review. opendev. org/c/openstack /cinder/ +/689486 /opendev. org/openstack/ cinder/ commit/ d2f6ec5569b1c1b 68f567392cfc03a 6476169b4b
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit d2f6ec5569b1c1b 68f567392cfc03a 6476169b4b
Author: Gorka Eguileor <email address hidden>
Date: Fri Oct 18 15:51:13 2019 +0200
Remove file locks once we delete a resource
File locks are never removed from the system, so they keep increasing in
the locks directory, which can become problematic.
In this patch we start trying to delete these lock files when we delete
a volume or a snapshot.
This affects the 2 type of file locks we currently have: synchronized when deployed in Active-Passive and no
- Using oslo lockutils synchronized with external=True
- Using coordination.
DLM
This will alleviate the ever increasing files in the locks directory.
Deployment tools should implement a service that runs when the host is
booting and cleans of the locks directory before the OpenStack services
are started.
Partial-Bug: #1432387 24383c6cb79f2e8 c04810aaf69
Change-Id: Ic73ee64257aeb0