<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>分布式锁 on Answer</title>
    <link>https://answer.freetools.me/tags/%E5%88%86%E5%B8%83%E5%BC%8F%E9%94%81/</link>
    <description>Recent content in 分布式锁 on Answer</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>zh-cn</language>
    <lastBuildDate>Mon, 09 Mar 2026 03:04:33 +0800</lastBuildDate>
    <atom:link href="https://answer.freetools.me/tags/%E5%88%86%E5%B8%83%E5%BC%8F%E9%94%81/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>缓存穿透击穿雪崩为何总在关键时刻拖垮系统从布隆过滤器到分布式锁的完整防御指南</title>
      <link>https://answer.freetools.me/%E7%BC%93%E5%AD%98%E7%A9%BF%E9%80%8F%E5%87%BB%E7%A9%BF%E9%9B%AA%E5%B4%A9%E4%B8%BA%E4%BD%95%E6%80%BB%E5%9C%A8%E5%85%B3%E9%94%AE%E6%97%B6%E5%88%BB%E6%8B%96%E5%9E%AE%E7%B3%BB%E7%BB%9F%E4%BB%8E%E5%B8%83%E9%9A%86%E8%BF%87%E6%BB%A4%E5%99%A8%E5%88%B0%E5%88%86%E5%B8%83%E5%BC%8F%E9%94%81%E7%9A%84%E5%AE%8C%E6%95%B4%E9%98%B2%E5%BE%A1%E6%8C%87%E5%8D%97/</link>
      <pubDate>Mon, 09 Mar 2026 03:04:33 +0800</pubDate>
      <guid>https://answer.freetools.me/%E7%BC%93%E5%AD%98%E7%A9%BF%E9%80%8F%E5%87%BB%E7%A9%BF%E9%9B%AA%E5%B4%A9%E4%B8%BA%E4%BD%95%E6%80%BB%E5%9C%A8%E5%85%B3%E9%94%AE%E6%97%B6%E5%88%BB%E6%8B%96%E5%9E%AE%E7%B3%BB%E7%BB%9F%E4%BB%8E%E5%B8%83%E9%9A%86%E8%BF%87%E6%BB%A4%E5%99%A8%E5%88%B0%E5%88%86%E5%B8%83%E5%BC%8F%E9%94%81%E7%9A%84%E5%AE%8C%E6%95%B4%E9%98%B2%E5%BE%A1%E6%8C%87%E5%8D%97/</guid>
      <description>从Facebook 2010年2.5小时宕机事故出发，深入解析缓存穿透、缓存击穿、缓存雪崩三大问题的根本原因与技术差异。涵盖布隆过滤器的数学原理与最优参数计算、Singleflight单飞模式的并发控制机制、Redis分布式锁的正确实现方式，以及Netflix缓存预热架构的生产实践。</description>
    </item>
    <item>
      <title>分布式锁为何成了生产事故的隐形杀手——从Martin Kleppmann与antirez的论战说起</title>
      <link>https://answer.freetools.me/%E5%88%86%E5%B8%83%E5%BC%8F%E9%94%81%E4%B8%BA%E4%BD%95%E6%88%90%E4%BA%86%E7%94%9F%E4%BA%A7%E4%BA%8B%E6%95%85%E7%9A%84%E9%9A%90%E5%BD%A2%E6%9D%80%E6%89%8B%E4%BB%8Emartin-kleppmann%E4%B8%8Eantirez%E7%9A%84%E8%AE%BA%E6%88%98%E8%AF%B4%E8%B5%B7/</link>
      <pubDate>Fri, 06 Mar 2026 16:45:00 +0800</pubDate>
      <guid>https://answer.freetools.me/%E5%88%86%E5%B8%83%E5%BC%8F%E9%94%81%E4%B8%BA%E4%BD%95%E6%88%90%E4%BA%86%E7%94%9F%E4%BA%A7%E4%BA%8B%E6%95%85%E7%9A%84%E9%9A%90%E5%BD%A2%E6%9D%80%E6%89%8B%E4%BB%8Emartin-kleppmann%E4%B8%8Eantirez%E7%9A%84%E8%AE%BA%E6%88%98%E8%AF%B4%E8%B5%B7/</guid>
      <description>从2016年Martin Kleppmann与antirez关于Redlock算法的论战出发，深度剖析分布式锁的设计困境。基于Redis官方文档、ZooKeeper Recipes、Jepsen测试报告、Google Chubby论文等权威信源，揭示分布式锁的本质：它不是互斥锁，而是租约。详细分析Redlock算法的时钟同步问题、GC暂停导致的安全漏洞，以及ZooKeeper/etcd如何通过临时顺序节点和Revision实现更安全的锁机制。重点解读Fencing Token的设计原理，以及为什么Jepsen发现etcd锁也会出现互斥违反。最后给出工程实践建议：效率优先选Redis单实例，正确性优先选共识系统。</description>
    </item>
  </channel>
</rss>
