Skip to content

Conversation

wdberkeley
Copy link
Owner

Add retry logic to reconciler's metastore add_objects calls to handle transport errors. Previously, the reconciler would immediately fail and abandon the reconciliation round on any metastore error.

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v25.1.x
  • v24.3.x
  • v24.2.x

Release Notes

  • none

Change add_objects, replace_objects, and commit_objects method
signatures to take const refs instead of taking unique_ptr by value.
This enables retry scenarios where the builder needs to remain usable
after the call.

The replicated metastore's release method is no longer used and is
removed. The simple metastore still uses this method for testing, so it
remains.
They aren't needed for metastore add_objects, replace_objects, and
commit_objects calls, and are potentially confusing.
…errors

Add retry logic to reconciler's metastore add_objects calls to handle
transport errors. Previously, the reconciler would immediately fail and
abandon the reconciliation round on any metastore error.
@wdberkeley wdberkeley force-pushed the retry-builder-metastore branch 2 times, most recently from eebea5e to 7f5a333 Compare September 24, 2025 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant