What is the %SYS.Monitor.Control.1 process doing with journal files?

Question

Question

Fabio Care · May 26, 2023

In the Windows Ressource Manager I can observe multiple parallel processes coming from cache.exe with read operations to journaling files.

All except one of these processes have the same reads(Byte/s). The processes point to different journal files and constantly read between 200 and 3000 Bytes/s.

The corresponding process via PID in the management portal of Caché shows the process %SYS.Monitor.Control.1. In 3 days of uptime on the server it has run 181.632.583 commands and modified 32.140.642 globals.

These processes are not writing to the journal at any point. I can see a seperate process that does all the writing to the current journal without having any reads.

What kind of process would read old journaling files without a rollback happening? Can you disable it?

Product version: Caché 2018.1

$ZV: Cache for Windows (x86-64) 2018.1.7 (Build 721U) Fri Mar 18 2022 22:07:35 EDT

Discussion (2)2

Log in or sign up to continue

Lucas Fernandes · May 29, 2023

This process is related to the Caché System Monitor. Monitors various resources, including the Journal.

"Caché System Monitor is a flexible, user-extensible utility used to monitor a Caché instance and generate notifications when the values of one or more of a wide range of metrics indicate a potential problem."

You can Stop them or customize the Sampling Interval for your environment.

See more in the documentation Caché System Monitor and Caché Monitor

1 0

score 0 · Answer 1 · 2023-05-30T16:25:55-04:00

Yes, this is the System Monitor. I believe it's always started by default, but it can be stopped manually.

It does monitor the size and growth rate of Journal files. But it also monitors for long running Transactions, which may be the journal reads you're seeing.