Subramanian-ERS

Results 7 comments of Subramanian-ERS

Redis::ProtocolError: Got 'Protocol error, got "\r" as reply type byte' as initial reply byte. If you're in a forking environment, such as Unicorn, you need to connect to Redis after forking.

No, I never did. redis-rb always took care of the reconnections as that did not require me handling the disconnections manually in code during forking process.

Redis::ProtocolError: Got 'Protocol error, got "\r" as reply type byte' as initial reply byte. If you're in a forking environment, such as Unicorn, you need to connect to Redis after forking.

Yes, I think the same as well. But instead of disconnecting in the parent, I would prefer reconnecting in the child or forked processes. Can you point me to the...

Redis::ProtocolError: Got 'Protocol error, got "\r" as reply type byte' as initial reply byte. If you're in a forking environment, such as Unicorn, you need to connect to Redis after forking.

No, @byroot. I did not configure that option. It is very strange as to why I get this issue only with Redis cluster connection string.

Redis::ProtocolError: Got 'Protocol error, got "\r" as reply type byte' as initial reply byte. If you're in a forking environment, such as Unicorn, you need to connect to Redis after forking.

@byroot How and where do you suggest I reconnect to Redis in my Rails application? I initialise a Redis client in one of the initializer files. Is there a Redis.reconnect...

Redis::ProtocolError: Got 'Protocol error, got "\r" as reply type byte' as initial reply byte. If you're in a forking environment, such as Unicorn, you need to connect to Redis after forking.

@byroot Found the issue to be related with Delayed Jobs in my application. For some reason, the Redis cluster connection has issues when the Delayed Job is a long running...

Redis::ProtocolError: Got 'Protocol error, got "\r" as reply type byte' as initial reply byte. If you're in a forking environment, such as Unicorn, you need to connect to Redis after forking.

Could it be possible that the error message is incorrect? Maybe it is a data issue? And also, would this issue be fixed if we do not use hiredis?

Redis::ProtocolError: Got 'Protocol error, got "\r" as reply type byte' as initial reply byte. If you're in a forking environment, such as Unicorn, you need to connect to Redis after forking.

Update: @byroot I have not been able to reproduce the issue since I removed hiredis from my application. Could the problem be a combination of using Redis cluster and hiredis?