Dynamic log distribution is a feature that allows the Security Gateway to distribute logs between the active Log Servers, instead of sending a copy of every log to each Log Server. This feature was introduced in Check Point R81.10 version, and it requires both the Management and the Gateways to be at least on version R81.10 for this to be supported12. With dynamic log distribution, the Gateway can optimize the disk space usage and network bandwidth consumption of the Log Servers, and also improve the performance and reliability of the logging system3. References: Dynamic logs distribution - Check Point CheckMates1, (CCTE) - Check Point Software2, SmartLog and SmartEvent R81.10 Administration Guide3
1: https://community.checkpoint.com/t5/Management/Dynamic-logs-distribution/td-p/142732 2: https://www.
checkpoint.com/downloads/training/DOC-Training-Data-Sheet-CCTE-R81.10-V1.0.pdf 3: https://sc1.
checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_LoggingAndMonitoring_AdminGuide
/html_frameset.htm

When a process is frozen (hung or unresponsive), the typical method to resolve it is to kill the process. On Check Point, you can use cpwd_admin kill -name <ProcessName> or a standard Linux kill -9 <PID> command if necessary. You then allow CPWD (the Check Point watchdog) to restart it, or manually restart it if needed.
Other options:
A . Power off the machine: This is too drastic and not recommended just for a single frozen process.
B . Restart the process: While this sounds viable, you typically must kill the frozen process first, then let WatchDog or an admin restart it.
C . Reboot the machine: Similar to powering off-too disruptive for just one stuck process.
Hence, the most direct and standard approach:
"Kill the process."
Check Point Troubleshooting Reference
sk97638 - Explanation of CPWD (Check Point WatchDog) and how to manage processes.
sk43807 - How to gracefully stop or kill a Check Point process.
Check Point CLI Reference Guide - Details on using cpwd_admin commands to kill or restart processes.