...
As you can imagine, keeping log lines in memory indefinitely will cause some memory leaks over time, especially if a data integration user wants to log with incredibly high
If you don't want to discard lines (for example on a DI server where you don't know when the user will be querying the log text) you can set log line time-out and a maximum size of the central log buffer. These options are available with Pan/Kitchen/Carte-XML/DI Server but also as a number of environment variables...
Variable name | Description | Default |
|---|---|---|
KETTLE_MAX_LOG_SIZE_IN_LINES | The maximum number of log lines that are kept internally by Kettle. Set to 0 to keep all rows (default | 0 (<4.2) |
KETTLE_MAX_LOG_TIMEOUT_IN_MINUTES | The maximum age (in minutes) of a log line while being kept internally by Kettle. Set to 0 to keep all rows indefinitely (default | 0 (<4.2) |
The following options were introduced in 4.2.0-M1 to further keep memory usage under control while using repeat loops in jobs and so on:
Variable name | Description | Default |
|---|---|---|
KETTLE_MAX_JOB_ENTRIES_LOGGED | The maximum number of job entry results kept in memory for logging purposes. | 1000 |
KETTLE_MAX_JOB_TRACKER_SIZE | The maximum number of job trackers kept in memory | 1000 |
KETTLE_MAX_LOGGING_REGISTRY_SIZE | The maximum number of logging registry entries kept in memory for logging purposes. | 1000 |
4.2.0 also sets sane defaults on all these values to make sure that by default you don't run out of memory.