Skip to content

Conversation

tillrohrmann
Copy link
Contributor

When provisioning the cluster we are writing some metadata to the metadata store.
In case that the write succeeds, we should be able to directly update the
MetadataManager to avoid having to fetch it from the metadata store. This is a
minor optimization.

This fixes #3170.

This PR is based on #3164.

@AhmedSoliman
Copy link
Contributor

I guess this needs a rebase. Let's do that after I merge my stack.

@tillrohrmann
Copy link
Contributor Author

I've rebased it on main now.

Copy link
Contributor

@AhmedSoliman AhmedSoliman left a comment

Choose a reason for hiding this comment

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

❤️

…e cluster

When provisioning the cluster we are writing some metadata to the metadata store.
In case that the write succeeds, we should be able to directly update the
MetadataManager to avoid having to fetch it from the metadata store. This is a
minor optimization.

This fixes restatedev#3170.
@tillrohrmann tillrohrmann merged commit c80b6d7 into restatedev:main Apr 29, 2025
19 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Apr 29, 2025
@tillrohrmann tillrohrmann deleted the issues/3170 branch April 29, 2025 09:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants