ZettaScale Knowledge Base ZettaScale Knowledge Base

  • Home
  • DDS Products
    • DDS Overview and Concepts
    • OpenSplice DDS
      • OpenSplice DDS
        • OpenSplice FAQ
        • Why OpenSplice DDS?
        • Installation
          • OpenSplice Licensing FAQ
        • Best Practice and Possible Errors
        • API and IDL
        • Configuration
        • Networking
          • DDSI
          • RT Networking
        • Durability Service
        • DDS Security
        • Logging
        • Databases and DBMS
        • Release Notes
      • OpenSplice Tools
        • Overview
        • OpenSplice Launcher
        • OpenSplice Tuner
        • OpenSplice Tester
        • Record and Replay Manager
        • MMStat
    • Cyclone DDS
  • Zenoh
  • Contact Support
Home / DDS, OpenSplice DDS, DDS Overview and Concepts / How long does published data remain in Shared Memory?

How long does published data remain in Shared Memory?

Published data in OpenSplice remains ‘stored in the shared-memory’ until there’s no usage for it anymore. This ‘usage’ can be identified as

  • If it is part of a writer’s history on the sample that is awaiting transferring to local subscribers and/or sending over the network,
  • If it is part of the ‘transient/persistent’ data-storage on a node made available for late-joining subscribers
  • If it is part of the dataReader cache of a subscriber.

If a developer wants to be certain that his dataWriter history is empty they can utilize the wait_for_acknowledgement() method in the API.

To assure that non-volatile data is removed from the transient/persistent data-storage a writer has to dispose its instances and/or use our extended dispose_all() method to dispose of all instances of a specific topic.

Related

DDSOpenSplice DDSDDS Overview and Concepts
twitter logo linkedin logo
News and Events
Copyright © 2022 ZettaScale Technology Ltd. All Rights Reserved