Hi,

This might be more of a feature request rather than a bug. If you have a sharded cluster with lots of shards and a collection with several indexes, it is common to see the error following error when running the command from the router:

In this example, I can reproduce the issue with 50 shards and a collection with 50-100 indexes:

mongos> db.getSiblingDB("XXXX").getCollection("YYY").stats()
{
"ok" : 0,
"errmsg" : "BufBuilder attempted to grow() to 67210445 bytes, past the 64MB limit.",
"code" : 13548,
"codeName" : "Location13548",
"operationTime" : Timestamp(1683741378, 653),
"$clusterTime" : {
"clusterTime" : Timestamp(1683741378, 653),
"signature" : {
"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
"keyId" : NumberLong(0)
}
}

So, as Mongo continues to be used over these years, the clusters continue to grow and face architecture limitations. I suggest documenting this limitation or considering it a bug and increasing the limit (ideally, making it configurable through a parameter).

Thanks,