create pvc from snapshot takes too much time

[fangfenghuang]

40Gi pvc restore from snapshot tasks more than 11min:

• source pvc: 40Gi

• snapshot: oceanstor-40g-snapshot

• targe pvc: from-oceanstor-40g-snapshot

• describe pvc

  # kubectl describe pvc from-oceanstor-40g-snapshot
  Name:          from-oceanstor-40g-snapshot
  Namespace:     default
  StorageClass:  oceanstor-vstore001
  Status:        Pending
  Volume:
  Labels:        <none>
  Annotations:   volume.beta.kubernetes.io/storage-provisioner: csi.huawei.com
             volume.kubernetes.io/storage-provisioner: csi.huawei.com
  Finalizers:    [kubernetes.io/pvc-protection]
  Capacity:
  Access Modes:
  VolumeMode:    Block
  DataSource:
  APIGroup:  snapshot.storage.k8s.io
  Kind:      VolumeSnapshot
  Name:      oceanstor-40g-snapshot
  Used By:     <none>
  Events:
  Type    Reason                Age                From                                                                   Message
  ----    ------                ----               ----                                                                   -------
  Normal  Provisioning          43s                csi.huawei.com_telecom-k8s-virt3_e1f5aebe-ebb8-4cf8-870b-d548c87a3580  External provisioner is provisioning volume for claim "default/from-oceanstor-40g-snapshot"
  Normal  ExternalProvisioning  14s (x4 over 43s)  persistentvolume-controller                                            waiting for a volume to be created, either by external provisioner "csi.huawei.com" or manually created by system administrator

• pvc creating: (took 11min )

  # kubectl get pvc from-oceanstor-40g-snapshot -w
  NAME                          STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS          AGE
  from-oceanstor-40g-snapshot   Pending                                      oceanstor-vstore001   2s
  ...
  from-oceanstor-40g-snapshot   Pending   pvc-1c32389a-0062-469d-8a0e-47b53d3c2896   0                         oceanstor-vstore001   11m
  from-oceanstor-40g-snapshot   Bound     pvc-1c32389a-0062-469d-8a0e-47b53d3c2896   40Gi       RWX            oceanstor-vstore001   11m

• csi-provisioner logs:

  # kubectl logs -n huawei-csi huawei-csi-controller-78cf9f96f5-sfw2k  -c csi-provisioner | grep from-oceanstor-40g-snapshot
  I0416 01:26:19.147533       1 controller.go:1279] provision "default/from-oceanstor-40g-snapshot" class "oceanstor-vstore001": started
  I0416 01:26:19.147676       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"from-oceanstor-40g-snapshot", UID:"1c32389a-0062-469d-8a0e-47b53d3c2896", APIVersion:"v1", ResourceVersion:"478373306", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "default/from-oceanstor-40g-snapshot"
  I0416 01:37:41.264126       1 controller.go:1384] provision "default/from-oceanstor-40g-snapshot" class "oceanstor-vstore001": volume "pvc-1c32389a-0062-469d-8a0e-47b53d3c2896" provisioned
  I0416 01:37:41.264164       1 controller.go:1397] provision "default/from-oceanstor-40g-snapshot" class "oceanstor-vstore001": succeeded
  I0416 01:37:41.268659       1 controller.go:1279] provision "default/from-oceanstor-40g-snapshot" class "oceanstor-vstore001": started
  I0416 01:37:41.268695       1 controller.go:1288] provision "default/from-oceanstor-40g-snapshot" class "oceanstor-vstore001": persistentvolume "pvc-1c32389a-0062-469d-8a0e-47b53d3c2896" already exists, skipping
  I0416 01:37:41.268710       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"from-oceanstor-40g-snapshot", UID:"1c32389a-0062-469d-8a0e-47b53d3c2896", APIVersion:"v1", ResourceVersion:"478373306", FieldPath:""}): type: 'Normal' reason: 'ProvisioningSucceeded' Successfully provisioned volume pvc-1c32389a-0062-469d-8a0e-47b53d3c2896

I have tried other csi like xsky, ceph that didn't take so much time, almost less than 3min

• xsky: (took 79s)

  # kubectl get pvc from-xsky-40g-snapshot -w
  NAME                     STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS      AGE
  from-xsky-40g-snapshot   Pending                                      xsky-block-sc-1   6s
  ...
  from-xsky-40g-snapshot   Pending   pvc-a63ea285-0ee9-4a33-b5ef-b2c5e3af38ba   0                         xsky-block-sc-1   79s
  from-xsky-40g-snapshot   Bound     pvc-a63ea285-0ee9-4a33-b5ef-b2c5e3af38ba   40Gi       RWX            xsky-block-sc-1   79s

I wonder whether it’s possible to optimize the performance of snapshot recovery?

[fangfenghuang]

As i set parameters.cloneSpeed to 4, it promoted from 11min to ~1min