14. Release Notes

14.1. Supported Platforms

See the column for Cloud Discovery Service in the Table of Supported Platforms for Connext Applications, in the RTI Connext Core Libraries Release Notes.

14.2. Compatibility

For backward compatibility information between the current and previous releases of Cloud Discovery Service, please see the Migration Guide on the RTI Community portal.

14.2.1. Connext compatibility

Cloud Discovery Service can be used to provide discovery for applications built with RTI Connext, except as noted below.

  • Starting in RTI Connext DDS 5.1.0, the default message_size_max for the UDPv4, UDPv6, TCP, Secure WAN, and shared-memory transports changed to provide better out-of-the-box performance. Cloud Discovery Service also uses the new value for message_size_max. Consequently, Cloud Discovery Service is not out-of-the-box compatible with applications running older versions of Connext. Please see the RTI Connext Core Libraries Release Notes for instructions on how to resolve this compatibility issue with older Connext applications.

14.3. What’s New in 7.0.0

14.3.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:




For additional information about these new parameters, see Forwarder.

14.3.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.3.3. Removals 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. <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.3.4. Third-Party Software Upgrades

The following third-party software used by Cloud Discovery Service has been upgraded:

Table 14.1 Third-Party Software Changes

Third-Party Software

Previous Version

Current Version







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.

14.4. What’s Fixed in 7.0.0

14.4.1. Problems with Discovery after disposal of a Remote Participant

Cloud Discovery Service may have assigned incorrect properties from one remote participant to another remote participant. This caused discovery problems. These incorrect properties typically belonged to another remote participant that was recently disposed. This problem has been resolved.

[RTI Issue ID CDS-155]

14.4.2. Cloud Discovery Service did not allow using other transports when Real-Time WAN Transport was enabled

Cloud Discovery Service had an issue that prevented the use of multiple transports at the same time, when the Real-Time WAN Transport (udpv4_wan transport alias) was enabled. This issue has been resolved.

[RTI Issue ID CDS-158]

14.4.3. Cloud Discovery Service did not allow use of UDPv6 transport alias

Cloud Discovery Service did not enable the UDPv6 transport (udpv6 transport alias), even when it was set in the <transport> tag. This problem has been resolved.

[RTI Issue ID CDS-161]

14.4.4. Cloud Discovery Service crashed when empty participant GUID provided to Remote Administration API

If the /cloud_discovery_services/[service_name]/database/locators Remote Administration endpoint was provided an empty Remote Participant GUID in its string_body, Cloud Discovery Service crashed due to a parsing error. This problem has been resolved.

[RTI Issue ID CDS-176]

14.5. Known Issues


For an updated list of critical known issues, see the Critical Issues List on the RTI Customer Portal at https://support.rti.com/.

14.5.1. Cloud Discovery Service does not terminate when its internal DomainParticipant does not initialize properly

Cloud Discovery Service creates an internal DomainParticipant that reserves the participant_id 0, on domain ID 0. This DomainParticipant is required by Cloud Discovery Service to relay the participant discovery announcements. If the participant_id 0 for domain ID 0 is already being used by another Connext application, Cloud Discovery Service throws errors but doesn’t terminate.

Although such a Cloud Discovery Service instance is running, it won’t be able to relay any participant discovery announcements. A simple workaround is to ensure that Cloud Discovery Service is always the first Connext application started on a given machine.

[RTI Issue ID CDS-143]