0

Hi I am having an issue with mongo version 2.6.4 my insert queries has became extremely slow after update when i check log on primary i got this

2014-09-16T16:40:18.576+0530 [conn51476] insert ibeat20140916.pageTrendLog query: { _id: ObjectId('54181a9aaf81111fafbe8c44'), url: "http://timesofindia.indiatimes.com/entertainment/telugu/movies/news/Deepika-Padukone-comes-out-in-support-of-Swetha-Babu/articleshow/42396946.cms?inte...", sessionId: "ca2bf536-e98e-44fb-c2d5-a881d2ee75b3", ip: "119.226.77.150", pgDownloadTime: 510, agentType: "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0...", referer: "http://traffic.outbrain.com/network/redir?p=naQdy%2Fzis%2FCA%2FMjPzUSnnVbtZXahRKTZ3g5i9WAjjPbUG68csKBg1qkMMkajH9nYEcmndghMbZ216hl%2FL3us6Z%2BQq2BI7T1Y...", domain: "timesofindia.indiatimes.com", channel: "TNN", host: "timesofindia.indiatimes.com", pgAccessTime: 1410865818469, contentType: 1, articleId: "42396946", location: 1, action: 1, cat: "Entertainment", subcat: "Telugu", tags: [ "tollywood", "telugu cinema", "swetha basu", "deepika padukone fimls", "deepika padukone" ], isIndia: 1, geoLocation: "Delhi/NCR", publishTime: 1410616680000, author: "", pagePosition: "", ssoId: null } ninserted:1 keyUpdates:0 numYields:0 locks(micros) w:521 113ms

2014-09-16T16:40:18.576+0530 [conn51476] command ibeat20140916.$cmd command: insert { $msg: "query not recording (too large)" } ntoreturn:1 keyUpdates:0 numYields:0 locks(micros) w:177 reslen:140 113ms

Could you please check why this is happening.

  • I would add a few additional details to this: What version of MongoDB were you running prior to 2.6.4? Where are you measuring insert time (client, db log, ?). How long were you inserts taking before upgrade? – James Wahlin Sep 17 '14 at 13:04
  • I was running 2.4.2 version before 2.6 – viren Dec 9 '14 at 4:59
  • Can you upgrade to 2.6.5 and see whether it improves performance? The MongoDB query engine was rewritten for 2.6 and there have been regressions fixed with each minor release. It could be that your read/update path is not running as efficiently and impacting insert latency as a side-affect. – James Wahlin Dec 9 '14 at 14:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.