<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fencing Tokens on Nalar</title>
    <link>https://nalar.dev/tags/fencing-tokens/</link>
    <description>Recent content in Fencing Tokens on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/fencing-tokens/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fencing Tokens Block Stale Lock Holders at the Resource</title>
      <link>https://nalar.dev/fencing-tokens-block-stale-lock-holders-at-the-resource/</link>
      <pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/fencing-tokens-block-stale-lock-holders-at-the-resource/</guid>
      <description>&lt;h1 id=&#34;fencing-tokens-block-stale-lock-holders-at-the-resource&#34;&gt;Fencing Tokens Block Stale Lock Holders at the Resource&lt;/h1&gt;&#xA;&lt;p&gt;A distributed lease can expire while its holder is still running. A process may pause for garbage collection, lose contact with the coordinator, stall under scheduler pressure, or resume after a machine suspension. The lock service can correctly grant the lease to another worker while the old worker still has unfinished work.&lt;/p&gt;&#xA;&lt;p&gt;That gap matters when both workers can reach the protected resource. A lease controls ownership in the coordinator; it does not automatically revoke a delayed database connection, storage request, or RPC that was prepared by the previous holder.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
