Timeout exception - AeronCluster client with non-default ingress and egress stream-id

[tamama]

Timeout exception - AeronCluster client with non-default ingress and egress stream-id

[JPWatson]

Hey Tama,

In Aeron Cluster, all ingress traffic is sequenced onto a single replicated log. The reason your example is failing is the cluster client and nodes assume all ingress traffic is using the same ingress stream ID. To represent distinct topics, you'd either need the discriminator at a well-known offset within the message or multiple instances of Cluster.
Aeron Cluster can sequence millions of messages per second, so often, one instance is enough. It may be possible for you model topics as a field at a well known offset and get visibility from AeronStat by creating custom counters and populating them from within the ClusteredService.

Thanks,
James