# Huge mongodb.log on Percona MongoDB Aribiter

**URL:** <https://forums.percona.com/t/huge-mongodb-log-on-percona-mongodb-aribiter/34420>\
**Category:** Percona Server for MongoDB\
**Created:** [October 17, 2024, 10:04am UTC](https://forums.percona.com/t/huge-mongodb-log-on-percona-mongodb-aribiter/34420 "2024-10-17T10:04:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Altin\_Tushe](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/altin_tushe/32/14319_2.png) [@Altin\_Tushe](https://forums.percona.com/u/Altin_Tushe)\
**Post date:** [October 17, 2024, 10:04am UTC](https://forums.percona.com/t/huge-mongodb-log-on-percona-mongodb-aribiter/34420/1 "2024-10-17T10:04:36Z")

</div>

Hi All,

I have a Percona MongoDB (version 7.0.11-6) replica set consisting of two data-bearing nodes and one arbiter node.

While reviewing the arbiter’s log (`mongodb.log`), I noticed several lines (250K rows in 3 days) with information like the following:  
{“t”:{“$date”:“2024-10-10T03:43:56.002+02:00”},“s”:“W”, “c”:“QUERY”, “id”:23799, “ctx”:“ftdc”,“msg”:“Aggregate command executor error”,“attr”:{“error”:{“code”:26,“codeName”:“NamespaceNotFound”,“errmsg”:“Unable to retrieve storageStats in $collStats stage :: caused by :: Collection [local.oplog.rs] not found.”},“stats”:{},“cmd”:{“aggregate”:“oplog.rs”,“cursor”:{},“pipeline”:[{“$collStats”:{“storageStats”:{“waitForLock”:false,“numericOnly”:true}}}],“$db”:“local”}}}

It seems there is an error related to the execution of the `Aggregate` command, specifically a `NamespaceNotFound` error, which is likely caused by the missing `local.oplog.rs` collection.

Has anyone encountered a similar issue or have suggestions on how to resolve this?

Thanks in advance for your help!

AT

---

<div class="post-metadata">

**Author:** ![Igor\_Solodovnikov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/igor_solodovnikov/32/1265_2.png) [@Igor\_Solodovnikov](https://forums.percona.com/u/Igor_Solodovnikov)\
**Post date:** [October 21, 2024, 8:08am UTC](https://forums.percona.com/t/huge-mongodb-log-on-percona-mongodb-aribiter/34420/2 "2024-10-21T08:08:01Z")

</div>

Hello,  
Arbiters are not supposed to have any collections or execute any aggregations.  
I would suggest to check replica set status information and ensure there is nothing wrong with this arbiter’s config. Then if configuration is OK try to figure out from the logs which client is trying to execute aggregation on arbiter.

---

<div class="post-metadata">

**Author:** ![Max\_Makarov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/max_makarov/32/18821_2.png) [@Max\_Makarov](https://forums.percona.com/u/Max_Makarov)\
**Post date:** [November 7, 2024, 3:19pm UTC](https://forums.percona.com/t/huge-mongodb-log-on-percona-mongodb-aribiter/34420/3 "2024-11-07T15:19:31Z")

</div>

I have the same problem with the exactly same configuration with 2 replicas + 1 arbiter.

---

<div class="post-metadata">

**Author:** ![Altin\_Tushe](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/altin_tushe/32/14319_2.png) [@Altin\_Tushe](https://forums.percona.com/u/Altin_Tushe)\
**Post date:** [November 13, 2024, 11:09am UTC](https://forums.percona.com/t/huge-mongodb-log-on-percona-mongodb-aribiter/34420/4 "2024-11-13T11:09:36Z")

</div>

Hi Max,  
while analyzing the mongodb.log, I noticed numerous entries related to FTDC (Full-Time Diagnostic Data Capture) with the context “ctx”:“ftdc”.  
To reduce these entries, I modified the MongoDB configuration file adding the following setting (only on arbiter node):

setParameter:  
diagnosticDataCollectionEnabled: false

After applying this change, mongodb.log is smaller