Persistent QoS Policy Not Working & Need Guidance for dds_ps Compilation in CycloneDDS

[Dante-Go]

Dear CycloneDDS Maintainers,

I'm using CycloneDDS 0.10.5 and facing critical issues with durability QoS policies:

1. Only TRANSIENT_LOCAL works as expected; PERSISTENT (and TRANSIENT) policies have no effect—new subscribers can’t retrieve historical data after publishers restart.
2. I can’t find clear instructions to compile and enable the Persistence Service (dds_ps) in the official docs. The README.md lacks details on required CMake options or setup steps for dds_ps.

Could you please clarify:

• Does CycloneDDS officially support the PERSISTENT durability policy?
• What are the exact steps to compile dds_ps (e.g., CMake flags, dependencies)?
• How to configure dds_ps and application QoS to make the PERSISTENT policy work (e.g., XML config snippets, service startup commands)?

My environment: Windows 10 (VS 2022) / Ubuntu 22.04. Any guidance or examples would be greatly appreciated!

Best regards,
kai

[TheFixer]

The persistent and transient profiles are currently not supported in the open source CycloneDDS, only the volatile and transient-local profiles are.

However, transient support is available as a commercial offering by ZettaScale (which is a major contributor to CycloneDDS). This will give you a daemon that you can deploy anywhere in your system, and that collects the transient data in the system to make it available to late joiners, even when the original writers have left. For fault tolerance you can deploy multiple daemons that will keep each other in sync, so if one fails or becomes disconnected others still retain the data. Persistency support is currently being added to the daemon, and is expected to be available somewhere in 2026Q1.

In order to run the daemon you need a license. In case you want to play with transient support, I recommend to contact techsupport@zettascale.tech. They can provide you with a trial license.

TheFixer