We have upgrade two customers to 26r1 and it seem like the ifsapp-connect pod has issues. It crash loops (OOMKILLED) using 2,5 core of cpu and over 4/5GB of memory even if now messages is in state processing.
We have also observer that execute in order queue dosn’t work as expected (don’t stop processing on failed messages and runns multiple messages in parallel) and on the in sequence queue you can’t control the amount of threads… It just ends up with a lot’s of messages in processing
Has anybody seen similar issues on ifsapp-connect in 26r1 or do we need ro report it as an bug to IFS Support?
Question
Unstable/high cpu/high memory ifsapp-connect pod in 26r1 all su upt to su3
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.