<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" version="2.0"><channel><title>Test</title><link>http://81.71.123.130:8091/</link><atom:link href="http://81.71.123.130:8091/rss.xml" rel="self" type="application/rss+xml"/><description>Test</description><generator>Halo v2.25.0</generator><language>zh-cn</language><lastBuildDate>Fri, 12 Jun 2026 09:23:51 GMT</lastBuildDate><item><title><![CDATA[TrinoPrestoSQL和数仓几个概念梳理]]></title><link>http://81.71.123.130:8091/archives/trinoprestosqlhe-shu-cang-ji-ge-gai-nian-shu-li</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=TrinoPrestoSQL%E5%92%8C%E6%95%B0%E4%BB%93%E5%87%A0%E4%B8%AA%E6%A6%82%E5%BF%B5%E6%A2%B3%E7%90%86&amp;url=/archives/trinoprestosqlhe-shu-cang-ji-ge-gai-nian-shu-li" width="1" height="1" alt="" style="opacity:0;">Trino、PrestoSQL 和数仓几个概念梳理 前言 最近在补一些大数据基础概念时，发现自己最容易混的不是某一个单独术语，而是这些词总是一起出现：Trino、PrestoSQL、DW、ODS/DWD/DWS/ADS、ETL/ELT、OLTP/OLAP。 单看每个词，好像都能说两句；真要把它们放到]]></description><guid isPermaLink="false">/archives/trinoprestosqlhe-shu-cang-ji-ge-gai-nian-shu-li</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[synchronized相关思考]]></title><link>http://81.71.123.130:8091/archives/synchronizedxiang-guan-si-kao</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=synchronized%E7%9B%B8%E5%85%B3%E6%80%9D%E8%80%83&amp;url=/archives/synchronizedxiang-guan-si-kao" width="1" height="1" alt="" style="opacity:0;">synchronized 相关思考 前言 最近又重新过了一遍 synchronized，发现自己之前对它的理解其实偏“结论导向”。 比如知道它能保证原子性、可见性、有序性，也知道它背后有锁升级、对象头、Monitor 这些东西，但一旦继续追问“为什么会升级”“对象头里到底放了什么”“自旋和阻塞的边界]]></description><guid isPermaLink="false">/archives/synchronizedxiang-guan-si-kao</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[大数据回溯相关的一些思考]]></title><link>http://81.71.123.130:8091/archives/da-shu-ju-hui-su-xiang-guan-de-yi-xie-si-kao</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E5%A4%A7%E6%95%B0%E6%8D%AE%E5%9B%9E%E6%BA%AF%E7%9B%B8%E5%85%B3%E7%9A%84%E4%B8%80%E4%BA%9B%E6%80%9D%E8%80%83&amp;url=/archives/da-shu-ju-hui-su-xiang-guan-de-yi-xie-si-kao" width="1" height="1" alt="" style="opacity:0;">回溯相关的一些思考 前言 这次想单独记一下自己对“回溯”这件事的一些理解。 一开始我对回溯的理解其实也比较直白，无非就是把某个对象过去某一天的数据查出来，再往后分析原因。 但后面越想越觉得不对。 如果回溯真的只是查历史数据，那很多问题其实解释不通。比如为什么时间跨度一大，就不能继续逐天查；为什么有些]]></description><guid isPermaLink="false">/archives/da-shu-ju-hui-su-xiang-guan-de-yi-xie-si-kao</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[大数据回溯场景下的缓存与SQL体积调优经验总结]]></title><link>http://81.71.123.130:8091/archives/da-shu-ju-hui-su-chang-jing-xia-de-huan-cun-yu-sqlti-ji-diao-you-jing-yan-zong-jie</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E5%A4%A7%E6%95%B0%E6%8D%AE%E5%9B%9E%E6%BA%AF%E5%9C%BA%E6%99%AF%E4%B8%8B%E7%9A%84%E7%BC%93%E5%AD%98%E4%B8%8ESQL%E4%BD%93%E7%A7%AF%E8%B0%83%E4%BC%98%E7%BB%8F%E9%AA%8C%E6%80%BB%E7%BB%93&amp;url=/archives/da-shu-ju-hui-su-chang-jing-xia-de-huan-cun-yu-sqlti-ji-diao-you-jing-yan-zong-jie" width="1" height="1" alt="" style="opacity:0;">前言 最近在做大数据回溯相关工作，这里把其中关于 CID 缓存以及 SQL 体积调优的一些经验做一次整理。 这类场景里，随着数据量和回溯范围变大，CID 存储方式、批量读取方式、SQL 体积控制以及查询执行稳定性，都会逐渐成为影响整体性能的关键因素。实际处理过程中，也会涉及缓存成本、查询开销、批次控]]></description><guid isPermaLink="false">/archives/da-shu-ju-hui-su-chang-jing-xia-de-huan-cun-yu-sqlti-ji-diao-you-jing-yan-zong-jie</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[ClickHouseTOOMANYPARTS异常分析与优化实践]]></title><link>http://81.71.123.130:8091/archives/clickhousetoomanypartsyi-chang-fen-xi-yu-you-hua-shi-jian</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=ClickHouseTOOMANYPARTS%E5%BC%82%E5%B8%B8%E5%88%86%E6%9E%90%E4%B8%8E%E4%BC%98%E5%8C%96%E5%AE%9E%E8%B7%B5&amp;url=/archives/clickhousetoomanypartsyi-chang-fen-xi-yu-you-hua-shi-jian" width="1" height="1" alt="" style="opacity:0;">技术排查 初步分析 流量突增？ 监控显示调用量平稳，排除突发流量导致分片激增的可能。 集群负载异常？ DBA核查CPU/内存/磁盘IO指标均正常，排除硬件资源瓶颈。 插入流程深挖 [客户端] │ 单条INSERT操作 ▼ [分布式表] → 哈希计算分片键 → 路由至Shard-2]]></description><guid isPermaLink="false">/archives/clickhousetoomanypartsyi-chang-fen-xi-yu-you-hua-shi-jian</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记一次因网络问题导致Http连接池耗尽]]></title><link>http://81.71.123.130:8091/archives/ji-yi-ci-yin-wang-luo-wen-ti-dao-zhi-httplian-jie-chi-hao-jin</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E4%B8%80%E6%AC%A1%E5%9B%A0%E7%BD%91%E7%BB%9C%E9%97%AE%E9%A2%98%E5%AF%BC%E8%87%B4Http%E8%BF%9E%E6%8E%A5%E6%B1%A0%E8%80%97%E5%B0%BD&amp;url=/archives/ji-yi-ci-yin-wang-luo-wen-ti-dao-zhi-httplian-jie-chi-hao-jin" width="1" height="1" alt="" style="opacity:0;">技术排查 初步分析 流量突增？ 监控显示调用量平稳，排除突发流量激增的可能。 集群负载异常？ DBA核查CPU/内存/磁盘IO指标均正常，排除硬件资源瓶颈。 插入流程深挖 [客户端] │ 单条INSERT操作 ▼ [分布式表] → 哈希计算分片键 → 路由至Shard-2 ▼ [本]]></description><guid isPermaLink="false">/archives/ji-yi-ci-yin-wang-luo-wen-ti-dao-zhi-httplian-jie-chi-hao-jin</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[ArrayList扩容相关思考]]></title><link>http://81.71.123.130:8091/archives/arraylistkuo-rong-xiang-guan-si-kao</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=ArrayList%E6%89%A9%E5%AE%B9%E7%9B%B8%E5%85%B3%E6%80%9D%E8%80%83&amp;url=/archives/arraylistkuo-rong-xiang-guan-si-kao" width="1" height="1" alt="" style="opacity:0;">2. 核心作用：Fail-Fast 机制 modCount 是 Fail-Fast（快速失败） 机制的核心，用于在以下场景快速检测并发修改： 场景 1：单线程迭代时修改集合 List&lt;String&gt; list = new ArrayList&lt;&gt;(Arrays.asList("A", "B", "C"]]></description><guid isPermaLink="false">/archives/arraylistkuo-rong-xiang-guan-si-kao</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记一次Clickhouse数据写入成功但是却无数据问题]]></title><link>http://81.71.123.130:8091/archives/ji-yi-ci-clickhouseshu-ju-xie-ru-cheng-gong-dan-shi-que-wu-shu-ju-wen-ti</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E4%B8%80%E6%AC%A1Clickhouse%E6%95%B0%E6%8D%AE%E5%86%99%E5%85%A5%E6%88%90%E5%8A%9F%E4%BD%86%E6%98%AF%E5%8D%B4%E6%97%A0%E6%95%B0%E6%8D%AE%E9%97%AE%E9%A2%98&amp;url=/archives/ji-yi-ci-clickhouseshu-ju-xie-ru-cheng-gong-dan-shi-que-wu-shu-ju-wen-ti" width="1" height="1" alt="" style="opacity:0;">背景 在一次数据排查时，无意间发现数据对不齐。结合代码及日志分析发现都没问题，且有插入操作，但是 Clickhouse 却查不到改条记录。匪夷所思… 排查过程 最后断定大概率是 Clickhouse 的问题，难道 Clickhouse 存在数据丢失的情况？进一步分析丢失数据部分时间分布发现并无任何规]]></description><guid isPermaLink="false">/archives/ji-yi-ci-clickhouseshu-ju-xie-ru-cheng-gong-dan-shi-que-wu-shu-ju-wen-ti</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记一次Zookeeper高负载引发的一系列问题]]></title><link>http://81.71.123.130:8091/archives/ji-yi-ci-zookeepergao-fu-zai-yin-fa-de-yi-xi-lie-wen-ti</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E4%B8%80%E6%AC%A1Zookeeper%E9%AB%98%E8%B4%9F%E8%BD%BD%E5%BC%95%E5%8F%91%E7%9A%84%E4%B8%80%E7%B3%BB%E5%88%97%E9%97%AE%E9%A2%98&amp;url=/archives/ji-yi-ci-zookeepergao-fu-zai-yin-fa-de-yi-xi-lie-wen-ti" width="1" height="1" alt="" style="opacity:0;">背景 在一次 ZK 突然莫名的出现高负载，导致Provider、Consumer 与 ZK 连接异常，系统一直提示连接异常，但是此时对各个系统Dubbo 服务依旧正常调度，下文继续分析为什么不会影响到服务间调用。但是使得 ZK 高负载的根因是什么呢？ 排查过程 日志记录异常如下： org.apach]]></description><guid isPermaLink="false">/archives/ji-yi-ci-zookeepergao-fu-zai-yin-fa-de-yi-xi-lie-wen-ti</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记一次MQ消费失败引发的一系列问题]]></title><link>http://81.71.123.130:8091/archives/ji-yi-ci-mqxiao-fei-shi-bai-yin-fa-de-yi-xi-lie-wen-ti</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E4%B8%80%E6%AC%A1MQ%E6%B6%88%E8%B4%B9%E5%A4%B1%E8%B4%A5%E5%BC%95%E5%8F%91%E7%9A%84%E4%B8%80%E7%B3%BB%E5%88%97%E9%97%AE%E9%A2%98&amp;url=/archives/ji-yi-ci-mqxiao-fei-shi-bai-yin-fa-de-yi-xi-lie-wen-ti" width="1" height="1" alt="" style="opacity:0;">背景 使用了腾讯云封装的 Pulsar 作为云消息队列，消费中有大致就是一个异步 MQ 日志落库的逻辑。我们日志库使用的 ClickHouse，那天 CK 出现了一段时间的连接异常导致 MQ 消费一直消费异常，进而 Consumer 没再接收到任何消息，但是我本地主动发起了一笔请求，消息成功消费日志]]></description><guid isPermaLink="false">/archives/ji-yi-ci-mqxiao-fei-shi-bai-yin-fa-de-yi-xi-lie-wen-ti</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记一次分布式ID主键冲突问题]]></title><link>http://81.71.123.130:8091/archives/ji-yi-ci-fen-bu-shi-idzhu-jian-chong-tu-wen-ti</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E4%B8%80%E6%AC%A1%E5%88%86%E5%B8%83%E5%BC%8FID%E4%B8%BB%E9%94%AE%E5%86%B2%E7%AA%81%E9%97%AE%E9%A2%98&amp;url=/archives/ji-yi-ci-fen-bu-shi-idzhu-jian-chong-tu-wen-ti" width="1" height="1" alt="" style="opacity:0;">背景 在一次Uat 环境测试中，出现主键冲突异常，明明昨天测试都是正常的。多试了几笔发现生成的主键 ID 确实已经重复了，且该 ID 是在今天上午十点生成的，很奇怪。 排查过程 该分布式 ID 生成器是借助 Zookeeper 来实现的，发现Uat 环境 ZK 配置的 Host 与 Prod 环境不]]></description><guid isPermaLink="false">/archives/ji-yi-ci-fen-bu-shi-idzhu-jian-chong-tu-wen-ti</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[一文讲清加解签名加解密数字签名数字证书]]></title><link>http://81.71.123.130:8091/archives/yi-wen-jiang-qing-jia-jie-qian-ming-jia-jie-mi-shu-zi-qian-ming-shu-zi-zheng-shu</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E4%B8%80%E6%96%87%E8%AE%B2%E6%B8%85%E5%8A%A0%E8%A7%A3%E7%AD%BE%E5%90%8D%E5%8A%A0%E8%A7%A3%E5%AF%86%E6%95%B0%E5%AD%97%E7%AD%BE%E5%90%8D%E6%95%B0%E5%AD%97%E8%AF%81%E4%B9%A6&amp;url=/archives/yi-wen-jiang-qing-jia-jie-qian-ming-jia-jie-mi-shu-zi-qian-ming-shu-zi-zheng-shu" width="1" height="1" alt="" style="opacity:0;">前言 话说前段时间，大毛和二毛两家打的那叫一个热火朝天。大毛将二毛摁在地上反复摩擦之际，鹰酱给二毛发去一项指令：不要送！！！而此条指令被精通特工技术的大毛潜伏人员截获对报文内容进行稍加修饰：不要怂！！！二毛收到指令瞬间就打上鸡血，哐哐就是和大毛死磕到底。二毛：鹰酱都这么说了，肯定能给我不少支持，我可]]></description><guid isPermaLink="false">/archives/yi-wen-jiang-qing-jia-jie-qian-ming-jia-jie-mi-shu-zi-qian-ming-shu-zi-zheng-shu</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[巧用Apifox自动生成接口签名]]></title><link>http://81.71.123.130:8091/archives/qiao-yong-apifoxzi-dong-sheng-cheng-jie-kou-qian-ming</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E5%B7%A7%E7%94%A8Apifox%E8%87%AA%E5%8A%A8%E7%94%9F%E6%88%90%E6%8E%A5%E5%8F%A3%E7%AD%BE%E5%90%8D&amp;url=/archives/qiao-yong-apifoxzi-dong-sheng-cheng-jie-kou-qian-ming" width="1" height="1" alt="" style="opacity:0;">前言 近期在使用apifox调试接口时，由于众多测试样例，每次修改参数都需要重新手动去生成一下签名，再回填入参数中，略烦。便着手寻找可自动生成签名并回填方法。查阅官网文档，发现所提供的样例是针对form表单类型可使用动态值{{signature}}进行拼接。但是我司是使用json交互，签名字段在js]]></description><guid isPermaLink="false">/archives/qiao-yong-apifoxzi-dong-sheng-cheng-jie-kou-qian-ming</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记一次mybatis与mybatisplus及mysql与cilickhouse共存遇到的问题]]></title><link>http://81.71.123.130:8091/archives/ji-yi-ci-mybatisyu-mybatisplusji-mysqlyu-cilickhousegong-cun-yu-dao-de-wen-ti</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E4%B8%80%E6%AC%A1mybatis%E4%B8%8Emybatisplus%E5%8F%8Amysql%E4%B8%8Ecilickhouse%E5%85%B1%E5%AD%98%E9%81%87%E5%88%B0%E7%9A%84%E9%97%AE%E9%A2%98&amp;url=/archives/ji-yi-ci-mybatisyu-mybatisplusji-mysqlyu-cilickhousegong-cun-yu-dao-de-wen-ti" width="1" height="1" alt="" style="opacity:0;">背景 在维护公司一个老项目时，出于方便的考虑，准备在项目中引入Mybatis-plus作为持久层，那么这就涉及到新老代码共存的问题。随后由于该项目是一个数据产品相关项目，有一个日志模块会记录用户的调用记录，该日志数据落库在MySQL现已存储8kw+数据，已经不堪重负了，同时产品同学期望完善一下这块的]]></description><guid isPermaLink="false">/archives/ji-yi-ci-mybatisyu-mybatisplusji-mysqlyu-cilickhousegong-cun-yu-dao-de-wen-ti</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记一次Druid连接池关闭异常问题]]></title><link>http://81.71.123.130:8091/archives/ji-yi-ci-druidlian-jie-chi-guan-bi-yi-chang-wen-ti</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E4%B8%80%E6%AC%A1Druid%E8%BF%9E%E6%8E%A5%E6%B1%A0%E5%85%B3%E9%97%AD%E5%BC%82%E5%B8%B8%E9%97%AE%E9%A2%98&amp;url=/archives/ji-yi-ci-druidlian-jie-chi-guan-bi-yi-chang-wen-ti" width="1" height="1" alt="" style="opacity:0;">背景 在一个DB层本是只有MySQL项目中，后期同时引入了Clickhouse作为日志存储的数据库。在每次项目发布时都会抛出异常unregister mbean error提示注销bean异常，具体报错如下： javax.management.InstanceNotFoundException:]]></description><guid isPermaLink="false">/archives/ji-yi-ci-druidlian-jie-chi-guan-bi-yi-chang-wen-ti</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记一次生产Druid连接池Communicationslinkfailure异常]]></title><link>http://81.71.123.130:8091/archives/ji-yi-ci-sheng-chan-druidlian-jie-chi-communicationslinkfailureyi-chang</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E4%B8%80%E6%AC%A1%E7%94%9F%E4%BA%A7Druid%E8%BF%9E%E6%8E%A5%E6%B1%A0Communicationslinkfailure%E5%BC%82%E5%B8%B8&amp;url=/archives/ji-yi-ci-sheng-chan-druidlian-jie-chi-communicationslinkfailureyi-chang" width="1" height="1" alt="" style="opacity:0;">异常日志 The last packet successfully received from the server was 15,788,990 milliseconds ago. The last packet sent successfully to the server was 15,788]]></description><guid isPermaLink="false">/archives/ji-yi-ci-sheng-chan-druidlian-jie-chi-communicationslinkfailureyi-chang</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记一次上线发布引用包问题]]></title><link>http://81.71.123.130:8091/archives/ji-yi-ci-shang-xian-fa-bu-yin-yong-bao-wen-ti</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E4%B8%80%E6%AC%A1%E4%B8%8A%E7%BA%BF%E5%8F%91%E5%B8%83%E5%BC%95%E7%94%A8%E5%8C%85%E9%97%AE%E9%A2%98&amp;url=/archives/ji-yi-ci-shang-xian-fa-bu-yin-yong-bao-wen-ti" width="1" height="1" alt="" style="opacity:0;">在上线代码后，后台日志疯狂抛表不存在异常，经排查发现，新建的该表未在本次上线需求中，还在测试中的需求，第一反应是本次上线分支被合入了另外需求代码所致，然而奇怪的点却是该版本分支确实无那块代码，且检查mster分支也无那块代码。懵…，立马检查打包构建及其docker镜像问题，也都是正常，构建的也都是正]]></description><guid isPermaLink="false">/archives/ji-yi-ci-shang-xian-fa-bu-yin-yong-bao-wen-ti</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:30 GMT</pubDate></item><item><title><![CDATA[记公司出口网关建设遇到问题]]></title><link>http://81.71.123.130:8091/archives/ji-gong-si-chu-kou-wang-guan-jian-she-yu-dao-wen-ti</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=%E8%AE%B0%E5%85%AC%E5%8F%B8%E5%87%BA%E5%8F%A3%E7%BD%91%E5%85%B3%E5%BB%BA%E8%AE%BE%E9%81%87%E5%88%B0%E9%97%AE%E9%A2%98&amp;url=/archives/ji-gong-si-chu-kou-wang-guan-jian-she-yu-dao-wen-ti" width="1" height="1" alt="" style="opacity:0;">背景 由于公司出于安全考虑，准备统一收拢对外出口服务器，同时对出口请求进行监控管理，因此tplinker项目孕育而生 项目简介 该项目针对不同场景主要有两种模式 透传模式：主要用于兼容现有业务直接对外请求接口，该模式对于已经开发请求URL配置代理域名，请求先通过Nginx转发到出口服务器中，再经过t]]></description><guid isPermaLink="false">/archives/ji-gong-si-chu-kou-wang-guan-jian-she-yu-dao-wen-ti</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:29 GMT</pubDate></item><item><title><![CDATA[ThreadPoolExecutor解析]]></title><link>http://81.71.123.130:8091/archives/threadpoolexecutorjie-xi</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=ThreadPoolExecutor%E8%A7%A3%E6%9E%90&amp;url=/archives/threadpoolexecutorjie-xi" width="1" height="1" alt="" style="opacity:0;">ThreadPoolExecutor 参数解析 corePoolSize 核心线程数 即使没有任务执行，核心线程也会一直存活 线程数小于核心线程时，即使有空闲线程，线程沲也会创建新线程执行任务 设置allowCoreThreadTimeout=true时，核心线程会超时关闭 maximumPoolS]]></description><guid isPermaLink="false">/archives/threadpoolexecutorjie-xi</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:29 GMT</pubDate></item><item><title><![CDATA[TCP的三次握手四次挥手]]></title><link>http://81.71.123.130:8091/archives/tcpde-san-ci-wo-shou-si-ci-hui-shou</link><description><![CDATA[<img src="http://81.71.123.130:8091/plugins/feed/assets/telemetry.gif?title=TCP%E7%9A%84%E4%B8%89%E6%AC%A1%E6%8F%A1%E6%89%8B%E5%9B%9B%E6%AC%A1%E6%8C%A5%E6%89%8B&amp;url=/archives/tcpde-san-ci-wo-shou-si-ci-hui-shou" width="1" height="1" alt="" style="opacity:0;">]]></description><guid isPermaLink="false">/archives/tcpde-san-ci-wo-shou-si-ci-hui-shou</guid><dc:creator>Administrator</dc:creator><pubDate>Fri, 12 Jun 2026 06:37:29 GMT</pubDate></item></channel></rss>