You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?/Why is this needed
Describe the solution you'd like in detail
currently every single volume cloning requires 5s, most of the time is wasting in waiting for next tick, maybe it's better using exponential seconds waiting, e.g. 0.5ms, 1s, 2s, 4s, 8s or simply set 0.5ms ticking, and only print logs every 5s?
I0119 11:53:03.883970 1 controllerserver.go:1265] generate sas token for account(f6e8d90b6b56b496f8c21b1)
I0119 11:53:03.898119 1 azurefile.go:1016] azcopy job status: NotFound, copy percent: %, error: <nil>
I0119 11:53:03.898142 1 azurefile.go:1020] begin to copy fileshare pvc-99deda38-6cab-4625-af12-7ee0f73788c1 to pvc-4653ddc5-f315-44ef-bb68-9d78b9903ba7
I0119 11:53:08.898581 1 azurefile.go:1025] azcopy job status: NotFound, copy percent: %, error: <nil>
I0119 11:53:08.898611 1 azurefile.go:1030] copy fileshare pvc-99deda38-6cab-4625-af12-7ee0f73788c1 to pvc-4653ddc5-f315-44ef-bb68-9d78b9903ba7
I0119 11:53:31.264565 1 azurefile.go:1051] copied fileshare pvc-99deda38-6cab-4625-af12-7ee0f73788c1 to pvc-4653ddc5-f315-44ef-bb68-9d78b9903ba7 successfully
I0119 11:53:31.264664 1 controllerserver.go:590] create file share pvc-4653ddc5-f315-44ef-bb68-9d78b9903ba7 on storage account f6e8d90b6b56b496f8c21b1 successfully
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?/Why is this needed
Describe the solution you'd like in detail
currently every single volume cloning requires 5s, most of the time is wasting in waiting for next tick, maybe it's better using exponential seconds waiting, e.g. 0.5ms, 1s, 2s, 4s, 8s or simply set 0.5ms ticking, and only print logs every 5s?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: