[SERVER-42415] Duplicate key log lines are truncated Created: 25/Jul/19  Updated: 27/Oct/23  Resolved: 29/Jul/19

Status: Closed
Project: Core Server
Component/s: Logging, Tools
Affects Version/s: 4.0.10
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dheeraj Gunda Assignee: Danny Hatcher (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Microsoft Word Jira_ticket_Mongo.docx    
Operating System: ALL
Participants:

 Description   

Robo3T is showing the full error log when duplicate documents are getting inserted, but few field values in Mongod logs are getting hidden.

Inserting to MongoDB Sharded cluster with Uniqueness on Shard key

 



 Comments   
Comment by Danny Hatcher (Inactive) [ 29/Jul/19 ]

We truncate some aspects of longer log messages in order to help bound the size of any given log line. The reason that one insert only truncated some of the duplicate key information and the other one truncated all of it is due to the character count of the respective logs. The Spark insert involved a longer collection name and longer index names than the other insert which explains why more of it is truncated. The involvement of Robo3T is not relevant in this case.

Therefore, this is our logging system currently working as designed.

Generated at Thu Feb 08 05:00:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.