[restatectl] Introduces replicated-loglet top-level command #2231
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 7, 2024
AhmedSoliman
force-pushed
the
pr2231
branch
3 times, most recently
from
d4c56ea
to
f063825
Compare
tillrohrmann
approved these changes
Nov 8, 2024
MetadataContainer enum was ~450 bytes and it's being used often. It also forces users to clone input which is not great. The PR contains mostly mechanical changes.
This introduces a lookup table to find replicated loglets by id in Log metadata. This also promotes replicated loglet as a core feature in restate-types since it'll become the default soon. In future follow-up we can explore deserializing the loglet params prematurely (or use typed structure instead of string) and maintain reference-counted container to avoid memory bloat. In this PR, we treat replicated loglet as a special case to speed up implementation and since this will be the de-facto loglet provider anyway.
Currently this only implements a very basic `info`. Note that the command is built merely as an example, it's UI/UX and behaviour will change by follow-ups.
Pass by stringified log_id (`<log_id>_<segment>`)
```
cargo run -q --bin restatectl -- replicated-loglet info 1_0 ✘ 1
Log Configuration (v1)
Loglet Referenced in:
- LogId=1, Segment=0
Loglet Parameters:
Loglet Id: 1_0 (4294967296)
Sequencer: N1:1
Replication: {node: 2}
Node Set: [N3, N2, N1]
```
Or raw loglet id (`<loglet_id>`)
```
cargo run -q --bin restatectl -- replicated-loglet info 1_0 ✘ 1
Log Configuration (v1)
Loglet Referenced in:
- LogId=1, Segment=0
Loglet Parameters:
Loglet Id: 1_0 (4294967296)
Sequencer: N1:1
Replication: {node: 2}
Node Set: [N3, N2, N1]
```
This was referenced Nov 8, 2024
pcholakov
reviewed
Nov 11, 2024
|
|
||
| #[derive(Run, Parser, Collect, Clone, Debug)] | ||
| #[cling(run = "get_info")] | ||
| pub struct InfoOpts { |
There was a problem hiding this comment.
No strong opinion her but we've used the verb "describe" for this type of command elsewhere - we can solve with aliases and the internal struct doesn't need to be consistent, but it may be nice for users to see the same set of sub-commands everywhere.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently this only implements a very basic
info. Note that the command is built merely as an example, it's UI/UX and behaviour will change by follow-ups.Pass by stringified log_id (
<log_id>_<segment>)Or raw loglet id (
<loglet_id>)Stack created with Sapling. Best reviewed with ReviewStack.