DATAREDIS-552-Support setting client name for connection with redis server #219
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Motivation:
JedisConnectionFactory should support setting clientName into Jedis so
that we can trouble shooting easier by client name.
now no client name be showed for client list:
id=18 addr=10.140.201.34:51637 fd=12 name= age=85650 idle=85619 flags=N
db=0 sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0
events=r cmd=scan
Modifications:
add private member: clientName and use it in constructor for Jedis Pool.
Result:
easier to trouble shooting with connection name:
id=2 addr=10.224.38.23:33652 fd=5 name=sentinel-164682c3-cmd age=1350882
idle=1 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