Workaround for fixing stale connection state data when dropping and recreating sharded collections?

[David Nesbitt]

We are experiencing the same problem as documented in
https://jira.mongodb.org/browse/SERVER-4262 regarding dropping and
recreating sharded collections. I am wondering if there is a manual
workaround for clearing the stale connection state data?

[Kristina Chodorow]

You could try running the flushRouterConfig command, but you will
probably actually have to restart the mongos to clear the state.


On Apr 16, 7:05 pm, David Nesbitt <da...@trippy.com> wrote:
> We are experiencing the same problem as documented inhttps://jira.mongodb.org/browse/SERVER-4262regarding dropping and

[David Nesbitt]

Thanks, Kristina! Restarting mongos did the trick. I will try to
update the bug with the workaround.

On Apr 17, 8:26 am, Kristina Chodorow <krist...@10gen.com> wrote:
> You could try running the flushRouterConfig command, but you will
> probably actually have to restart the mongos to clear the state.
>
> On Apr 16, 7:05 pm, David Nesbitt <da...@trippy.com> wrote:
>
>
>
>
>
>
>

> > We are experiencing the same problem as documented inhttps://jira.mongodb.org/browse/SERVER-4262regardingdropping and