14.5.1. What’s New in 7.0.0
14.5.1.1. Improved steady state bandwidth utilization and discovery time in systems with many DomainParticipants communicating over lossy networks
In lossy networks, DomainParticipant discovery could take longer if DomainParticipant announcements forwarded
from Cloud Discovery Service were dropped. In previous releases, the <refresh_period> configuration
tag could be used to resend DomainParticipant announcements periodically.
The tradeoff of using that parameter was that it could lead to unnecessary network
traffic on systems that had completed DomainParticipant discovery (because the
<refresh_period> mechanism continued resending indefinitely).
In this release, the <refresh_period> is replaced with a more efficient
way to resend DomainParticipant announcements. This new mechanism resends the DomainParticipant announcements
from Cloud Discovery Service a finite number of times, spaced randomly in an interval between
a minimum and maximum value:
<forwarder>
<event>
<new_or_update_participant_announcements>
</new_or_update_participant_announcements>
<min_new_or_update_participant_announcements_period>
</min_new_or_update_participant_announcements_period>
<max_new_or_update_participant_announcements_period>
</max_new_or_update_participant_announcements_period>
</event>
</forwarder>
For additional information about these new parameters, see Forwarder.
14.5.1.2. Domain Participant Partitions support
Cloud Discovery Service supports systems that utilize Domain Participant Partitions. Partitioning at the DomainParticipant level can be particularly useful in large, WAN, distributed systems (with thousands of participants) in which not all participants need to know about each other at any given time.
Domain Participant Partitions functionality reduces network, CPU, and memory utilization, because DomainParticipants without matching partitions will not exchange information about themselves and their DataWriters and DataReaders.
Domain Participant Partitions support in Cloud Discovery Service ensures that Cloud Discovery Service doesn’t forward a DomainParticipant announcement to DomainParticipants whose partition values don’t match.
For details, see Domain Participant Partitions.
14.5.1.3. Removals
14.5.1.3.1. domain_id_info_seq field in DatabasePeriodic type used in monitoring removed
The @optional sequence<DomainIdInfo> domain_id_info_seq field in the
DatabasePeriodic type used for Monitoring
and defined in CdsMonitoring.idl has been removed.
This change was done as a part of refactoring the internal state of Cloud Discovery Service.
Refer to the Migration Guide
on the RTI Community portal
to see how this change could affect your upgrade to 7.0.0.
14.5.1.3.2. <refresh_period> tag removed
The <refresh_period> tag from previous releases has been replaced by
new tags. (See Improved steady state bandwidth utilization and discovery time in systems with many DomainParticipants communicating over lossy networks.) The <refresh_period> is still
present in the XSD,
and Cloud Discovery Service logs a warning if that tag is parsed; however, the value of
<refresh_period> no longer influences the operation of Cloud Discovery Service.
14.5.1.4. Third-Party Software Upgrades
The following third-party software used by Cloud Discovery Service has been upgraded:
Third-Party Software |
Previous Version |
Current Version |
|---|---|---|
libxml2 |
2.9.12 |
2.9.14 |
libxslt |
1.1.34 |
1.1.35 |
For information on third-party software used by Connext products,
see the “3rdPartySoftware” documents in your installation:
<NDDSHOME>/doc/manuals/connext_dds_professional/release_notes_3rdparty.