webhook监听上下线事件时，事件时序有误，原因不明（connected and disconnected events may out of order) about emqx HOT 3 CLOSED

非必现，时有发生

from emqx.

Hello @hotraygroup
这一个已知，但是不计划解决的问题。
重链后处理新连接的进程不是同一个，也可能不是同一个节点，事件被触发后也有可能是异步发送事件到 webhook（或者其他数据集成），所以也无法保证投递顺序。
要保证事件严格有序会需要引入全局锁，或者把事件序列化，对性能造成的损失可能远大于解决两个异步事件顺序带来的收益。

from emqx.

This is a known, but won't fix issue.

The new connection after reconned is handled by a different process,
when cluster, it might be handled by a different node.
The events might be delivered async-ly towards webhook (or other data sinks).

To ensure order, we may need to either introduce a global lock, or serialise the events by one single actor
--- we believe the performance loss does not worth it

from emqx.