What this PR does / why we need it:
Currently, the detaching retry limiter(added in https://github.com/yunify/qingcloud-csi/pull/160) will block any further detaching operation for a specific volume if this volume has more than --retry-times-max(defaults to 10) failed detaching operations recorded in the limiter.
But very often, when the cause of the failing detachments is fixed or self-recovered, the retry times have already exceeded the maxium, and since the retry times are stored in a map and never reset, this leaves the detaching of the volume blocked forever.
This PR:
Renames the ambiguous --retry-times-max option to --retry-detach-times-max.
Change the default retry times limit of detaching to 100.
Allows users to lift the retry times limit of detaching completely, by setting the --retry-detach-times-max to 0.
Signed-off-by: dkeven keven@kubesphere.io
What type of PR is this? /kind improvement
What this PR does / why we need it: Currently, the detaching retry limiter(added in https://github.com/yunify/qingcloud-csi/pull/160) will block any further detaching operation for a specific volume if this volume has more than
--retry-times-max
(defaults to 10) failed detaching operations recorded in the limiter.But very often, when the cause of the failing detachments is fixed or self-recovered, the retry times have already exceeded the maxium, and since the retry times are stored in a map and never reset, this leaves the detaching of the volume blocked forever.
This PR:
--retry-times-max
option to--retry-detach-times-max
.--retry-detach-times-max
to0
.Which issue(s) this PR fixes:
Fixes https://github.com/yunify/qingcloud-csi/issues/184