| [hono-dev] Changes in settlement of telemetry and dispatch router config? |
|
Hi *, as investigated in
https://github.com/eclipse/hono/issues/337, we have some problems with our actual use of settlement as well as the dispatch router configuration in regards of full flow control. First of all a configuration of multicast together with link-routing is not an intended use-case of the dispatch router [1]. So we should not configure it this way
in our example – flow control is not useable, because the router will always settle the messages. I propose to change this to balanced. I think this is also a more realistic use case, that the consumer has multiple instances, that should be balanced. The second finding is, that it might be a better approach to use unsettled also for telemetry, to be able to use flow control/back pressure. So we will be able to
handle overload as far at the devices side as possible – at least in the adapter (dependent on the device protocol). In this case we would change telemetry to also use at least once (like events - but we don’t need to wait). From the numbers this seams not
a big difference in throughput. WDYT? 1: https://issues.jboss.org/browse/ENTMQIC-1932?focusedCommentId=13395229&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13395229 Marc Pellmann |