Armen
Armen
@walkor thank you for information!
@cayolblake Yeah, unfortunately after couple of days trying to implement clean solution, I was forced to abandon workerman in flavor of C++ application and "true" threads with "true" shared memory....
Same thing ;( Please update bindings
@michael-grunder thx for reply. This is exactly what I am doing. Post fork in freshly created process I am creating RedisCluster by simply calling new RedisCluster(...). The problem is that...
@michael-grunder Here you go! https://github.com/mrAndersen/swoole-phpredis-mutliprocess To run this, execute - docker-compose up -d --build - docker exec -it t_swoole composer i - ./cluster.sh (This will create actual redis cluster locally)...
Seems like spl_object_hash is working per process. Seems like even if it shows same hashes, in reality those objects are different objects. You can take a look at last commit...
So in continuation - the exact errors I am getting are ``` RedisException: read error on connection to redis1:6380 ``` OR ``` RedisException: socket error on read socket ```
@michael-grunder Meanwhile, maybe I can somehow disable that caching mechanic? Maybe I can pass some specific $context into RedisCluster instance? Because really everything works fine, except for that random errors,...
Thx for advise. For the record. I managed to make it working setting persistent = false during object creation and setting redis.pconnect.pooling_enabled = 0, however the actual TCP connections established...