create_published_mef_list.py

Ensures that no events are lost when an engine failover occurs by generating a list of MATRIXX Event Files (MEFs) that were already published. This script creates the published_mef_list.txt output file on the publishing host. This script also sends results to the console if run manually, or it creates a create_published_mef_list.log file on the local system when it is run programmatically. Run this script as user mtx if you run it manually.

Note: Sorted transaction logging is enabled by default in your MATRIXX environment. When enabled, the Global Transaction Counter (GTC) ranges stored in the transaction log files include the minimum and maximum GTC ranges (when available), and the maximum and minimum time stamp.

Syntax

If for some reason you must perform the recovery behavior of this script, you might need to run it manually. 

create_published_mef_list.py -t target_host -u username -d directory -e engineId -o output_directory [ -v ]

Options

-d directory, --mef-directory directory
Mandatory. Specifies the directory containing the published MATRIXX Event Files.
-e engineId, --engine engineId
Mandatory. The ID of the engine hosting the MEF directory specified with the -d option.
-o filename, --output filename
Mandatory. Specifies the name of the output file.
-t target_host, --target_host target_host
Mandatory. The host name of the system to run the script on.
-u username, --target_user username
Mandatory. The name of a user with permission to run the script.
-v, --verbose
Optional. Increase the verbosity of the script. More messages and statistics are printed.

Publish MEFs

create_published_mef_list.py -v -t mtx-hp2b1-vm04 -u mtx -d /home/mtx/published_MEFs -e 1 -o /tmp/published_mef_list.txt