Hide Forgot
Redis service is impossible to set to active slave mode. Description of problem: Redis service is impossible to set to active slave mode. Version-Release number of selected component (if applicable): rh-redis32-redis-3.2.4-1.el7.x86_64 rh-redis32-redis-3.2.4-1.el6.x86_64 How reproducible: aways Steps to Reproduce: 1. run redis service on master and slave machine: $ service rh-redis32-redis start 2. fill redis database with key-values on master: $ opt/rh/rh-redis32/root/usr/bin/redis-cli SET mykey 10 3. revoke redis protection on master: $ opt/rh/rh-redis32/root/usr/bin/redis-cli CONFIG SET protected-mode no 4. order slave to master on slave machine: $ opt/rh/rh-redis32/root/usr/bin/redis-cli slaveof master_name master_port 5. as to values under keys exists on master machine using slave machine: $ opt/rh/rh-redis32/root/usr/bin/redis-cli GET mykey Actual results: (nill) no value Expected results: 10 Additional info: If we ask on reids status using "info replication" command we can see following output: $ opt/rh/rh-redis32/root/usr/bin/redis-cli INFO replication # Replication role:slave master_host:10.8.175.136 master_port:6379 master_link_status:down .... in case that 'slavery' proces is working well should be the output following: # Replication role:slave master_host:10.8.175.136 master_port:6379 master_link_status:up .... I suppose the master_link_status value shoul be up if the slaveof host port is called.
In accordance with the Red Hat Software Collections Product Life Cycle, the support period for this collection has ended. New bug fix, enhancement, and security errata updates, as well as technical support services will no longer be made available for this collection. Customers are encouraged to upgrade to a later release. Please contact Red Hat Support if you have further questions, or refer to the support lifecycle page for more information. https://access.redhat.com/support/policy/updates/rhscl/