[DRAFT] feat: implement redis array on phpredis. Issue #195 #746

shakaran · 2025-07-16T18:54:55Z

Related #195

shakaran · 2025-07-17T09:14:41Z

@ostrolucky Could you give some guide here? I don't know exactly which hosts or ports should use for the tests and get the connection done. I try to use like in other tests but it seems not working in the connection pipeline. Thanks

ostrolucky · 2025-07-17T09:35:18Z

@shakaran Here is the configuration of redis nodes used in tests https://github.com/snc/SncRedisBundle/tree/master/.github/workflows/redis-configs. If you follow the README, you will also have a way to reproduce this locally.

shakaran · 2025-07-17T11:10:00Z

@shakaran Here is the configuration of redis nodes used in tests https://github.com/snc/SncRedisBundle/tree/master/.github/workflows/redis-configs. If you follow the README, you will also have a way to reproduce this locally.

I can reproduce 100% locally with overmind, the same error than the pipeline, but I dont know why the tests are not connecting to the nodes in my tests.

$ overmind start 
system         | Tmux socket name: overmind-sncredisbundle-g4qZ-11MJfY3ud7v-1vXq
system         | Tmux session ID: sncredisbundle
system         | Listening at ./.overmind.sock
redis-node6    | Started with pid 2632643...
redis-node4    | Started with pid 2632629...
redis-node2    | Started with pid 2632611...
redis-node3    | Started with pid 2632616...
redis-sentinel | Started with pid 2632593...
redis-node5    | Started with pid 2632633...
redis-node1    | Started with pid 2632602...
redis-acl      | Started with pid 2632587...
redis-node1    | 2632610:C 17 Jul 2025 13:05:48.812 # WARNING: Changing databases number from 16 to 1 since we are in cluster mode
redis-node2    | 2632615:C 17 Jul 2025 13:05:48.815 # WARNING: Changing databases number from 16 to 1 since we are in cluster mode
redis          | Started with pid 2632580...
redis-node3    | 2632623:C 17 Jul 2025 13:05:48.821 # WARNING: Changing databases number from 16 to 1 since we are in cluster mode
redis-node4    | 2632634:C 17 Jul 2025 13:05:48.828 # WARNING: Changing databases number from 16 to 1 since we are in cluster mode
redis-acl      | 2632591:C 17 Jul 2025 13:05:48.799 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-acl      | 2632591:C 17 Jul 2025 13:05:48.799 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-acl      | 2632591:C 17 Jul 2025 13:05:48.799 * Redis version=7.2.7, bits=64, commit=00000000, modified=0, pid=2632591, just started
redis-sentinel | 2632597:X 17 Jul 2025 13:05:48.804 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-sentinel | 2632597:X 17 Jul 2025 13:05:48.804 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-sentinel | 2632597:X 17 Jul 2025 13:05:48.804 * Redis version=7.2.7, bits=64, commit=00000000, modified=0, pid=2632597, just started
redis-node1    | 2632610:C 17 Jul 2025 13:05:48.812 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-node1    | 2632610:C 17 Jul 2025 13:05:48.812 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-node2    | 2632615:C 17 Jul 2025 13:05:48.815 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-node2    | 2632615:C 17 Jul 2025 13:05:48.815 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-node3    | 2632623:C 17 Jul 2025 13:05:48.821 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-node3    | 2632623:C 17 Jul 2025 13:05:48.821 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-node4    | 2632634:C 17 Jul 2025 13:05:48.828 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-node4    | 2632634:C 17 Jul 2025 13:05:48.828 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-acl      | 2632591:C 17 Jul 2025 13:05:48.799 * Configuration loaded
redis-acl      | 2632591:M 17 Jul 2025 13:05:48.800 * monotonic clock: POSIX clock_gettime
redis-acl      |                 _._                                                  
redis-sentinel | 2632597:X 17 Jul 2025 13:05:48.804 * Configuration loaded
redis-sentinel | 2632597:X 17 Jul 2025 13:05:48.804 * monotonic clock: POSIX clock_gettime
redis-sentinel |                 _._                                                  
redis-node1    | 2632610:C 17 Jul 2025 13:05:48.812 * Redis version=7.2.7, bits=64, commit=00000000, modified=0, pid=2632610, just started
redis-node1    | 2632610:C 17 Jul 2025 13:05:48.812 * Configuration loaded
redis-node1    | 2632610:M 17 Jul 2025 13:05:48.812 * monotonic clock: POSIX clock_gettime
redis-node2    | 2632615:C 17 Jul 2025 13:05:48.815 * Redis version=7.2.7, bits=64, commit=00000000, modified=0, pid=2632615, just started
redis-node2    | 2632615:C 17 Jul 2025 13:05:48.815 * Configuration loaded
redis-node2    | 2632615:M 17 Jul 2025 13:05:48.815 * monotonic clock: POSIX clock_gettime
redis-node3    | 2632623:C 17 Jul 2025 13:05:48.821 * Redis version=7.2.7, bits=64, commit=00000000, modified=0, pid=2632623, just started
redis-node3    | 2632623:C 17 Jul 2025 13:05:48.821 * Configuration loaded
redis-node3    | 2632623:M 17 Jul 2025 13:05:48.822 * monotonic clock: POSIX clock_gettime
redis-node4    | 2632634:C 17 Jul 2025 13:05:48.828 * Redis version=7.2.7, bits=64, commit=00000000, modified=0, pid=2632634, just started
redis-node4    | 2632634:C 17 Jul 2025 13:05:48.828 * Configuration loaded
redis-node4    | 2632634:M 17 Jul 2025 13:05:48.828 * monotonic clock: POSIX clock_gettime
redis-acl      |            _.-``__ ''-._                                             
redis-acl      |       _.-``    `.  `_.  ''-._           Redis 7.2.7 (00000000/0) 64 bit
redis-sentinel |            _.-``__ ''-._                                             
redis-sentinel |       _.-``    `.  `_.  ''-._           Redis 7.2.7 (00000000/0) 64 bit
redis-node1    |                 _._                                                  
redis-node2    |                 _._                                                  
redis-node3    |                 _._                                                  
redis-node4    |                 _._                                                  
redis-acl      |   .-`` .-```.  ```\/    _.,_ ''-._                                  
redis-sentinel |   .-`` .-```.  ```\/    _.,_ ''-._                                  
redis-node1    |            _.-``__ ''-._                                             
redis-node2    |            _.-``__ ''-._                                             
redis-node3    |            _.-``__ ''-._                                             
redis-node4    |            _.-``__ ''-._                                             
redis-acl      |  (    '      ,       .-`  | `,    )     Running in standalone mode
redis-sentinel |  (    '      ,       .-`  | `,    )     Running in sentinel mode
redis-node1    |       _.-``    `.  `_.  ''-._           Redis 7.2.7 (00000000/0) 64 bit
redis-node2    |       _.-``    `.  `_.  ''-._           Redis 7.2.7 (00000000/0) 64 bit
redis-node3    |       _.-``    `.  `_.  ''-._           Redis 7.2.7 (00000000/0) 64 bit
redis-node4    |       _.-``    `.  `_.  ''-._           Redis 7.2.7 (00000000/0) 64 bit
redis-node1    |   .-`` .-```.  ```\/    _.,_ ''-._                                  
redis-node2    |   .-`` .-```.  ```\/    _.,_ ''-._                                  
redis-node3    |   .-`` .-```.  ```\/    _.,_ ''-._                                  
redis-node4    |   .-`` .-```.  ```\/    _.,_ ''-._                                  
redis-acl      |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 7099
redis-sentinel |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 26379
redis-acl      |  |    `-._   `._    /     _.-'    |     PID: 2632591
redis-acl      |   `-._    `-._  `-./  _.-'    _.-'                                   
redis-acl      |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-acl      |  |    `-._`-._        _.-'_.-'    |           https://redis.io       
redis-acl      |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-acl      |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-acl      |  |    `-._`-._        _.-'_.-'    |                                  
redis-sentinel |  |    `-._   `._    /     _.-'    |     PID: 2632597
redis-sentinel |   `-._    `-._  `-./  _.-'    _.-'                                   
redis-sentinel |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-sentinel |  |    `-._`-._        _.-'_.-'    |           https://redis.io       
redis-sentinel |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-sentinel |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-sentinel |  |    `-._`-._        _.-'_.-'    |                                  
redis-node1    |  (    '      ,       .-`  | `,    )     Running in cluster mode
redis-node1    |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 7079
redis-node1    |  |    `-._   `._    /     _.-'    |     PID: 2632610
redis-node1    |   `-._    `-._  `-./  _.-'    _.-'                                   
redis-node1    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node1    |  |    `-._`-._        _.-'_.-'    |           https://redis.io       
redis-node1    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node2    |  (    '      ,       .-`  | `,    )     Running in cluster mode
redis-node2    |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 7080
redis-node2    |  |    `-._   `._    /     _.-'    |     PID: 2632615
redis-node2    |   `-._    `-._  `-./  _.-'    _.-'                                   
redis-node2    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node2    |  |    `-._`-._        _.-'_.-'    |           https://redis.io       
redis-node2    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node3    |  (    '      ,       .-`  | `,    )     Running in cluster mode
redis-node3    |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 7081
redis-node3    |  |    `-._   `._    /     _.-'    |     PID: 2632623
redis-node3    |   `-._    `-._  `-./  _.-'    _.-'                                   
redis-node3    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node3    |  |    `-._`-._        _.-'_.-'    |           https://redis.io       
redis-node3    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node4    |  (    '      ,       .-`  | `,    )     Running in cluster mode
redis-node4    |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 7082
redis-node4    |  |    `-._   `._    /     _.-'    |     PID: 2632634
redis-node4    |   `-._    `-._  `-./  _.-'    _.-'                                   
redis-node4    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node4    |  |    `-._`-._        _.-'_.-'    |           https://redis.io       
redis-node4    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-acl      |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-acl      |       `-._    `-.__.-'    _.-'                                       
redis-acl      |           `-._        _.-'                                           
redis-acl      |               `-.__.-'                                               
redis-acl      | 
redis-sentinel |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-sentinel |       `-._    `-.__.-'    _.-'                                       
redis-sentinel |           `-._        _.-'                                           
redis-sentinel |               `-.__.-'                                               
redis-sentinel | 
redis-node1    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node1    |  |    `-._`-._        _.-'_.-'    |                                  
redis-node1    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node1    |       `-._    `-.__.-'    _.-'                                       
redis-node2    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node2    |  |    `-._`-._        _.-'_.-'    |                                  
redis-node2    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node2    |       `-._    `-.__.-'    _.-'                                       
redis-node3    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node3    |  |    `-._`-._        _.-'_.-'    |                                  
redis-node3    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node3    |       `-._    `-.__.-'    _.-'                                       
redis-node4    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node4    |  |    `-._`-._        _.-'_.-'    |                                  
redis-node4    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node4    |       `-._    `-.__.-'    _.-'                                       
redis-acl      | 2632591:M 17 Jul 2025 13:05:48.801 * Server initialized
redis-acl      | 2632591:M 17 Jul 2025 13:05:48.801 * Ready to accept connections tcp
redis-sentinel | 2632597:X 17 Jul 2025 13:05:48.805 * Sentinel new configuration saved on disk
redis-sentinel | 2632597:X 17 Jul 2025 13:05:48.805 * Sentinel ID is 2e3def4f0b908f5917de3a4f27cfa0291314a5c1
redis-node1    |           `-._        _.-'                                           
redis-node1    |               `-.__.-'                                               
redis-node1    | 
redis-node2    |           `-._        _.-'                                           
redis-node2    |               `-.__.-'                                               
redis-node2    | 
redis-node3    |           `-._        _.-'                                           
redis-node3    |               `-.__.-'                                               
redis-node3    | 
redis-node4    |           `-._        _.-'                                           
redis-node4    |               `-.__.-'                                               
redis-node4    | 
redis-sentinel | 2632597:X 17 Jul 2025 13:05:48.805 # +monitor master mymaster 127.0.0.1 6379 quorum 2
redis-node1    | 2632610:M 17 Jul 2025 13:05:48.813 * Node configuration loaded, I'm a1c1f6c5cb54b42f99b4a5685732854d175ad2c0
redis-node1    | 2632610:M 17 Jul 2025 13:05:48.813 * Server initialized
redis-node2    | 2632615:M 17 Jul 2025 13:05:48.816 * Node configuration loaded, I'm 20027176d468e0e940924879da9851ab45c69439
redis-node2    | 2632615:M 17 Jul 2025 13:05:48.817 * Server initialized
redis-node3    | 2632623:M 17 Jul 2025 13:05:48.822 * Node configuration loaded, I'm d948130def0604d08b1373ebc871083a37f912c2
redis-node3    | 2632623:M 17 Jul 2025 13:05:48.823 * Server initialized
redis-node4    | 2632634:M 17 Jul 2025 13:05:48.829 * Node configuration loaded, I'm 8194f94f95cb04f9c42da2703014c396dcfe65a2
redis-node4    | 2632634:M 17 Jul 2025 13:05:48.829 * Server initialized
redis-node1    | 2632610:M 17 Jul 2025 13:05:48.814 * Ready to accept connections tcp
redis-node2    | 2632615:M 17 Jul 2025 13:05:48.817 * Ready to accept connections tcp
redis-node3    | 2632623:M 17 Jul 2025 13:05:48.823 * Ready to accept connections tcp
redis-node4    | 2632634:M 17 Jul 2025 13:05:48.829 * Ready to accept connections tcp
redis-node2    | 2632615:M 17 Jul 2025 13:05:48.832 * Replica 127.0.0.1:7082 asks for synchronization
redis-node4    | 2632634:S 17 Jul 2025 13:05:48.831 * Before turning into a replica, using my own master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer.
redis-node4    | 2632634:S 17 Jul 2025 13:05:48.831 * Connecting to MASTER 127.0.0.1:7080
redis-node2    | 2632615:M 17 Jul 2025 13:05:48.832 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'e95595e62dbbbf3838e3d67e064148d0feb6e464', my replication IDs are 'fba225407a152d41b3b1dc14997af774314a0630' and '0000000000000000000000000000000000000000')
redis-node4    | 2632634:S 17 Jul 2025 13:05:48.831 * MASTER <-> REPLICA sync started
redis-node2    | 2632615:M 17 Jul 2025 13:05:48.832 * Replication backlog created, my new replication IDs are 'a08328699982740fcb12098f3ab50e57f93e57fb' and '0000000000000000000000000000000000000000'
redis-node2    | 2632615:M 17 Jul 2025 13:05:48.832 * Delay next BGSAVE for diskless SYNC
redis-node4    | 2632634:S 17 Jul 2025 13:05:48.831 * Cluster state changed: ok
redis-node4    | 2632634:S 17 Jul 2025 13:05:48.831 * Non blocking connect for SYNC fired the event.
redis-node4    | 2632634:S 17 Jul 2025 13:05:48.831 * Master replied to PING, replication can continue...
redis-node4    | 2632634:S 17 Jul 2025 13:05:48.832 * Trying a partial resynchronization (request e95595e62dbbbf3838e3d67e064148d0feb6e464:1).
redis-node5    | 2632642:C 17 Jul 2025 13:05:48.834 # WARNING: Changing databases number from 16 to 1 since we are in cluster mode
redis-node5    | 2632642:C 17 Jul 2025 13:05:48.834 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-node5    | 2632642:C 17 Jul 2025 13:05:48.834 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-node5    | 2632642:C 17 Jul 2025 13:05:48.834 * Redis version=7.2.7, bits=64, commit=00000000, modified=0, pid=2632642, just started
redis-node5    | 2632642:C 17 Jul 2025 13:05:48.834 * Configuration loaded
redis-node5    | 2632642:M 17 Jul 2025 13:05:48.835 * monotonic clock: POSIX clock_gettime
redis-node5    |                 _._                                                  
redis-node5    |            _.-``__ ''-._                                             
redis-node5    |       _.-``    `.  `_.  ''-._           Redis 7.2.7 (00000000/0) 64 bit
redis-node5    |   .-`` .-```.  ```\/    _.,_ ''-._                                  
redis-node5    |  (    '      ,       .-`  | `,    )     Running in cluster mode
redis-node5    |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 7083
redis-node5    |  |    `-._   `._    /     _.-'    |     PID: 2632642
redis-node5    |   `-._    `-._  `-./  _.-'    _.-'                                   
redis-node5    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node5    |  |    `-._`-._        _.-'_.-'    |           https://redis.io       
redis-node5    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node5    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node5    |  |    `-._`-._        _.-'_.-'    |                                  
redis-node5    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node5    |       `-._    `-.__.-'    _.-'                                       
redis-node5    |           `-._        _.-'                                           
redis-node5    |               `-.__.-'                                               
redis-node5    | 
redis-node5    | 2632642:M 17 Jul 2025 13:05:48.835 * Node configuration loaded, I'm 778e8e0344fb3ad3249cc156d41e41109248fd71
redis-node5    | 2632642:M 17 Jul 2025 13:05:48.836 * Server initialized
redis-node5    | 2632642:M 17 Jul 2025 13:05:48.836 * Ready to accept connections tcp
redis-node5    | 2632642:S 17 Jul 2025 13:05:48.837 * Before turning into a replica, using my own master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer.
redis-node5    | 2632642:S 17 Jul 2025 13:05:48.837 * Connecting to MASTER 127.0.0.1:7081
redis-node6    | 2632651:C 17 Jul 2025 13:05:48.837 # WARNING: Changing databases number from 16 to 1 since we are in cluster mode
redis-node5    | 2632642:S 17 Jul 2025 13:05:48.837 * MASTER <-> REPLICA sync started
redis-node6    | 2632651:C 17 Jul 2025 13:05:48.837 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-node5    | 2632642:S 17 Jul 2025 13:05:48.837 * Cluster state changed: ok
redis-node6    | 2632651:C 17 Jul 2025 13:05:48.837 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-node6    | 2632651:C 17 Jul 2025 13:05:48.837 * Redis version=7.2.7, bits=64, commit=00000000, modified=0, pid=2632651, just started
redis-node6    | 2632651:C 17 Jul 2025 13:05:48.837 * Configuration loaded
redis-node6    | 2632651:M 17 Jul 2025 13:05:48.838 * monotonic clock: POSIX clock_gettime
redis-node5    | 2632642:S 17 Jul 2025 13:05:48.838 * Non blocking connect for SYNC fired the event.
redis-node5    | 2632642:S 17 Jul 2025 13:05:48.838 * Master replied to PING, replication can continue...
redis-node6    |                 _._                                                  
redis-node6    |            _.-``__ ''-._                                             
redis-node6    |       _.-``    `.  `_.  ''-._           Redis 7.2.7 (00000000/0) 64 bit
redis-node6    |   .-`` .-```.  ```\/    _.,_ ''-._                                  
redis-node6    |  (    '      ,       .-`  | `,    )     Running in cluster mode
redis-node6    |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 7084
redis-node6    |  |    `-._   `._    /     _.-'    |     PID: 2632651
redis-node6    |   `-._    `-._  `-./  _.-'    _.-'                                   
redis-node6    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node6    |  |    `-._`-._        _.-'_.-'    |           https://redis.io       
redis-node6    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node6    |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
redis-node6    |  |    `-._`-._        _.-'_.-'    |                                  
redis-node6    |   `-._    `-._`-.__.-'_.-'    _.-'                                   
redis-node6    |       `-._    `-.__.-'    _.-'                                       
redis-node6    |           `-._        _.-'                                           
redis-node6    |               `-.__.-'                                               
redis-node6    | 
redis-node6    | 2632651:M 17 Jul 2025 13:05:48.838 * Node configuration loaded, I'm 2a86e6658cd1e45f2c521cb00eb7927f8cffc50d
redis-node5    | 2632642:S 17 Jul 2025 13:05:48.838 * Trying a partial resynchronization (request 8e3d79d160e14937e4b8890a6e0786766800b489:1).
redis-node3    | 2632623:M 17 Jul 2025 13:05:48.838 * Replica 127.0.0.1:7083 asks for synchronization
redis-node3    | 2632623:M 17 Jul 2025 13:05:48.838 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for '8e3d79d160e14937e4b8890a6e0786766800b489', my replication IDs are '8d809248568081f1ed90c177d2ef6e858d4283d4' and '0000000000000000000000000000000000000000')
redis-node3    | 2632623:M 17 Jul 2025 13:05:48.838 * Replication backlog created, my new replication IDs are 'f1390dba90d5bacc9fd6dfaa8a0e8fb5787fcf03' and '0000000000000000000000000000000000000000'
redis-node3    | 2632623:M 17 Jul 2025 13:05:48.838 * Delay next BGSAVE for diskless SYNC
redis-node6    | 2632651:M 17 Jul 2025 13:05:48.839 * Server initialized
redis-node6    | 2632651:M 17 Jul 2025 13:05:48.839 * Ready to accept connections tcp
redis-node6    | 2632651:S 17 Jul 2025 13:05:48.840 * Before turning into a replica, using my own master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer.
redis-node6    | 2632651:S 17 Jul 2025 13:05:48.840 * Connecting to MASTER 127.0.0.1:7079
redis-node6    | 2632651:S 17 Jul 2025 13:05:48.840 * MASTER <-> REPLICA sync started
redis-node6    | 2632651:S 17 Jul 2025 13:05:48.840 * Cluster state changed: ok
redis-node6    | 2632651:S 17 Jul 2025 13:05:48.840 * Non blocking connect for SYNC fired the event.
redis-node6    | 2632651:S 17 Jul 2025 13:05:48.841 * Master replied to PING, replication can continue...
redis-node6    | 2632651:S 17 Jul 2025 13:05:48.841 * Trying a partial resynchronization (request 84e2f98c11edd7d5a8df62b92b009e1e56394b1b:1).
redis-node1    | 2632610:M 17 Jul 2025 13:05:48.841 * Replica 127.0.0.1:7084 asks for synchronization
redis-node1    | 2632610:M 17 Jul 2025 13:05:48.841 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for '84e2f98c11edd7d5a8df62b92b009e1e56394b1b', my replication IDs are '8026dac96537eb57051d15da509b477645bdda88' and '0000000000000000000000000000000000000000')
redis-node1    | 2632610:M 17 Jul 2025 13:05:48.841 * Replication backlog created, my new replication IDs are '3340121f041a6934dd4833e5fecfae64cab7d57c' and '0000000000000000000000000000000000000000'
redis-node1    | 2632610:M 17 Jul 2025 13:05:48.841 * Delay next BGSAVE for diskless SYNC
redis          | Exited with code 1
redis-acl      | Interrupting...
redis-sentinel | Interrupting...
redis-node1    | Interrupting...
redis-node2    | Interrupting...
redis-node3    | Interrupting...
redis-node4    | Interrupting...
redis-acl      | 2632591:signal-handler (1752750349) Received SIGINT scheduling shutdown...
redis-sentinel | 2632597:signal-handler (1752750349) Received SIGINT scheduling shutdown...
redis-node5    | Interrupting...
redis-node6    | Interrupting...
redis-node2    | 2632615:signal-handler (1752750349) Received SIGINT scheduling shutdown...
redis-node4    | 2632634:signal-handler (1752750349) Received SIGINT scheduling shutdown...
redis-node1    | 2632610:signal-handler (1752750349) Received SIGINT scheduling shutdown...
redis-node3    | 2632623:signal-handler (1752750349) Received SIGINT scheduling shutdown...
redis-node5    | 2632642:signal-handler (1752750349) Received SIGINT scheduling shutdown...
redis-node6    | 2632651:signal-handler (1752750349) Received SIGINT scheduling shutdown...
redis-acl      | 2632591:M 17 Jul 2025 13:05:49.103 * User requested shutdown...
redis-acl      | 2632591:M 17 Jul 2025 13:05:49.103 # Redis is now ready to exit, bye bye...
redis-sentinel | 2632597:X 17 Jul 2025 13:05:49.109 * User requested shutdown...
redis-sentinel | 2632597:X 17 Jul 2025 13:05:49.109 # Sentinel is now ready to exit, bye bye...
redis-node1    | 2632610:M 17 Jul 2025 13:05:49.116 * User requested shutdown...
redis-node1    | 2632610:M 17 Jul 2025 13:05:49.116 * 1 of 1 replicas are in sync when shutting down.
redis-node1    | 2632610:M 17 Jul 2025 13:05:49.116 # Redis is now ready to exit, bye bye...
redis-node6    | 2632651:S 17 Jul 2025 13:05:49.117 # Failed to read response from the server: Success
redis-node6    | 2632651:S 17 Jul 2025 13:05:49.117 # Master did not reply to PSYNC, will try later
redis-node2    | 2632615:M 17 Jul 2025 13:05:49.120 * User requested shutdown...
redis-node2    | 2632615:M 17 Jul 2025 13:05:49.120 * 1 of 1 replicas are in sync when shutting down.
redis-node2    | 2632615:M 17 Jul 2025 13:05:49.120 # Redis is now ready to exit, bye bye...
redis-node4    | 2632634:S 17 Jul 2025 13:05:49.121 # Failed to read response from the server: Success
redis-node4    | 2632634:S 17 Jul 2025 13:05:49.121 # Master did not reply to PSYNC, will try later
redis-node3    | 2632623:M 17 Jul 2025 13:05:49.126 * User requested shutdown...
redis-node3    | 2632623:M 17 Jul 2025 13:05:49.126 * 1 of 1 replicas are in sync when shutting down.
redis-node3    | 2632623:M 17 Jul 2025 13:05:49.126 # Redis is now ready to exit, bye bye...
redis-node5    | 2632642:S 17 Jul 2025 13:05:49.127 # Failed to read response from the server: Success
redis-node5    | 2632642:S 17 Jul 2025 13:05:49.127 # Master did not reply to PSYNC, will try later
redis-node4    | 2632634:S 17 Jul 2025 13:05:49.132 * User requested shutdown...
redis-node4    | 2632634:S 17 Jul 2025 13:05:49.132 # Redis is now ready to exit, bye bye...
redis-node5    | 2632642:S 17 Jul 2025 13:05:49.139 * User requested shutdown...
redis-node5    | 2632642:S 17 Jul 2025 13:05:49.139 # Redis is now ready to exit, bye bye...
redis-node6    | 2632651:S 17 Jul 2025 13:05:49.143 * User requested shutdown...
redis-node6    | 2632651:S 17 Jul 2025 13:05:49.143 # Redis is now ready to exit, bye bye...
redis-acl      | Exited with code 0
redis-node6    | Exited with code 0
redis-sentinel | Exited with code 0
redis-node1    | Exited with code 0
redis-node5    | Exited with code 0
redis-node3    | Exited with code 0
redis-node2    | Exited with code 0
redis-node4    | Exited with code 0

ostrolucky · 2025-07-18T11:34:16Z

Well you are using made up API RedisArray::getHosts(), that's why.

…ue-195

shakaran added 3 commits July 16, 2025 20:53

feat: implement redis array on phpredis. Issue snc#195

3b676a1

fix: phpsalm warnings errors

235c860

fix: remove old test with warning about no support

7f8d737

shakaran changed the title ~~feat: implement redis array on phpredis. Issue #195~~ [DRAFT] feat: implement redis array on phpredis. Issue #195 Jul 16, 2025

shakaran added 16 commits July 16, 2025 21:14

fix: default values expected on tests

aed65de

fix: phpsalm and phpcbf again

8265b1b

fix: wrong remove use cases phpbcf

4b0ccf5

fix: use logic exception missing

7b4e134

fix: add option redis_array in xsd

57e5d22

fix: missing use relay sentinel

862cafb

fix: issues with place for redis_array

8be8c60

fix: return tests expected

042d81a

fix: more fixes for psalm

961c176

fix: more fixes formatting

06efc01

fix: try to fix psalm again

6488a89

fix: warnings again

1f40829

fix: try last one psalm

c3912b1

fix: skip psalm warning

8447a8c

fix: spaces

eb477c7

fix: remove wrong scan option from other PR

e4a569b

ostrolucky force-pushed the master branch 3 times, most recently from 37c8fe3 to e049151 Compare July 18, 2025 10:25

Merge branch 'master' into feat/implement-redis-array-on-phpredis-iss…

66bc3b3

…ue-195

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[DRAFT] feat: implement redis array on phpredis. Issue #195 #746

[DRAFT] feat: implement redis array on phpredis. Issue #195 #746

Uh oh!

shakaran commented Jul 16, 2025

Uh oh!

shakaran commented Jul 17, 2025

Uh oh!

ostrolucky commented Jul 17, 2025

Uh oh!

shakaran commented Jul 17, 2025

Uh oh!

ostrolucky commented Jul 18, 2025

Uh oh!

Uh oh!

[DRAFT] feat: implement redis array on phpredis. Issue #195 #746

Are you sure you want to change the base?

[DRAFT] feat: implement redis array on phpredis. Issue #195 #746

Uh oh!

Conversation

shakaran commented Jul 16, 2025

Uh oh!

shakaran commented Jul 17, 2025

Uh oh!

ostrolucky commented Jul 17, 2025

Uh oh!

shakaran commented Jul 17, 2025

Uh oh!

ostrolucky commented Jul 18, 2025

Uh oh!

Uh oh!