MySQL Replication Data Importer

The Oracle Communications Unified Assurance MySQL Replication Data Importer service imports events and event journals from the Event database (MySQL) to the Historical database (OpenSearch) for use in Observability Analytics dashboards. It monitors the MySQL binary log for changes.

The AnalyticsWizard enables and runs this service automatically. You do not need to run or set up this service manually. The information in this document is included for reference only.

If you update the service configuration, you must restart the service for the changes to take effect. See Services in Unified Assurance User's Guide for information about using the Services UI to restart a service.

Default Service

The following table shows the settings for the default service. Actual values are in bold, descriptions of values are in plaintext.

Field Default Value
Package Name historicalProcessing-app
Service Name MySQL Replication Data Importer
Service Program bin/historical/MySqlReplImporterd
Service Arguments This field is blank. There is no default value.
Service Description Imports historical events and journals from MySQL to OpenSearch
Failover Type Standalone (Supported: Standalone)
Status Disabled (Automatically switched to Enabled after running AnalyticsWizard.)
Privileged This option is selected.

Default Configuration

The following table shows the default configurations for the application. Actual values are in bold, descriptions of values are in plaintext.

Name Default Value Possible Values Notes
LogFile logs/MySQLReplImporterd.log Text, 255 characters The relative path to the log file.
LogLevel ERROR OFF, ERROR, WARN, INFO, DEBUG The logging level for the application.
ShardID 1 An integer The database shard to use.
ActiveBackup False True or False Whether this service is associated with a secondary server (True) or a primary server (False).
ReplicateOldest False True or False Whether to start reading the binlog from the oldest record (True) or from the last read location (False).
DBThreads 3 An integer The number of concurrent threads to create to synchronize data to the Historical database.
Limit 1600 An integer no greater than 1600. The maximum number of rows sent in Historical database inserts. If the row limit is reached before the time limit, the batch of rows is sent and the timer is reset. If you set this to a value greater than 1600, it is ignored, a warning appears in the logs, and 1600 is used.
BulkTime 10 An integer The maximum number of seconds to wait for the number of rows specified in Limit. If the time limit is reached before the row limit, the current batch of rows is sent.