ceph-csi/deploy/rbd/kubernetes
ShyamsundarR c4a3675cec Move locks to more granular locking than CPU count based
As detailed in issue #279, current lock scheme has hash
buckets that are count of CPUs. This causes a lot of contention
when parallel requests are made to the CSI plugin. To reduce
lock contention, this commit introduces granular locks per
identifier.

The commit also changes the timeout for gRPC requests to Create
and Delete volumes, as the current timeout is 10s (kubernetes
documentation says 15s but code defaults are 10s). A virtual
setup takes about 12-15s to complete a request at times, that leads
to unwanted retries of the same request, hence the increased
timeout to enable operation completion with minimal retries.

Tests to create PVCs before and after these changes look like so,

Before:
Default master code + sidecar provisioner --timeout option set
to 30 seconds

20 PVCs
Creation: 3 runs, 396/391/400 seconds
Deletion: 3 runs, 218/271/118 seconds
  - Once was stalled for more than 8 minutes and cancelled the run

After:
Current commit + sidecar provisioner --timeout option set to 30 sec
20 PVCs
Creation: 3 runs, 42/59/65 seconds
Deletion: 3 runs, 32/32/31 seconds

Fixes: #279
Signed-off-by: ShyamsundarR <srangana@redhat.com>
2019-07-01 14:10:14 +00:00
..
csi-config-map.yaml Removed config maps and replaced with rados omaps 2019-05-19 12:29:33 +00:00
csi-nodeplugin-rbac.yaml deploy: Use aggregated ClusterRoles 2019-04-17 11:15:08 +05:30
csi-provisioner-rbac.yaml Revert "Use Deployment with leader election instead of StatefulSet" 2019-06-14 13:39:03 +00:00
csi-rbdplugin-provisioner.yaml Move locks to more granular locking than CPU count based 2019-07-01 14:10:14 +00:00
csi-rbdplugin.yaml update statefulset and daemonset api-version 2019-06-25 14:00:46 +00:00