VIVALXH

@git-hulk thanks. No duplicate data was generated, but this resulted in the loss of a significant amount of data that should have been written. I controlled the osscluster retry count...

@git-hulk I am using ClusterClient, and internally it uses MaxRedirects instead of MaxRetries in its process function. It worked as expected and achieved our goal of preventing duplicate data. https://github.com/redis/go-redis/blob/1139bc3aa9073851f67faa6d68df07a566901dd7/osscluster.go#L967...

> Hi [@VIVALXH](https://github.com/VIVALXH) > > go-redis might retry on network error. Would you mind disabling the retry to see if the issue is still existing? https://github.com/redis/go-redis/blob/1139bc3aa9073851f67faa6d68df07a566901dd7/options.go#L75C2-L75C12 @git-hulk Now we conclude...

> [@VIVALXH](https://github.com/VIVALXH) The cluster client also supports the [MaxRetries](https://github.com/redis/go-redis/blob/master/osscluster.go#L75), set MaxRedirects=-1 wouldn't retry when occuring the TRYGAIN error. @git-hulk Hello, I tried setting `MaxRetries=-1` today, but duplicate data still occurred....

> > So I guess the data duplication is caused by retries due to Moved errors or TryAgain errors? > > I'm not quite sure about this. But after considering...