<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title><![CDATA[weixin_61241721的博客]]></title><description><![CDATA[]]></description><link>https://blog.youkuaiyun.com/weixin_61241721</link><language>zh-cn</language><generator>https://blog.youkuaiyun.com/</generator><copyright><![CDATA[Copyright &copy; weixin_61241721]]></copyright><item><title><![CDATA[Redis与DB数据一致性问题]]></title><link>https://blog.youkuaiyun.com/weixin_61241721/article/details/148865664</link><guid>https://blog.youkuaiyun.com/weixin_61241721/article/details/148865664</guid><author>weixin_61241721</author><pubDate>Tue, 24 Jun 2025 10:14:52 +0800</pubDate><description><![CDATA[摘要：Cache-Aside模式通过&quot;先查缓存，无则查DB更新缓存&quot;的读操作和&quot;先更新DB再删除缓存&quot;的写操作实现数据一致性。删除而非更新缓存能避免并发写脏数据、简化逻辑并应对部分失败场景。常见方案主要有四种，分析表明&quot;先改DB再删redis&quot;是最优选择，但无法完全避免最终不一致。关键是要拉长写操作的DB更新与最终缓存删除的时间窗口，以降低不一致概率。该模式核心在于平衡读写并发时序问题，最终实现数据一致性。]]></description><category></category></item><item><title><![CDATA[Redis数据丢失场景]]></title><link>https://blog.youkuaiyun.com/weixin_61241721/article/details/148818467</link><guid>https://blog.youkuaiyun.com/weixin_61241721/article/details/148818467</guid><author>weixin_61241721</author><pubDate>Sun, 22 Jun 2025 00:01:50 +0800</pubDate><description><![CDATA[redis数据丢失场景]]></description><category></category></item><item><title><![CDATA[raft 分布式共识]]></title><link>https://blog.youkuaiyun.com/weixin_61241721/article/details/148796386</link><guid>https://blog.youkuaiyun.com/weixin_61241721/article/details/148796386</guid><author>weixin_61241721</author><pubDate>Fri, 20 Jun 2025 17:18:38 +0800</pubDate><description><![CDATA[精简版]]></description><category></category></item><item><title><![CDATA[Redis中 flushdb 与 flushall 的区别]]></title><link>https://blog.youkuaiyun.com/weixin_61241721/article/details/148767938</link><guid>https://blog.youkuaiyun.com/weixin_61241721/article/details/148767938</guid><author>weixin_61241721</author><pubDate>Thu, 19 Jun 2025 15:34:00 +0800</pubDate><description><![CDATA[Redis的flushdb和flushall命令在数据持久化处理上有重要区别。flushdb仅清空当前数据库，是否触发持久化取决于是否满足默认的RDB保存条件（如save 900 1）；若未满足且强制终止进程，数据可能恢复。而flushall会清空所有数据库并立即执行持久化，通过INFO persistence的rdb_last_save_time可验证其特性，数据无法恢复。实际测试表明，flushdb后若在900秒内终止服务，原数据仍存在；flushall则会彻底清除数据。]]></description><category></category></item><item><title><![CDATA[ElementUI 使用 v-if 遇到问题：Duplicate keys detected]]></title><link>https://blog.youkuaiyun.com/weixin_61241721/article/details/148695336</link><guid>https://blog.youkuaiyun.com/weixin_61241721/article/details/148695336</guid><author>weixin_61241721</author><pubDate>Mon, 16 Jun 2025 16:51:21 +0800</pubDate><description><![CDATA[ElementUI 使用 v-if 遇到问题：Duplicate keys detected]]></description><category></category></item><item><title><![CDATA[this.getClass().getClassLoader().getResource和this.getClass().getResource的区别和联系]]></title><link>https://blog.youkuaiyun.com/weixin_61241721/article/details/127473270</link><guid>https://blog.youkuaiyun.com/weixin_61241721/article/details/127473270</guid><author>weixin_61241721</author><pubDate>Sun, 23 Oct 2022 12:31:52 +0800</pubDate><description><![CDATA[this.getClass().getClassLoader().getResource和this.getClass().getResource的区别和联系]]></description><category></category></item></channel></rss>