top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

GridFS writes to mongod after sharding

0 votes

We recently sharded a replica set and missed a process update which allowed that process to bypass the mongos and continue writing GridFS documents directly to the original replica set. The mongos seems to be aware of the fs.files document but cant find the fs.chunks related to that document. The fs.chunks can be found by going directly to the original mongod. Is there an easy way to tap mongos on the shoulder and say "hey, look over there"?

posted Jan 27, 2017 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+1 vote

I generated some GridFs data on local MongoDB but I want to export these files only to production MongoDB.
I just have uploadtime field to query these files. Is there some option in Export to JSON by mongoexport both files and chunks after time stamp.

+1 vote

Does anyone know how I remove orphaned documents in a cluster (sharding) in mongodb version 3.0.10, My actual data are 20 million orphans and documents the value amounts to 21 million data

0 votes

I thought the time limit for Mongos to connect to Mongod was hard coded to 30 seconds. But some times after less than 2 seconds I see the following exception in the mongos logs -
Failed to connect to HOST:27017 - ExceededTimeLimit: Operation timed out
Any idea why?