By using this parameter, you can enable or disable the log reader capability.

no

RO

This parameter defines the size of the protected portion of the disk-based transaction log.

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 may 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 practically unlimited.

Unit: megabytes.

10240

RW

This parameter defines the maximum number of log records buffered before slowdown.

The log records are buffered in an in-memory log reader 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 log reader activity, the solidDB^® server continues the processing and log files are preserved at least until the defined MaxLogSize limit is reached (see above).

100000

RW

Maximum size of the Log Reader logfile in memory, when logging is not enabled (Logging.LogEnabled = no). After maximum size is reached, logreader catchup might not be possible anymore.

Unit: megabytes.

1 MB

RW

If set to Yes, the Log Reader activities are not output to solmsg.out.

Possible values are yes and no.

no

RW/
Startup

Controls whether the log reader uses throttling to block operations until there is space in the log reader buffer.

yes

RW/
Startup