{"id":83,"date":"2026-10-01T18:30:00","date_gmt":"2026-10-01T18:30:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/01\/dead-letter-queue-poison-message\/"},"modified":"2026-10-01T18:30:00","modified_gmt":"2026-10-01T18:30:00","slug":"dead-letter-queue-poison-message","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/01\/dead-letter-queue-poison-message\/","title":{"rendered":"Dead Letter Queue Bir \u00c7\u00f6p Kutusu De\u011fildir"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Bir kuyruk t\u00fcketicisi d\u00fc\u015f\u00fcn\u00fcn.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mesaj\u0131 al\u0131r, i\u015fler, onaylar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir g\u00fcn kuyru\u011fa bozuk bir mesaj gelir. Belki zorunlu bir alan bo\u015ftur. Belki referans verdi\u011fi m\u00fc\u015fteri silinmi\u015ftir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consumer exception f\u0131rlat\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mesaj onaylanmad\u0131\u011f\u0131 i\u00e7in kuyru\u011fa geri d\u00f6ner.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consumer onu tekrar al\u0131r. Tekrar hata verir. Tekrar kuyru\u011fa d\u00f6ner.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Saniyede y\u00fczlerce kez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Arkas\u0131nda bekleyen binlerce sa\u011fl\u0131kl\u0131 mesaj ise hi\u00e7 i\u015flenmez.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Poison message<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu t\u00fcr mesajlara poison message deniyor. Ne kadar tekrar denenirse denensin ba\u015far\u0131l\u0131 olamayacak mesajlar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Problem tek mesaj\u0131n i\u015flenememesi de\u011fil. O mesaj\u0131n b\u00fct\u00fcn kuyru\u011fu kilitlemesi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6zellikle s\u0131ral\u0131 i\u015flenen kuyruklarda, \u00f6rne\u011fin bir Kafka partition&#8217;\u0131nda, consumer bozuk mesaj\u0131 ge\u00e7emedi\u011fi s\u00fcrece arkas\u0131ndaki hi\u00e7bir mesaja ula\u015famaz. Consumer lag dakikalar i\u00e7inde b\u00fcy\u00fcr.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ge\u00e7ici ve kal\u0131c\u0131 hata ayr\u0131m\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Her hata ayn\u0131 de\u011fildir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Veritaban\u0131na k\u0131sa s\u00fcreli eri\u015filememesi ge\u00e7ici bir hatad\u0131r. Birka\u00e7 saniye sonra tekrar denemek muhtemelen ba\u015far\u0131l\u0131 olur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mesaj\u0131n JSON format\u0131n\u0131n bozuk olmas\u0131 kal\u0131c\u0131 bir hatad\u0131r. Bin kez denense de sonu\u00e7 de\u011fi\u015fmez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consumer&#8217;\u0131n ilk g\u00f6revi bu ayr\u0131m\u0131 yapmakt\u0131r:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>catch (TransientDataAccessException e) {\n    \/\/ tekrar dene\n}\ncatch (JsonParseException | ValidationException e) {\n    \/\/ tekrar deneme, do\u011frudan DLQ\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Kal\u0131c\u0131 hatalar\u0131 retry etmek sadece kaynak harcar.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Retry&#8217;\u0131 ana kuyruktan ay\u0131rmak<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ge\u00e7ici hatalar i\u00e7in retry gerekli. Ama retry&#8217;\u0131 ana kuyru\u011fu bloklamadan yapmak gerekir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yayg\u0131n bir y\u00f6ntem, gecikmeli retry kuyruklar\u0131 kullanmak:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>orders\norders.retry.1m\norders.retry.10m\norders.dlq<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130lk hata alan mesaj 1 dakikal\u0131k retry kuyru\u011funa gider. Orada da ba\u015far\u0131s\u0131z olursa 10 dakikal\u0131k kuyru\u011fa. H\u00e2l\u00e2 ba\u015far\u0131s\u0131zsa dead letter queue&#8217;ya.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ana kuyruk akmaya devam eder. Problemli mesaj bir kenarda, kendi temposunda tekrar denenir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spring Kafka&#8217;n\u0131n <code>@RetryableTopic<\/code> deste\u011fi bu yap\u0131y\u0131 birka\u00e7 sat\u0131r konfig\u00fcrasyonla kuruyor. RabbitMQ taraf\u0131nda dead letter exchange ve TTL kombinasyonu ile benzer bir yap\u0131 olu\u015fturulabiliyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama bir bedeli var: retry kuyru\u011fu kullan\u0131ld\u0131\u011f\u0131nda mesajlar\u0131n s\u0131ras\u0131 bozulur. Ayn\u0131 sipari\u015fe ait iki event varsa ve ilki retry kuyru\u011funa gittiyse, ikincisi ondan \u00f6nce i\u015flenebilir. S\u0131ralama \u00f6nemliyse bu ayr\u0131ca d\u00fc\u015f\u00fcn\u00fclmeli.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">DLQ&#8217;ya mesaj atmak i\u015fin yar\u0131s\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir\u00e7ok sistemde DLQ \u015f\u00f6yle \u00e7al\u0131\u015f\u0131r: ba\u015far\u0131s\u0131z mesajlar oraya gider ve bir daha kimse onlara bakmaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Birka\u00e7 ay sonra DLQ&#8217;da 40 bin mesaj vard\u0131r ve hi\u00e7 kimse bunlar\u0131n ne oldu\u011funu bilmez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu bir dead letter queue de\u011fil, sessizce veri kaybetmenin daha d\u00fczenli bir yoludur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bence bir DLQ&#8217;nun faydal\u0131 olmas\u0131 i\u00e7in \u00fc\u00e7 \u015fey gerekiyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Ba\u011flam.<\/strong> Mesajla birlikte hata mesaj\u0131, exception tipi, ka\u00e7 kez denendi\u011fi, hangi consumer&#8217;\u0131n ve hangi versiyonun hata verdi\u011fi saklanmal\u0131. Header&#8217;lar bunun i\u00e7in uygun.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>G\u00f6r\u00fcn\u00fcrl\u00fck.<\/strong> DLQ&#8217;ya mesaj d\u00fc\u015ft\u00fc\u011f\u00fcnde bir alarm \u00e7almal\u0131. DLQ boyutu bir metrik olarak izlenmeli. S\u0131f\u0131rdan farkl\u0131 bir DLQ, bir \u015feyin ters gitti\u011fini s\u00f6yler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Replay.<\/strong> Hata giderildikten sonra mesajlar\u0131 ana kuyru\u011fa geri g\u00f6nderebilecek bir ara\u00e7 olmal\u0131. Bug d\u00fczeltildi, deploy edildi, DLQ&#8217;daki 300 mesaj tekrar i\u015flendi. Bu ak\u0131\u015f \u00f6nceden d\u00fc\u015f\u00fcn\u00fclmezse, ilk ihtiya\u00e7 an\u0131nda elle script yaz\u0131l\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Replay g\u00fcvenli olmal\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">DLQ&#8217;daki mesajlar\u0131 tekrar oynatmak, baz\u0131lar\u0131n\u0131n ikinci kez i\u015flenmesi anlam\u0131na gelebilir. Mesaj k\u0131smen i\u015flenmi\u015f ve sonra hata vermi\u015f olabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu y\u00fczden consumer&#8217;\u0131n idempotent olmas\u0131 burada da \u00f6nemli. Ayn\u0131 event ID ile gelen ikinci mesaj, yan etki olu\u015fturmadan atlanabilmeli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mesajla\u015fma sistemleri genellikle mutlu yol \u00fczerinden tasarlan\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama bir sistemin olgunlu\u011fu, i\u015flenemeyen mesajlara ne oldu\u011funa bak\u0131larak daha iyi anla\u015f\u0131l\u0131r.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Bir mesaj i\u015flenemedi ve consumer sonsuz d\u00f6ng\u00fcye girdi. Poison message, retry topic&#8217;leri ve DLQ&#8217;daki mesajlar\u0131n ger\u00e7ekten yeniden i\u015flenebilmesi i\u00e7in gerekenler.<\/p>\n","protected":false},"author":1,"featured_media":82,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-83","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dagitik-sistemler"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/83","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=83"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/83\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/82"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=83"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=83"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=83"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}