{"id":59,"date":"2026-10-18T19:31:00","date_gmt":"2026-10-18T19:31:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/18\/redis-distributed-lock-fencing-token\/"},"modified":"2026-10-18T19:31:00","modified_gmt":"2026-10-18T19:31:00","slug":"redis-distributed-lock-fencing-token","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/18\/redis-distributed-lock-fencing-token\/","title":{"rendered":"Redis ile Distributed Lock: SETNX Neden Tek Ba\u015f\u0131na Yetmez?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Birden fazla instance ayn\u0131 i\u015fi yapmas\u0131n diye lock kullanmak istiyoruz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Redis&#8217;te en bilinen y\u00f6ntem \u015fudur:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SET lock:invoice:2026-10 worker-a NX PX 30000<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>NX<\/code> anahtar yoksa yazar. <code>PX<\/code> 30 saniye sonra otomatik silinmesini sa\u011flar. Process \u00e7\u00f6kerse lock sonsuza kadar kalmaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Lock al\u0131namad\u0131ysa ba\u015fka bir worker i\u015fi yap\u0131yordur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130\u015fimiz bitince lock&#8217;u sileriz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Basit ve \u00e7o\u011fu zaman \u00e7al\u0131\u015f\u0131yor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Yanl\u0131\u015f lock&#8217;u silmek<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130lk tuzak silme an\u0131nda.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Worker A lock&#8217;u ald\u0131. \u0130\u015fi beklenenden uzun s\u00fcrd\u00fc. 30 saniye doldu ve lock kendili\u011finden silindi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Worker B lock&#8217;u ald\u0131 ve \u00e7al\u0131\u015fmaya ba\u015flad\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Worker A i\u015fini bitirdi ve <code>DEL<\/code> komutunu \u00e7al\u0131\u015ft\u0131rd\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A&#8217;n\u0131n sildi\u011fi lock art\u0131k B&#8217;ye aitti. \u015eimdi Worker C de lock alabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu y\u00fczden silmeden \u00f6nce lock&#8217;un h\u00e2l\u00e2 size ait oldu\u011funu kontrol etmek gerekir. Kontrol ve silme atomik olmal\u0131d\u0131r, bu da genellikle bir Lua script demektir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>if redis.call(\"GET\", KEYS[1]) == ARGV[1] then\n  return redis.call(\"DEL\", KEYS[1])\nend\nreturn 0<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">As\u0131l problem: duraklayan process<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Daha zor senaryo \u015fu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Worker A lock&#8217;u ald\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tam o anda uzun bir garbage collection pause&#8217;una girdi. Veya VM&#8217;i ba\u015fka bir host&#8217;a ta\u015f\u0131nd\u0131. Veya network paketleri ge\u00e7 ula\u015ft\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">35 saniye sonra uyand\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A&#8217;n\u0131n bak\u0131\u015f a\u00e7\u0131s\u0131ndan hi\u00e7bir zaman ge\u00e7memi\u015f gibi. Lock&#8217;u ald\u0131\u011f\u0131n\u0131 d\u00fc\u015f\u00fcn\u00fcyor ve yazmaya devam ediyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama TTL \u00e7oktan dolmu\u015f, Worker B lock&#8217;u alm\u0131\u015f ve ayn\u0131 kayna\u011fa yaz\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130ki process ayn\u0131 anda kritik b\u00f6lgede.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Burada Redis&#8217;in yapabilece\u011fi hi\u00e7bir \u015fey yok. Process duraklamas\u0131, lock servisinin kontrol\u00fc d\u0131\u015f\u0131nda. &#8220;Lock&#8217;u ald\u0131ktan sonra s\u00fcreyi kontrol edeyim&#8221; demek de \u00e7\u00f6z\u00fcm de\u011fil, \u00e7\u00fcnk\u00fc kontrolden hemen sonra da duraklama ya\u015fanabilir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fencing token<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Martin Kleppmann&#8217;\u0131n Redlock \u00fczerine yazd\u0131\u011f\u0131 bilinen yaz\u0131da \u00f6nerdi\u011fi \u00e7\u00f6z\u00fcm fencing token.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Her lock al\u0131nd\u0131\u011f\u0131nda artan bir say\u0131 verilir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>A \u2192 lock, token 33\nB \u2192 lock, token 34<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Kayna\u011fa yap\u0131lan her yazma i\u015flemi bu token ile birlikte g\u00f6nderilir. Kaynak, g\u00f6rd\u00fc\u011f\u00fc en b\u00fcy\u00fck token&#8217;\u0131 hat\u0131rlar ve daha k\u00fc\u00e7\u00fck token ile gelen yazmay\u0131 reddeder.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>UPDATE invoices\nSET ..., fence = 34\nWHERE period = '2026-10'\n  AND fence &lt; 34;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A uyand\u0131\u011f\u0131nda token 33 ile yazmaya \u00e7al\u0131\u015f\u0131r. Kaynak 34&#8217;\u00fc zaten g\u00f6rm\u00fc\u015ft\u00fcr. Yazma reddedilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6nemli nokta \u015fu: g\u00fcvenli\u011fi lock servisi de\u011fil, kayna\u011f\u0131n kendisi sa\u011flar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Redis&#8217;in <code>INCR<\/code> komutu bu token&#8217;\u0131 \u00fcretmek i\u00e7in kullan\u0131labilir. Ama yaz\u0131lan sistemin token kontrol\u00fc yapabilmesi gerekir. Bir veritaban\u0131 i\u00e7in kolayd\u0131r. D\u0131\u015far\u0131daki bir \u00f6deme API&#8217;si i\u00e7in genellikle m\u00fcmk\u00fcn de\u011fildir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hangi lock, ne i\u00e7in?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Kleppmann&#8217;\u0131n yapt\u0131\u011f\u0131 ayr\u0131m bence pratikte \u00e7ok faydal\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Verimlilik i\u00e7in lock:<\/strong> Ayn\u0131 i\u015fin iki kez yap\u0131lmas\u0131n\u0131 engellemek istiyorsunuz ama iki kez yap\u0131l\u0131rsa felaket olmaz. Bir rapor iki kez \u00fcretilir, bir cache iki kez \u0131s\u0131t\u0131l\u0131r. Burada tek Redis instance&#8217;\u0131 ve <code>SET NX PX<\/code> gayet yeterli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Do\u011fruluk i\u00e7in lock:<\/strong> \u0130ki kez yap\u0131lmas\u0131 veri bozulmas\u0131na veya para kayb\u0131na yol a\u00e7\u0131yor. Burada sadece lock&#8217;a g\u00fcvenmek yeterli de\u011fil. Fencing token, veritaban\u0131 seviyesinde unique constraint veya idempotency gerekir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130kinci kategoride \u00e7o\u011fu zaman Redis lock&#8217;una hi\u00e7 ihtiya\u00e7 bile olmaz. Veritaban\u0131n\u0131n kendi lock mekanizmas\u0131, \u00f6rne\u011fin PostgreSQL advisory lock veya <code>SELECT ... FOR UPDATE<\/code>, ayn\u0131 transaction i\u00e7inde oldu\u011fu i\u00e7in daha g\u00fc\u00e7l\u00fc garantiler verir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Lock s\u00fcresini uzatmak<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Uzun s\u00fcren i\u015fler i\u00e7in baz\u0131 k\u00fct\u00fcphaneler arka planda lock&#8217;un TTL&#8217;ini d\u00fczenli olarak uzat\u0131r. Redisson&#8217;\u0131n watchdog mekanizmas\u0131 buna bir \u00f6rnek.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu, i\u015fin TTL&#8217;den uzun s\u00fcrmesi problemini azalt\u0131r. Ama process duraklamas\u0131 problemini \u00e7\u00f6zmez. Duraklayan process lock&#8217;unu da uzatamaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Distributed lock kelimesi g\u00fc\u00e7l\u00fc bir garanti varm\u0131\u015f gibi bir his veriyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ger\u00e7ekte verdi\u011fi \u015fey &#8220;\u00e7o\u011fu zaman tek bir process \u00e7al\u0131\u015f\u0131r&#8221; garantisi. Bu ikisi aras\u0131ndaki fark, sistemin kritik verisini korurken \u00f6nemli hale geliyor.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Lock ald\u0131n\u0131z, GC pause ya\u015fad\u0131n\u0131z, TTL doldu ve ba\u015fka bir process ayn\u0131 kayna\u011fa yazmaya ba\u015flad\u0131. Distributed lock&#8217;lar\u0131n s\u0131n\u0131rlar\u0131 ve fencing token ihtiyac\u0131.<\/p>\n","protected":false},"author":1,"featured_media":58,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-59","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\/59","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=59"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/59\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/58"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=59"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=59"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=59"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}