We have recently introduced Redis into our solution and are running into an odd problem. We have updated the timeout setting in the redis.conf file in addition to executing the redis-cli CONFIG SET timeout command and after a reboot of the server the timeout setting is being returned as nill when executing the command redis-cli get timeout. However when executing the command redis-cli CONFIG get timeout, the correct value does appear to be returning. Any insight?
One other piece of information, this is happening on our QA servers however everything works as expected on our DEV servers. Same process, different results.
I suspect I am just not understanding how these commands work (although the documentation appears to be solid), but just looking for some insight. I did not find any relevant discussions around this and very well could have missed something.
Comment From: badboy
GET timeout and CONFIG GET timeout are different things.
The first one tries to fetch the data associated with the key timeout, the later one fetches the config value of timeout.
Of course the former is likely empty.