Sharded mongos shows zero in "ops" "sharded"

[Rick C.]

Hi,

I have a sharded database and I actually went to each individual server to see the file size and they're there, sh.status() has partitioned:true with a good amount of chunks.

However, when I connect to mongos on one of the app servers and run db.serverStatus(), I get this:
"ops" : {
        "sharded" : {
                "insert" : 0,
                "query" : 0,
                "update" : 0,
                "delete" : 0,
                "getmore" : 0,
                "command" : 0
        },
        "notSharded" : {
                "insert" : 1618,
                "query" : 181305,
                "update" : 136656,
                "delete" : 2881,
                "getmore" : 1,
                "command" : 149301
        }
}

Did I set up mongos wrong? Or did I run db.serverStatus() at the wrong place?

[jean carlo]

I think that the answer is the second one, because I had the same behavior, I almost sure that the mongos should not have this information. But the config database actually have this, prove with use config and run  db.serverStatus()

--

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

[Rick C.]

Hi,

I tried to "use config" and run it again. Same problem.
I have another mongo cluster, running 2.0 and it had all ops on "sharded". Could this be a 2.2 change?

Thanks,
Rick

[Rick C.]

Issue found. It's the rebalancer.

Thanks,

Rick

On Thursday, November 15, 2012 3:34:48 PM UTC-8, Rick C. wrote:

[gluz]

Hi,

I have the same problem could you elaborate if this is a problem or not and if it is, how did you fix it?

Thanks,

Gil

[Shaun]

Hi Gil and Rick,

These stats are not updated anymore because they are no longer meaningful.  The "sharded" and "notSharded" operations used to have two different code paths, but they were consolidated.  The names are there for historical reasons and are a bit misleading.  You can look at SERVER-7717 to follow this issue and get more information.

Thanks,
~Shaun Verch