CDC Forced Stop on Log Deletion

I am writing to request an enhancement in the CDC (Change Data Capture) functionality to include a forced stop mechanism when logs required by the XStream API are deleted. Currently, CDC continues to wait for logs from the XStream API, which results in no new data being processed when these logs are unavailable due to deletion.

Justification for the Enhancement:

Clear Error Notification:

• Implementing a forced stop when logs are deleted would generate a clear error notification. This helps in distinguishing between temporary issues that can be resolved without manual intervention and critical issues that require immediate attention.

Timely Action:

• A forced stop with an error notification ensures that administrators are alerted promptly. This allows for quicker resolution, minimizing downtime and potential data inconsistencies.

Operational Efficiency:

• Without this enhancement, the CDC process continues to operate in a waiting state, leading to increased latency and delayed data replication. By stopping the process and notifying administrators, we can prevent unnecessary delays and maintain the efficiency of data replication operations.

Prevention of Data Loss:

• Ensuring that the CDC stops when logs are deleted can prevent scenarios where data is not replicated for extended periods. This is particularly crucial for maintaining data integrity and consistency across systems.

Proposed Solution:

• Introduce a mechanism within CDC to detect the deletion of required logs.
• Trigger a forced stop of the CDC process when such a deletion is detected.
• Generate a detailed error message to notify administrators of the specific issue.
• Optionally, provide configuration options for administrators to enable or disable this feature based on their operational needs.