Skip to content

Conversation

@mchain0
Copy link
Contributor

@mchain0 mchain0 commented Jan 5, 2026

CRE-1627

Related to discussion

@mchain0 mchain0 requested a review from a team as a code owner January 5, 2026 09:52
@github-actions
Copy link

github-actions bot commented Jan 5, 2026

👋 mchain0, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

✅ API Diff Results - No breaking changes


📄 View full apidiff report

@mchain0 mchain0 requested a review from bolekk January 5, 2026 09:53
p.lggr.Errorw("RingOCR failed to get arbiter scaler status", "error", err)
return nil, err
p.lggr.Errorw("RingOCR exhausted retries for arbiter scaler status, using fallback", "error", err)
// Fallback to store's previous state
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm still not convinced that we want to have fallback at all.
If arbiter is down for more than F nodes, let's just start failing OCR and we won't be able to scale until we fix those Arbiters. In fact, even if fallback somehow works, those nodes won't be able to tell their arbiters to scale ;)

Copy link
Contributor Author

@mchain0 mchain0 Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, I'm not convinced myself. let's park this for now and revive if needed.

@mchain0 mchain0 closed this Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants