Revert existing ULong configs to have LONG_MAX upper threshold

Update valkey.conf description

Signed-off-by: Brennan Cathcart <[email protected]>

src/config.c

@@ -3208,9 +3208,9 @@ standardConfig static_configs[] = {
 #endif
 
     /* Unsigned Long configs */
-    createULongConfig("active-defrag-max-scan-fields", NULL, MODIFIABLE_CONFIG, 1, ULONG_MAX, server.active_defrag_max_scan_fields, 1000, INTEGER_CONFIG, NULL, NULL), /* Default: keys with more than 1000 fields will be processed separately */
-    createULongConfig("slowlog-max-len", NULL, MODIFIABLE_CONFIG, 0, ULONG_MAX, server.slowlog_max_len, 128, INTEGER_CONFIG, NULL, NULL),
-    createULongConfig("acllog-max-len", NULL, MODIFIABLE_CONFIG, 0, ULONG_MAX, server.acllog_max_len, 128, INTEGER_CONFIG, NULL, NULL),
+    createULongConfig("active-defrag-max-scan-fields", NULL, MODIFIABLE_CONFIG, 1, LONG_MAX, server.active_defrag_max_scan_fields, 1000, INTEGER_CONFIG, NULL, NULL), /* Default: keys with more than 1000 fields will be processed separately */
+    createULongConfig("slowlog-max-len", NULL, MODIFIABLE_CONFIG, 0, LONG_MAX, server.slowlog_max_len, 128, INTEGER_CONFIG, NULL, NULL),
+    createULongConfig("acllog-max-len", NULL, MODIFIABLE_CONFIG, 0, LONG_MAX, server.acllog_max_len, 128, INTEGER_CONFIG, NULL, NULL),
     createULongConfig("cluster-blacklist-ttl", NULL, MODIFIABLE_CONFIG, 0, ULONG_MAX, server.cluster_blacklist_ttl, 60, INTEGER_CONFIG, NULL, NULL),
 
     /* Long Long configs */

valkey.conf

@@ -1760,11 +1760,13 @@ aof-timestamp-enabled no
 #
 # cluster-preferred-endpoint-type ip
 
-# The cluster blacklist is useful when removing a node from the cluster completely. 
+# The cluster blacklist is used when removing a node from the cluster completely. 
 # When CLUSTER FORGET is called for a node, that node is put into the blacklist for
 # some time so that when gossip messages are received from other nodes that still
 # remember it, it is not re-added. This gives time for CLUSTER FORGET to be sent to
-# every node in the cluster. The blacklist TTL is 60 seconds by default.
+# every node in the cluster. The blacklist TTL is 60 seconds by default, which should
+# be sufficient for most clusters, but you may considering increasing this if you see
+# nodes getting re-added while using CLUSTER FORGET.
 #
 # cluster-blacklist-ttl 60
 
@@ -2329,4 +2331,4 @@ jemalloc-bg-thread yes
 # this is only exposed via the info command for clients to use, but in the future we
 # we may also use this when making decisions for replication.
 #
-# availability-zone "zone-name"
+# availability-zone "zone-name"