Leo Barcellos

I just reduced the chunk size from 100 to 25 on CampaignService:generateSendList, and also on CampaignEnqueueSendsJobs:handler. I've also added a pool config on database: `pool: { min: 2, max: 25...

Hmm, probably related, worker CPU Utilization was around 97% when it occurred. But it's still weird that this error happened. I also tried to check on event `email_failed` on the...

@pushchris Yes, some sends on the same blast campaign are going through normally and some are not, that is the weird part. Today we experienced same on 3 blasts from...

I just ran these commands on redis, hope this will prevent the second error mentioned. ``` SLAVEOF NO ONE REPLICAOF NO ONE ```

@pushchris I'm running on AWS ECS Fargate, I have a task with worker and a separated task with redis. The "slave" error went away with the commands I've mentioned earlier.....

Update: Redis issue was not related to memory issue. I just updated my deploy to a EC2 "monolith" (ui / api / worker / redis) with AWS RDS It's running...

By the way, I just checked this answer on stack overflow: https://stackoverflow.com/questions/55613789/how-to-fix-fatal-error-ineffective-mark-compacts-near-heap-limit-allocation-fa I just updated the env for the worker like this: `NODE_OPTIONS=--max_old_space_size=7580` Let's see if this helps.

Well, it keep happening, however I'm not experiencing deadlock issues or stuck campaigns anymore. I guess it was happening only on ECS FARGATE.  It's...

Yeah, I was at `debug` level to actually see what's going on. I returned it back to `error` log level, but it's still happening. I will drop the screenshot here,...

More info, memory of worker instance keep increasing.. that's why things start to fail at certain point:  It starts like 50mb.. 70mb, and then...