LogReaderEnabled

If set to yes, Logreader capability is enabled and the server can act as a source database for replication.

no

RO

MaxLogSize

Size (in megabytes) of the protected portion of the disk-based transaction log.

Follow the value with G (to specify a value in GB).

For example: MaxLogSize=20G

When the log files are removed (for example after a backup), at least the specified amount of the log data is retained. The protected portion of the log facilitates a possible catchup after a failure case when the replication has not been active for some time.

The actual log size can exceed the MaxLogSize value, if the log files are not removed. Catchup is possible as long as the propagator log position is within the existing log.

The minimum value is 5 (5 MB). If you attempt to define a smaller log size, it is automatically changed to 5 MB. The maximum possible log size is unlimited.

10G)

RW

MaxMemLogSize

Maximum size (in megabytes) of the Logreader logfile in memory, when logging is not enabled (Logging.LogEnabled = no).

Follow the value with G (to specify a value in GB).

For example: MaxMemLogSize=2

After maximum size is reached, Logreader catchup might not be possible anymore.

1

RW

MaxQueueLen

Maximum length (in records) of the Logreader queue after which the Logreader cursor is aborted.

If set to 0, there is no limit.

This parameter is usually used together with LogReader.SpaceWaitTimeout.

When LogReader.SpaceWaitTimeout is set, the default value for maximum queue length is at least 3 * LogReader.MaxSpace.

0

RW/
Startup

MaxSpace

Maximum number of log records buffered before slowdown.

The log records are buffered in an in-memory Logreader buffer. The size of a log record is that of the (binary) row size, plus a few bytes of additional metadata overhead.

When the buffer fills up, throughput throttling is applied in the solidDB server: the operations are blocked until there is room in the Logreader buffer.

The throttling only takes place when the log reading is active. If there is no Logreader activity, the solidDB server continues the processing and log files are preserved at least until the value defined in LogReader.MaxLogSize is reached.

100000

RW

Silent

If set to yes, the Logreader activities are not output to solmsg.out.

no

RW/
Startup

SpaceWaitTimeout

Maximum wait time (in milliseconds) for Logreader space manager.

If set to 0, there is no timeout.

This parameter is usually used together with LogReader.MaxQueueLen.

0

RW/
Startup

Timeout

Time (in seconds) after which Logreader closes the cursor if Logreader has run out of space and the client has stopped reading.

60

RW/
Startup

UseThrottling

If set to yes, Logreader uses throttling to block operations until there is space in the Logreader buffer.

yes

RW/
Startup