[DEBEZIUM] Update debezium health scheduler

[Arsenii-Malov]

Summary by CodeRabbit

• Bug Fixes
  • Improved recovery when a connector is registered but Kafka Connect reports no status.
  • Attempts to recreate affected connectors when configuration is still available.
  • Raises a non-recoverable error alert when recovery cannot be completed.
  • Distinguishes between connectors removed during processing and connectors lacking status information.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2ed56286-20f4-4012-82e7-b8615d2dc777

📥 Commits

Reviewing files that changed from the base of the PR and between 7a71e2e and 210e630.

📒 Files selected for processing (2)

• openframe-debezium-initializer/src/main/java/com/openframe/debezium/service/ConnectorRecoveryManager.java
• openframe-debezium-initializer/src/main/java/com/openframe/debezium/service/DebeziumService.java

---

📝 Walkthrough

Walkthrough

Changes

Connector status recovery

Layer / File(s)	Summary
Missing-status detection and recovery openframe-debezium-initializer/src/main/java/com/openframe/debezium/service/ConnectorRecoveryManager.java, openframe-debezium-initializer/src/main/java/com/openframe/debezium/service/DebeziumService.java	checkAndRecover now disambiguates missing status using connector configuration, attempts versioned recreation for existing no-status connectors, and creates a NON_RECOVERABLE_ERROR alert when recovery is not performed. Javadoc documents the ambiguous null status result.

Estimated code review effort: 3 (Moderate) | ~15–30 minutes

Sequence Diagram(s)

sequenceDiagram
  participant ConnectorRecoveryManager
  participant DebeziumService
  participant AlertService
  ConnectorRecoveryManager->>DebeziumService: getConnectorStatus(connectorName)
  DebeziumService-->>ConnectorRecoveryManager: null status
  ConnectorRecoveryManager->>DebeziumService: getConnectorConfig(connectorName)
  DebeziumService-->>ConnectorRecoveryManager: config or absent
  ConnectorRecoveryManager->>ConnectorRecoveryManager: tryRecreate with no-status trigger
  ConnectorRecoveryManager->>AlertService: create NON_RECOVERABLE_ERROR alert when recreation is not attempted

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise and broadly matches the Debezium health/recovery changes in this PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch upd/debezium

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}