In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-02-24 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
# main view parameters: # Serveruptime_in_seconds:83904 # redis service run time uptime_in_days:0 # redis run days # Clients connected_clients:1 # number of connected clients (excluding connections from slave server) blocked_clients:0 # waiting & blocking command (BLPOP/BRPOP/BRPOPLPUSH) Number of clients # Memory used_memory_human:790.88K # human readable format Show Total memory allocated by redis used_memory_peak_human:979.51K # Human readable format shows the ratio of peak memory consumption peak mem_fragmentation_ratio:7.33 # used_memory_rss (actual memory used in the system) to used_memory (system allocated memory). # Stats total_connections_received:96840 # connection requests received by the redis service total_commands_processed:857679 # # commands executed instantaneous_ops_per_sec:2 # # commands executed per second rejected_connections:0 # # the number of connection requests rejected due to the maximum number of clients limit expired_keys:0 # # number of database keys automatically deleted due to expiration evicted_keys:0 # # number of keys expelled (evict) due to maximum memory capacity limit keyspace_hits:0 # # number of times keyspace_misses:190208 # # failed to find database keys # Persistence rdb_changes_since_last_save:0 # # since the last successful creation of a persistent file How many seconds have elapsed aof_last_bgrewrite_status:ok # # A flag value Records the success or failure of the most recent creation of the AOF file 127.0.0.1 123.el7.x86_64 x86_64arch_bits:64multiplexing_api:epollgcc_version:4.8.3process_id:32701run_id:dfc0c9b96cc2ecb0fd7fbdbdf116ddde63690b4ctcp_port:6379 6379 > INFO# Serverredis_version:2.8.19redis_git_sha1:00000000redis_git_dirty:0redis_build_id:c0359e7aa3798aa2redis_mode:standaloneos:Linux 3.10.0-123.el7.x86_64 x86_64arch_bits:64multiplexing_api:epollgcc_version:4.8.3process_id:32701run_id:dfc0c9b96cc2ecb0fd7fbdbdf116ddde63690b4ctcp_port:6379 # Enable port 6379uptime_in_seconds:83904 # redis service run time uptime_in_days:0 # redis run days hz:10lru_clock:13788489config_ # Clients # # connected client information connected_clients:1 # number of connected clients (excluding connections from slave server) client_longest_output_list:0 # in the currently connected client The most common output list client_biggest_input_buf:0 # of the currently connected clients, the largest input cache blocked_clients:0 # the number of clients waiting for the blocking command (BLPOP/BRPOP/BRPOPLPUSH) # Memory # # memory usage information used_memory:809856 # total memory allocated by redis Unit byte (byte) used_memory_human:790.88K # human-readable format showing the total memory allocated by redis used_memory_rss:5935104 # redis's resident memory in the system, that is, the peak memory consumption of used_memory_peak:1003016 # redis for allocated memory (consistent with the output of top, ps, etc.) Maximum consumption used_memory_peak_human:979.51K # Human-readable format shows the maximum memory consumption Peak used_memory_lua:35840 # # the amount of memory used by the lua engine, the ratio of mem_fragmentation_ratio:7.33 # # used_memory_rss (actual memory used in the system) to used_memory (system allocated memory). # # ideally, used_memory_rss is slightly higher than userd_memory. # # if rss > used, and there is a big difference between the two, it means that there is a memory fragment (internal or external) # # if used > rss, part of the memory of the redis is swapped out to the swap space by the operating system, and the request may cause obvious delay. # # when redis frees memory, the allocator may or may not return memory to the system. If it is not returned to the system, it will cause used_memory < userd_memory_rss. # # check used_memory_peak frequently to determine memory usage mem_allocator:jemalloc-3.6.0# Persistence # # RDB and AOF related information loading:0rdb_changes_since_last_save:0 # # after the last successful creation of a persistent file How many seconds have elapsed rdb_bgsave_in_progress:0rdb_last_save_time:1473322377rdb_last_bgsave_status:okrdb_last_bgsave_time_sec:-1rdb_current_bgsave_time_sec:-1aof_enabled:0aof_rewrite_in_progress:0aof_rewrite_scheduled:0aof_last_rewrite_time_sec:-1aof_current_rewrite_time_sec:-1aof_last_bgrewrite_status:ok # # A flag value Records whether the result of the last creation of the AOF file was successful or failed aof_last_write_status:ok# Stats # # General Statistics total_connections_received:96840 # connection requests received by the redis service total_commands_processed:857679 # # commands executed instantaneous_ops_per_sec:2 # # commands per second total_net _ input_bytes:38715733 total_net_output_bytes:4129604instantaneous_input_kbps:0.08instantaneous_output_kbps:0.06rejected_connections:0 # # the number of connection requests rejected because of the maximum number of clients limit sync_full:0sync_partial_ok:0sync_partial_err:0expired_keys:0 # # databases that are automatically deleted because of expiration Number of keys evicted_keys:0 # # number of keys expelled (evict) due to maximum memory capacity limit keyspace_hits:0 # # number of times database keys were successfully found keyspace_misses:190208 # # times pubsub_channels:0pubsub_patterns:0latest_fork_usec:0# Replication failed to find database keys # # redis Master-Slave replication Information role:master # # roles in the cluster connected_slaves:0master_repl_offset:0repl_backlog_active:0repl_backlog_size:1048576repl_backlog_first_byte_offset:0repl_backlog_histlen:0# CPU # # cpu consumed by using statistical information used_cpu_sys:56.14 # redis System cpuused_cpu_user: 21.72 # redis consumed user cpuused_cpu_ sys_children:0.00 # system cpuused_cpu_user_children:0.00 consumed by background process # user cpu# Keyspace consumed by background process
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.