Logreader is configured by using parameters in the server-side solid.ini configuration file, see LogReader section.
To configure Logreader, complete the following steps:
1 Enable Logreader by setting LogReader.LogReaderEnabled to yes.
This enables Logreader, allowing reads from SYS_LOG. The transaction logging mode is also more verbose.
2 As necessary for your environment, set the following parameters:
– Set LogReader.MaxSpace to the maximum number of log records that can be buffered into memory before throttling occurs.
– Set LogReader.MaxLogSize to the maximum size of the log you want to be available for catchup.
When the log reaches the defined size, old log data is deleted and catchup is not possible from the older LOGADDR log positions.
– Set LogReader.MaxMemLogSize to the maximum size of the Logreader log file in memory, when logging is not enabled (that is, when Logging.LogEnabled=No).
Example
[LogReader] LogReaderEnabled=yes ;Default: no ; ;MaxLogSize=100000 ;default: 10240 (MB) ; The amount of the log files (in MB) that will be always maintained ; for the sake of a possible catchup. The size should be adjusted to ; the biggest size of a catchup that is reasonable. The space declared ; is always fully occupied. ; MaxSpace=500000 ;default:100000 ; The size of the in-memory Logreader buffer used in throttling, ; in records. When the buffer fills up, the throttling (slowing down) ; is enacted. If the buffer is used, the size adds up to the : footprint of the solidDB server process.