.. include:: vars.rst

.. _section-release-notes:

Release Notes
*************

Supported Platforms
===================
See the column for |CDS| in the 
:link_connext_dds_pro_rn:`Table of Supported Platforms for Connext Applications, in the RTI Connext Core Libraries Release Notes <#release_notes/PAMtable.htm#PAM_AppsNotCompiled>`.

Compatibility
=============

For backward compatibility information between the current and previous releases
of |CDS|, please see the *Migration Guide* on the
`RTI Community portal <https://community.rti.com/Documentation/>`_.

Connext compatibility
---------------------

|CDS| 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. |CDS| also uses the new value for
  ``message_size_max``. Consequently, |CDS| is not out-of-the-box compatible
  with applications running older versions of |CONNEXT|. Please see the
  |CORE_RELNOTES| for instructions on how to
  resolve this compatibility issue with older |CONNEXT| applications.


What's New in 7.0.0
===================

.. _section-CDS-118:

Improved steady state bandwidth utilization and discovery time in systems with many DomainParticipants communicating over lossy networks
----------------------------------------------------------------------------------------------------------------------------------------
.. CDS-118

In lossy networks, |DP| discovery could take longer if |DP| announcements forwarded
from |CDS| were dropped. In previous releases, the ``<refresh_period>`` configuration 
tag could be used to resend |DP| announcements periodically.
The tradeoff of using that parameter was that it could lead to unnecessary network
traffic on systems that had completed |DP| discovery (because the
``<refresh_period>`` mechanism continued resending indefinitely).

In this release, the ``<refresh_period>`` is replaced with a more efficient
way to resend |DP| announcements. This new mechanism resends the |DP| announcements
from |CDS| a finite number of times, spaced randomly in an interval between
a minimum and maximum value:

.. code-block:: xml

    <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 
:ref:`section-config-forwarder`.

.. _section-CDS-150:

|DP_PARTITIONs_HEADING| support
-------------------------------
.. CDS-150

|CDS| supports systems that utilize |DP_PARTITIONs|. Partitioning at the |DP|
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.

|DP_PARTITIONs| functionality reduces network, CPU, and memory utilization,
because |DPs| without matching partitions will not exchange information about
themselves and their |DWs| and |DRs|.

|DP_PARTITIONs| support in |CDS| ensures that |CDS| doesn't forward a |DP|
announcement to |DPs| whose partition values don't match.

For details, see :ref:`section-domain-list-partitions`.

Removals
--------

domain_id_info_seq field in DatabasePeriodic type used in monitoring removed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. MG-114

The ``@optional sequence<DomainIdInfo> domain_id_info_seq`` field in the 
DatabasePeriodic type used for :ref:`section-cloud-discovery-service-monitoring`
and defined in ``CdsMonitoring.idl`` has been removed. 
This change was done as a part of refactoring the internal state of |CDS|. 
Refer to the *Migration Guide* 
on the `RTI Community portal <https://community.rti.com/Documentation/>`_
to see how this change could affect your upgrade to 7.0.0.

<refresh_period> tag removed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. MG-113

The ``<refresh_period>`` tag from previous releases has been replaced by  
new tags. (See :ref:`section-CDS-118`.) The ``<refresh_period>`` is still 
present in the XSD, 
and |CDS| logs a warning if that tag is parsed; however, the value of 
``<refresh_period>`` no longer influences the operation of |CDS|.


Third-Party Software Upgrades
-----------------------------
.. THIRDPARTY-1 (libxml2 and libxslt)

The following third-party software used by |CDS| has been upgraded:

.. list-table:: Third-Party Software Changes
    :name: ThirdPartyChanges
    :widths: 40 40 40
    :header-rows: 1

    * - 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``.


What's Fixed in 7.0.0
=====================

Problems with Discovery after disposal of a Remote Participant
--------------------------------------------------------------

|CDS| 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]

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

|CDS| 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]


Cloud Discovery Service did not allow use of UDPv6 transport alias
-------------------------------------------------------------------

|CDS| 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]


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``, |CDS| crashed due to a parsing error. This problem
has been resolved.

[RTI Issue ID CDS-176]


Known Issues
============

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


Cloud Discovery Service does not terminate when its internal DomainParticipant does not initialize properly
-----------------------------------------------------------------------------------------------------------
|CDS| creates an internal |DP| that reserves the *participant_id* 0, on domain ID 0.
This |DP| is required by |CDS| to relay the participant discovery announcements.
If the *participant_id* 0 for domain ID 0 is already being used by another
|CONNEXT| application, |CDS| throws errors but doesn't terminate.

Although such a |CDS| instance is running, it won't be able to relay any participant
discovery announcements. A simple workaround is to ensure that |CDS| is always
the first |CONNEXT| application started on a given machine.

[RTI Issue ID CDS-143]