This section explains how to run Replay Service from a command line. In particular, it describes:
- How to Start Replay Service (Section 4.1.1).
- How to Stop Replay Service (Section 4.1.2).
- Replay Service command-line parameters (Section 4.1.3).
4.1.1. Starting Replay Service¶
Replay Service runs as a separate application. The script to run the executable is in <NDDSHOME>/bin. (See Section 1.3 for the path to NDDSHOME.)
To start Replay Service with a default configuration, enter:
This command will run Replay Service indefinitely until you stop it.
Replay Service is pre-loaded with a built-in configuration that has default settings.
4.1.2. Stopping Replay Service¶
To stop Replay Service, press Ctrl-c. Replay Service will perform a clean shutdown.
4.1.3. Replay Service Command-Line Parameters¶
The following table describes all the command-line parameters available in
Replay Service. To list the available parameters, run
All command-line parameters are optional; if specified, they override the values of any corresponding settings in the loaded XML configuration. See Section 4.2.3 for the XML elements that can be overridden with command-line parameters.
|-appName <string>||Application name used to identify this execution for remote administration, and to name the Connext DDS participant.|
|-cfgFile <string>||Semicolon-separated list of configuration file paths.
Used to find a
|-domainIdBase <int>||This value is added to the domain IDs in the
|-D<name>=<value>||Defines a variable that can be used as an alternate replacement for
XML environment variables, specified in the form $(VAR_NAME).
Note that definitions in the environment take precedence over these definitions.
|-help||Shows this help.|
|-heapSnapshotDir||Output directory where the heap monitoring snapshots are dumped.
The filename format is:
|-heapSnapshotPeriod <sec>||Period at which heap monitoring snapshots are dumped.
Enables heap monitoring if > 0.
Default: 0 (disabled)
A mask to configure the format of the log messages for both Replay Service and Connext DDS.
|-maxObjectsPerThread <int>||Maximum number of Thread-specific
objects that can be created.
|-remoteAdministrationDomainId <int>||Enables remote administration and
sets the domain ID for communication.
Default: Remote administration is not enabled.
|-remoteMonitoringDomainId <int>||Enables remote monitoring and
sets the domain ID for status publication.
Default: Remote monitoring is not enabled.
Default: 1 (exceptions)
|-version||Prints the program version and exits.|
4.1.4. Replay Service Runtime Behavior¶
Replay Service currently does not delete DataWriters, even if all original DataWriters were deleted in the recorded database.
4.1.5. Working With Large Data¶
The built-in SQLite plugin implementation available in Replay Service is prepared to handle any type size and storage format. In order to improve the fidelity of the samples published with respect to the timestamps of the original samples in the database, Replay Service internally caches the next sample to be published, so that it can be accessed more quickly when it’s time to publish. This behavior is particularly useful when replaying large data.
However, when working with large data types and massive files (or filesets), Replay Service may take a while to prepare SQL statements to work with the data, resulting in a delay in publishing the first samples for any large data topics.
Because of this delay, it is recommended that you index the user data tables for
those large topics before running Replay Service on them. Indexing can massively
improve Replay Service’s startup time for those topics. You can create the
indexes offline, after Recording Service has finished recording all the data.
Index the tables on the
For example, imagine a table,
VeryLargeTopic@0, has been created by
Recording Service; you can use the following index creation statement:
CREATE INDEX IF NOT EXISTS [VeryLargeTopic@0_idx_rt] ON [VeryLargeTopic@0] (SampleInfo_reception_timestamp)