[SERVER-23955] Return what host the Shard::runCommand actually ran on Created: 27/Apr/16  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 1
Labels: AdiZ
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-18940 Optimise sharded aggregations that ar... Closed
is related to SERVER-22760 Sharded aggregation pipelines which i... Closed
Assigned Teams:
Cluster Scalability
Sprint: Sharding 14 (05/13/16), Sharding 15 (06/03/16)
Participants:

 Description   

Add a HostAndPort 'target' field to Shard::CommandResponse.



 Comments   
Comment by Spencer Brody (Inactive) [ 06/Jun/16 ]

Moving to 3.3 Desired to match the tickets that prompted this work.

Comment by Charlie Swanson [ 06/Jun/16 ]

spencer, yes. I think it is still needed.

As we discussed, I think this is needed to get out of our old-style command forwarding here. We need the information about which host it executed on in order to know where to send the getMore. I think we wanted to get out of this old-style forwarding as part of SERVER-22760 or SERVER-18940.

You mentioned that this might be easy enough that someone on the query team could do it. I'll leave it assigned to you in case you get around to it, but future readers of this comment should keep that in mind.

Comment by Spencer Brody (Inactive) [ 02/Jun/16 ]

charlie.swanson, this ticket was added because benjamin.murphy thought it would be needed for some work happening in aggregation. Do you know if this is still something you expect to need for 3.4?

Generated at Thu Feb 08 04:04:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.