forked from redis/redis
-
Notifications
You must be signed in to change notification settings - Fork 0
Cluster asm api #37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Cluster asm api #37
Conversation
This file contains hidden or 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
tezc
commented
Jun 19, 2025
ShooterIT
reviewed
Jun 23, 2025
ShooterIT
reviewed
Jun 23, 2025
ShooterIT
reviewed
Jun 23, 2025
ShooterIT
reviewed
Jun 23, 2025
ShooterIT
reviewed
Jun 23, 2025
Collaborator
|
cool job, your code makes the responsibilities and interactions between the plugin and redis much clearer to me! |
ShooterIT
reviewed
Jun 23, 2025
ShooterIT
approved these changes
Jun 23, 2025
ShooterIT
approved these changes
Jun 24, 2025
tezc
commented
Jun 24, 2025
|
|
||
|
|
||
| /* Called when an ASM event occurs to notify implementation/plugin. */ | ||
| int clusterAsmOnEvent(slotRangeArray *slot_ranges, int event, void *arg); |
Owner
Author
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EDIT: Please review last version in cluster-asm branch.
@jhershberg please comment if the above api makes sense.
Some notes/concerns:
- The above API uses two functions with different operations. So far, it seemed good enough but I wonder if an operation would need to pass more arguments. Then, we may prefer to switch to function calls per operation.
- I see that plugin handles
sdsalready. So, I assume we can pass strings/errors as sds. Plugin should implement struct slotRangeArray and struct slotRange. - For the above API, task identificator is the slot ranges. So, we are not using another kind of an ID, say a sequential integer, but this is how it will be for OSS. We don't have identificator there as well, operator will distinguish operations based on slot ranges.
- I totally ignored the case the plugin will work on its own thread, please comment if we need adjustment for it.
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.
dummy impl for the cluster plugin api