[SERVER-35790] Add shardId information to RemoteCommandRequest Created: 25/Jun/18 Updated: 23/Jun/23 Resolved: 23/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1 Desired |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Tommaso Tocci |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | LamontN | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Sprint: | Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Kaloian Manassiev [ 26/Jun/18 ] |
|
This is all part of the workflow on the sender side and will be an extension (decoration?) on the RemoteCommandRequest in order to allow all the hooks on that code path to not have to resolve the host back to a shard. It has nothing to do with the contents of the response received back. |
| Comment by Andy Schwerin [ 26/Jun/18 ] |
|
It's not obvious to me that it's safe for the recipient of a message to trust the remote node's self-identified shard. Like, what if the remote node is recently removed from its replica set? |
| Comment by Kaloian Manassiev [ 26/Jun/18 ] |
|
So we can get rid of all the resolutions from host to shard. |
| Comment by Andy Schwerin [ 26/Jun/18 ] |
|
Why? |