-
Notifications
You must be signed in to change notification settings - Fork 9
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
Make broadcasts deliver to the sender #883
Comments
If this gets changed, remember to update docs/md/vt.md as well |
We should carefully audit the AM bcast callsites to see. I think most of them run the handler locally after broadcasting. Objgroup broadcasts go to all the nodes including the sender of the broadcast. So that is another motivation to fix this problem to make it more consistent. I don't think there's a processing order issue here, unless we rely on that local call to happen right away. We should check for that at the callsites also. I think the fix should just put it in the scheduler's queue so it gets prioritized properly. |
@JacobDomagala Can you work on this when you are done with your current issues? |
…m sys_msg to user_msg so it can be later used in user handler
…since now sender will always execute the handler
…since now sender will always execute the handler
…sent to default group should be delivered to sender
…m sys_msg to user_msg so it can be later used in user handler
…since now sender will always execute the handler
…sent to default group should be delivered to sender
…m sys_msg to user_msg so it can be later used in user handler
…since now sender will always execute the handler
…sent to default group should be delivered to sender
…st-changes 1286: Fix bcast issue introduced with #883
…st-changes 1286: Fix bcast issue introduced with #883
What Needs to be Done?
Right now, vt broadcasts over certain sets of recipients exclude the sender from having the handler called (general handler bcast, objgroup bcast, I think?) while broadcasts to collections go to all elements, even if the sender is an element. I think this may be an undesirable semantic inconsistency, depending on what callers do relative to this non-uniformity.
We should go over broadcast call sites, and see how this impacts callers. Do they all just call the handler in-line? Does this represent an issue of processing order, since all other recipients will have the broadcasts ordered by the root? Are they all doing something special, such that they really shouldn't receive the broadcast?
Is your feature request related to a problem? Please describe.
Describe potential solution outcome
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: