.. include:: vars.rst .. _section-release-notes: Release Notes ============= Supported Platforms ------------------- |CDS| is supported on the platforms listed in :numref:`TableSupportedPlatforms`. .. list-table:: Supported Platforms in 6.1.0 :name: TableSupportedPlatforms :widths: 10 90 :header-rows: 1 * - Platform - Operating System * - Linux® - All Linux platforms on x64 CPUs in the |CORE_RELNOTES| with the same version number, except SUSE® Linux Enterprise Server. * - macOS® - All macOS platforms in the |CORE_RELNOTES| with the same version number. * - Windows® - All Windows platforms in the |CORE_RELNOTES| with the same version number. Note: POSIX®-compliant architectures that end with "FACE_GP" are not supported and custom platforms are not supported. Compatibility ------------- For backward compatibility information between |CDS| 6.1.0 and previous releases, please see the *Migration Guide* on the `RTI Community portal `_. Connext DDS Compatibility ^^^^^^^^^^^^^^^^^^^^^^^^^ |CDS| can be used to provide discovery for applications built with *RTI Connext DDS*, 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 6.1.0 ------------------- New platforms ^^^^^^^^^^^^^ |CDS| now includes support for these platforms: - macOS 10.15 (x64) - Red Hat® Enterprise Linux 7.6 (x64) - Ubuntu® 20.04 LTS (x64) For more information on these platforms, see the |CORE_PLATNOTES|. Removed platforms ^^^^^^^^^^^^^^^^^ These platforms are no longer supported: - 32-bit Linux and Windows platforms - macOS 10.12 - Ubuntu 12.04 LTS Advanced logging support ^^^^^^^^^^^^^^^^^^^^^^^^ .. CDS-47 This release provides you with more context while troubleshooting, and helps RTI Support better diagnose problems when inspecting a log file. For information on the various logging verbosities, see :ref:`section-cloud-discovery-service-command-line-parameters`. Remote monitoring support ^^^^^^^^^^^^^^^^^^^^^^^^^ .. CDS-48 This release adds support for remote monitoring. This allows you to enable the publication of samples on the three standard monitoring topics (Config, Event and Periodic). It also provides a way to check the health of the service when deployed in production. For details, including the metrics published by |CDS|, see :ref:`section-cloud-discovery-service-monitoring`. Remote administration support ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. CDS-56 This release adds support for remote administration. This allows you to issue remote commands to control the service and inspect its internal state. For details, see :ref:`section-cloud-discovery-service-administration`. Service API support for C and Modern C++ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. CDS-57 This release adds support for the Service API in the C and Modern C++ languages. This allows you to integrate |CDS| as a component in your own application. For details, see :ref:`section-sdk`. What's Fixed in 6.1.0 --------------------- Memory leak after receiving repeat discovery announcement if role_name or name set in DomainParticipant's ENTITY_NAME QosPolicy ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When |CDS| received a repeat discovery announcement from an existing *DomainParticipant*, it leaked memory if either the ``name`` or ``role_name`` was set in the *DomainParticipant's* ENTITY_NAME QosPolicy. This problem has been resolved. [RTI Issue ID CDS-74] Crash when a dispose or update participant announcement was received ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ In previous releases of |CDS|, on some Windows architectures, if a dispose or update participant announcement was received, it would result in a crash. This was due to an issue when trying to look up an inserted value. This problem has been resolved. [RTI Issue ID CDS-80]