त्रुटि र पुनः प्रयास सम्हालनु विश्वसनीय RabbitMQ उपभोक्ताहरूका लागि महत्त्वपूर्ण छ — जब सन्देश प्रक्रिया विफल हुन्छ (पुनः प्रयास, dead-letter, वा खारेज गर्नु) तब के गर्ने भनेर निर्णय गर्नु। उचित त्रुटि सम्हालनले हराएका सन्देशहरू र अड्किएका उपभोक्ताहरू रोक्छ।
समस्या
When a consumer fails to process a message (bad data, downstream failure, bug):
→ requeue forever → a "poison" message blocks the queue (retried endlessly)
→ discard → message LOST
→ crash → reprocess, possibly stuck again
→ need a deliberate strategy.
पुनः प्रयास रणनीतिहरू
✓ NACK + REQUEUE → reject and requeue for retry (but limit retries — don't requeue forever)
✓ RETRY WITH BACKOFF → retry transient failures with increasing delays (e.g. via a delayed
retry queue with TTL → requeue after a delay)
✓ RETRY LIMIT → track attempts; after N failures → DEAD LETTER (don't retry forever)
✓ Distinguish TRANSIENT (retry) vs PERMANENT (dead-letter immediately) failures
