[SERVER-39665] out_with_drop_shard.js should not need the flushRouterConfig command Created: 19/Feb/19  Updated: 27/Oct/23  Resolved: 01/Mar/19

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Martin Neupauer Assignee: Esha Maharishi (Inactive)
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-39205 Force the cache refresh after the sha... Closed
Operating System: ALL
Sprint: Sharding 2019-03-11
Participants:

 Comments   
Comment by Esha Maharishi (Inactive) [ 01/Mar/19 ]

Closing as gone away because we discussed why flushRouterConfig is needed on SERVER-39205 (see comment).

Comment by Craig Homa [ 28/Feb/19 ]

Moving to the Sharding backlog. martin.neupauer please add any further context to help in their debugging.

Comment by Martin Neupauer [ 19/Feb/19 ]

This is a follow up to SERVER-39205. During the code review of 39205 (https://mongodbcr.appspot.com/253490001/) it was stated that flushRouterConfig should not be needed and/or reasons for the flushRouterConfig are not clear.
We have to investigate more.

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