Keep retrying the indexer's durable NATS consumer after a deploy

FixEmailService
Ya
5 Agosti 2026, 23:23 UTC
Mwandishi
Kamo
Ahadi ya
038196a

A rolling deploy overlaps pods and the outgoing one still holds the durable consumer, so the incoming pod's bind to "email-metadata-indexer" fails with [SUB-90012] Consumer is already bound to a subscription. start() ran once from @PostConstruct, logged the error and gave up, so push indexing stayed dead for the entire life of that pod -- every deploy silently stopped indexing new mail until someone restarted it by hand, and nothing surfaced that it had happened. Retry on a daemon scheduler until the old pod releases the consumer, and stop cleanly on shutdown so the retry cannot outlive the bean.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei