Scarb

你这个现象就是正常的啊，过滤不是说这个消息还会在未消费消息那里，而是拉取了之后不处理。

@annoygaga 那你应该去问你朋友啊

@annoygaga kafka 我没实现过。你说的变化只是 3 种消息格式吧，v0 v1 v2 ，这个应该还好。别的就没什么变化了

我实现过 AMQP 协议。AMQP 协议更复杂，功能和细节非常多，有些不常用但是可能对有的用户来说又是刚需（比如优先级队列之类）。kafka 不那么复杂

之前看到 netty 的三段式 commit message ，觉得挺好，可以参考一下。举个例子
```
Aggressively remove PoolThreadCache references from its finalizer object

Motivation:
If a cache's FastThreadLocalThread owner win the race to remove the cache, due to debugging
capabilities, it's finalizer will still retain a strong reference to it, causing few classes to leak (and eventually, their ClassLoader).
Despite we cannot avoid finalizers to wait the finalization pass, we can reduce the memory footprint of "leaked" instances before the finalization happen.

Modification:
non-debug early cache removal can remove the cache strong reference within FreeOnFinalize, making it an emtpy shell, eligible for GC.

Result:
Smaller memory footprint while waiting finalization to happen
```

poi person of interest

服务端负载很高吗？把抓包文件或者截图放上来看看

"微信小游戏上线，软著和版号都不是必须的，带虚拟支付才需要。"
也就是说没法虚拟支付，没法赚钱吗