Ivan Kozlovic

I believe that there is no issue. I have created a "server" test (posted below) that tries to cover all issues describe above and the test passes with v2.9.0 (main...

@aricart @ripienaar I understand that this is a very old report, but if you could check my explanation above (and the test I provided) to see if that explains the...

@ianzhang1988 Correct, currently you cannot set the number of replicas, instead, the server determines the number based on the size of the cluster (number of routes) but cap it at...

> It's best if we could use all server in a cluster, so that we could meet new demand. Is it possible for mqtt use multiple stream across all server,...

@ianzhang1988 Unfortunately, this is not possible: consumers cannot span multiple streams.

> Is MQTT support a priority or a nice to have feature. That's a good question. We see more and more interest actually for MQTT at high scale, and we...

@ianzhang1988 As a step to help scalability, we have merged PR #3130 that would allow the configuration of the consumers as a lower replicas than the parent stream. So you...

> Is stream_replicas: 5 means that consumers can read from stream replicas evenly? I thought leader do all read and write. There is a leader for the stream, and there...

> Also, nats consumer ls show repeat consumer name. Any idea why? No, could you post an excerpt of the output? Normally these names are randomly generated and correspond to...

@ianzhang1988 We still have work to do on JetStream for sure (MQTT depends on it). Could you share your configuration file? I assumed that you were using `consumer_replicas: 1`, but...