Trigger multicast #75
Merged
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
If 'as_trigger' flag is specified, the object will only be used to trigger UDLs and will NOT apply to the K/V store.
TODO: add as_trigger flag support to C++/Java/C# clients.
|
This has been tested using the regression test framework. |
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.
We now support a new "trigger" multicast put API. Like the normal put/put_and_forget API, the object will multicast to all replicas in the shard. Unlike the normal one, the object will ONLY be used to trigger registered UDLs and will NOT apply to the K/V store. And it's simple to enable trigger multicast: set the "as_trigger" flag to true in
ServiceClient::put()orServiceClient::put_and_forget().