Unack messages

[Нурлан]

Good afternoon.

How to fix unack messages? 

We running SpringBoot microservices working with rabbitmq + firebase in k8s cluster for send iOS/Android push notification for our clients.

At first we thought our SpringBoot notification app can't handle request from rabbit, increased pods count to 5, it's didnt help.

We running in cluster.

SpringBoot notification app(5 pods) 

rabbitmq(1 pod)

what could be the reason for this behavior?

[Нурлан]

also i tried to set messages TTL with command: rabbitmqctl set_policy TTL ".*" '{"message-ttl":180}' --apply-to queues

четверг, 15 октября 2020 г. в 11:21:19 UTC+6, Нурлан:

[Michael Klishin]

In order to "fix" unacknowledged deliveries your applications must acknowledge them.

See tutorial 2 [1], a guide on acknowledgements [2] and keep in mind that message TTL only applies

to messages in Ready state; delivered but unacknowledged messages will not expire by design as your

consumers might still be processing them.

1. https://www.rabbitmq.com/getstarted.html

2. https://www.rabbitmq.com/confirms.html

[Нурлан]

somehow possible to clear unacked messages manually?

пятница, 16 октября 2020 г. в 03:29:10 UTC+6, Michael Klishin:

[Wesley Peng]

may you check this thread?

https://stackoverflow.com/questions/52505359/rabbitmq-removed-unacked-messages-on-a-queue-that-does-not-have-any-consumers

[Michael Klishin]

Closing the channel (or connection) on which said deliveries originated would auto-requeue them [1].

1. https://www.rabbitmq.com/confirms.html#automatic-requeueing