Application of redis client list in practice

The problem background

redis After the data migration on the old database is completed , The machine needs to be returned to O & M , When checking whether the old database still has traffic , There are very few set\get Requested and irregular .

Direction of investigation

This problem is to be solved , Otherwise, it cannot be returned to the operation and maintenance machine , The first reaction is to check the code , Look at the code that connects the instance , No result of investigation .

Problem thinking & solve

One morning I had a whim , If there is get\set request , There must be a client connection , You can reverse find the machine where the service is located through the connection of the client , And then find out the service . I want to go over it again redis manual , Now there's a client list All connected machines can be listed .

id=3968277 addr=10.10.31.109:33913 fd=5 age=1794 idle=5 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=ping replaof_fileid=0 replaof_fileoffset=0
id=3514528 addr=10.103.80.101:55962 fd=10 age=1531646 idle=1531646 flags=S db=0 sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events= cmd=sync replaof_fileid=1905 replaof_fileoffset=679885188 // From copying 

Parameter description ： From https://www.zadd.site/post/redis/client-list/

Pass quickly addr Locate the location of the service , After boarding, I found that the old service had not been stopped , Turn off the service and then monitor Command view ,set\get The order disappeared .

summary

Two points can be drawn from this question ：
1、 When positive thinking cannot be solved , Think in reverse .
2、 It is important to be familiar with the tools you use .