zmstone

> 2024-05-24T02:19:43.218437+00:00 [warning] msg: start_resource_failed, id: , reason: {start_pool_failed,,{connect_failed,{saslStart,#{ => 18, => , => }}}} This log hints bad username password for mongodb connector.

> Besides, I assume that the original setting auto can help to decide whether to use the latest mongo api. `auto` is explained here: https://github.com/emqx/mongodb-erlang/blob/c70e158fb8b67a0034ad3c17ed544fa29d11d358/src/main/mc_worker_pid_info.erl#L131-L151 If there is any doubt...

`function_clause. Stack: [{public_key,pkix_decode_cert,[[],otp]` this exception signature might indicate that the certificate is signed with unsupported keys. Maybe try RSA ECDSA or EdDSA keys?

Hi @qRainBirdp Could you provide logs from all three nodes ?

maybe run below commands (EMQX v5 or newer): - `emqx ctl retainer info`: this will provide the number of retained messages, when there are a large number of retained messages,...

sad to see people leave. the "smp:4:1" is alarming, it means the server started with 4 schedulers but only has 1 online. it's because the poor vm only got one...

In MQTT, there is no builtin semantics for consumer confirmation. The specification however provided a mechanism and guidelines how to implement it with PUB/SUB primitives, check out request/response: https://www.emqx.com/en/blog/mqtt5-request-response

As there is no plan to release kafka integration in Opensource edition, I’m closing this feature request.

Hi @Tyco1234Jun Please check syslog to see if the service is getting OOM killed by the OS.

@Tyco1234Jun In your logs, there are congestion and message_queue_too_long errors it indicates that the subscribers are not consuming the messages fast enough, caused a lot of message to pile up...