Reset cluster related stats in CONFIG RESETSTATS (#2458)

Previously CONFIG RESETSTATS only resets the slot statistics in
cluster part, this PR makes it reset cluster bus messages at well.
Additionally, we also reset stat_cluster_links_buffer_limit_exceeded.

Now we will reset:
- cluster_stats_messages_sent*
- cluster_stats_messages_received*
- total_cluster_links_buffer_limit_exceeded

Closes #2439.

Signed-off-by: Hongrui <2086160503@qq.com>

Author: withRiver

src/cluster.c

@@ -1594,6 +1594,10 @@ void resetClusterStats(void) {
     if (!server.cluster_enabled) return;
 
     clusterSlotStatResetAll();
+
+    memset(server.cluster->stats_bus_messages_sent, 0, sizeof(server.cluster->stats_bus_messages_sent));
+    memset(server.cluster->stats_bus_messages_received, 0, sizeof(server.cluster->stats_bus_messages_received));
+    server.cluster->stat_cluster_links_buffer_limit_exceeded = 0;
 }
 
 void clusterCommandFlushslot(client *c) {

tests/unit/cluster/info.tcl

@@ -63,6 +63,28 @@ start_cluster 3 0 {tags {external:skip cluster} overrides {cluster-node-timeout
         resume_process [srv -1 pid]
         wait_for_cluster_state ok
     }
+
+    test "CONFIG RESETSTAT resets cluster related stats" {
+        R 0 config set cluster-link-sendbuf-limit 1
+        wait_for_condition 1000 10 {
+            [CI 0 cluster_stats_messages_sent] >= 1 &&
+            [CI 0 cluster_stats_messages_received] >= 1 &&
+            [CI 0 total_cluster_links_buffer_limit_exceeded] >= 1
+        } else {
+            fail "R 0 related info fields are not as expected"
+        }
+
+        R 0 multi
+        R 0 config resetstat
+        R 0 cluster info
+        set info [lindex [R 0 exec] 1]
+        
+        assert_equal [getInfoProperty $info cluster_stats_messages_sent] 0
+        assert_equal [getInfoProperty $info cluster_stats_messages_received] 0
+        assert_equal [getInfoProperty $info total_cluster_links_buffer_limit_exceeded] 0
+
+        R 0 config set cluster-link-sendbuf-limit 0
+    }    
 }
 
 start_cluster 3 0 {tags {external:skip cluster} overrides {cluster-node-timeout 1000}} {