Redis INFO returns absurd value for connected_clients breaking lettuce.io

David Noriega 41 Reputation points
2021-12-02T02:02:03.043+00:00

I've setup a Redis cluster and when I send the command INFO, I get something like the following:

{'redis_version': '6.0.14', 'redis_mode': 'cluster', 'os': 'Windows  ', 'arch_bits': 64, 'multiplexing_api': 'winsock_IOCP', 'run_id': '9446a93cfb9fc2d192238fdfd8868550dfd68b07', 'uptime_in_seconds': 1013, 'uptime_in_days': 0, 'hz': 10, 'connected_clients': 4294967295, 'maxclients': 7500, 'client_recent_max_input_buffer': 8, 'client_recent_max_output_buffer': 0, 'client_total_writes_outstanding': 0, 'client_total_sent_bytes_outstanding': 0, 'blocked_clients': 0, 'tracking_clients': 0, 'clients_in_timeout_table': 0, 'used_memory': 102582496, 'used_memory_human': '97.83M', 'used_memory_rss': 2293760, 'used_memory_rss_human': '2.19M', 'used_memory_peak': 103143472, 'used_memory_peak_human': '98.37M', 'used_memory_peak_perc': '99.46%', 'used_memory_overhead': 102500328, 'used_memory_startup': 1713832, 'used_memory_dataset': 82168, 'used_memory_dataset_perc': '0.08%', 'used_memory_lua': 37888, 'maxmemory': 6100000000, 'maxmemory_reservation': 200000000, 'maxfragmentationmemory_reservation': 300000000, 'maxmemory_desired_reservation': 200000000, 'maxfragmentationmemory_desired_reservation': 300000000, 'maxmemory_human': '5.68G', 'maxmemory_policy': 'volatile-lru', 'mem_allocator': 'jemalloc-4.0.3', 'total_connections_received': 2358, 'total_commands_processed': 4330, 'instantaneous_ops_per_sec': 11, 'bytes_received_per_sec': 557, 'bytes_sent_per_sec': 2082, 'bytes_received_per_sec_human': '557B', 'bytes_sent_per_sec_human': '2.03K', 'rejected_connections': 0, 'expired_keys': 0, 'evicted_keys': 0, 'keyspace_hits': 3, 'keyspace_misses': 2, 'pubsub_channels': 0, 'pubsub_patterns': 0, 'total_oom_messages': 0, 'role': 'master', 'used_cpu_sys': 0.875, 'used_cpu_user': 0.734375, 'used_cpu_avg_ms_per_sec': 3, 'server_load': 0.28, 'event_wait': 15, 'event_no_wait': 15, 'event_wait_count': 24, 'event_no_wait_count': 12, 'cluster_enabled': 1, 'cluster_myself_name': 'e17a6708c086a29c544d3daa8e55cc0f9e991b00', 'db0': {'keys': 3, 'expires': 0, 'avg_ttl': 0}}

Notice 'connected_clients': 4294967295
The problem here is this is not true and causes problems when I use lettuce.io's redis library, it understandably does not like this value.

I can reboot the whole cluster, the first time I run INFO, connected_clients=1, but other attempts after that return this absurd number, which apparently is equal to the max number of keys redis can hold

Azure Cache for Redis
Azure Cache for Redis
An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.
251 questions
0 comments No comments
{count} votes

Accepted answer
  1. Oury Ba-MSFT 19,101 Reputation points Microsoft Employee
    2021-12-02T21:50:39.937+00:00

    Hi @David Noriega Thank you for posting your question on Microsoft Q&A.
    This is a known issue, and our product team will be rolling out a fix over the next couple of weeks.
    I will give you an update. Thanks for your patience

    Regards,
    Oury


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.