Hello everyone.
I am confused on how the static discovery works related to network
partitioning. In particular, here is my use case.
On one node (call it N1), I run a domain participant with one data
writer which writes some data to a topic 'T' in partition 'part'.
The reliability QoS for the data writer is best-effort with KEEP_LAST
history, and history.depth = 1.
The ospl configuration for that node (N1) for what concerns network
partitions is as follows:
...
<Partitioning>
<GlobalPartition Address="224.0.0.42"/>
<NetworkPartitions>
<NetworkPartition Address="N2 N3 N4 N5" Connected="true"
Name="part"/>
</NetworkPartitions>
<PartitionMappings>
<PartitionMapping DCPSPartitionTopic="part.*"
NetworkPartition="inputoutput"/>
</PartitionMappings>
</Partitioning>
...
N2, N3, N4, and N5 are the unicast ip addresses of other four potential
domain participants.
Now, if no data reader matching the data writer on N1 is started in the
domain I see no traffic going out from N1 as one would expect.
However, if I start exactly one data reader on -- for example -- N2 I
see that N1 generates UDP traffic towards ALL the hosts in the partition
(i.e., N2, N3, N4, N5) even though no opensplice instance is running on
N3, N4 and N5. The destination port of these messages is 53370, the port
of the best-effort channel.
Is the behaviour normal? I would have expected that no traffic was
generated towards the nodes not running opensplice...
Thanks,
andrea
_______________________________________________
OpenSplice DDS Developer Mailing List
Developer@opensplice.org
Subscribe / Unsubscribe http://dev.opensplice.org/mailman/listinfo/developer
