Oleksii Vasyliev

```bash $ ps aux | grep 'Z' USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 89379 1.0 0.0 0 0 ? Z 20:35 0:03 [java] root...

yes, this week sentry stop accept errors and transactions. On server I see > There are 37 zombie processes. So this is very bad issue. Sentry is latest - 24.2.0

ok, looks like I found where this issue came from. You need replace in docker-compose.yml: ``` test: ["CMD-SHELL", "/usr/bin/kafka-topics --bootstrap-server kafka:9092 --list"] ``` to old one: ``` test: ["CMD-SHELL", "nc...

we start getting same issue with redis after update from 22.12.0 to 23.2.0 (on this update we switched to aws s3 for Node Storage) 

@namco1992 it was merged, so it already in yml file, which was fetched for 23.2.0 update

Yes, but this is not a fix for bug. It just hide problem by removing redis keys, when it is not time to remove it (we don't have space for...

I did some monitoring for redis. Hard to say the reason of memory growth (too many events), but here interesting pattern: Insert some keys with pattern "c:1:e::" ``` "SETEX" "c:1:e:aa4223d9fb9b4acf953868aa04d00e87:46"...

``` RedisClient::ReadTimeoutError: Unknown Error (hiredis_read) (RedisClient::ReadTimeoutError) from hiredis-client (0.20.0) lib/redis_client/hiredis_connection.rb:95:in `_read' from hiredis-client (0.20.0) lib/redis_client/hiredis_connection.rb:95:in `read' from redis-client (0.20.0) lib/redis_client/connection_mixin.rb:31:in `call' from redis-client (0.20.0) lib/redis_client.rb:318:in `block (2 levels) in blocking_call'...

@Amarnath510 yep, it is hard coded. You can create PR to allow to change this

@colorfulfool how about read it from DOM?