[SERVER-16517] Secondary on 2.8.0rc2 cannot keep up (insert-heavy, mmapv1) (mms-prod-queues) Created: 11/Dec/14  Updated: 16/Jan/15  Resolved: 14/Jan/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.8.0-rc2
Fix Version/s: 2.8.0-rc5

Type: Bug Priority: Major - P3
Reporter: Cailin Nelson Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File queues_2014-12-28.png     PNG File queues_2014-12-29.png     PNG File repllag.png     PNG File repllag2.png    
Issue Links:
Related
related to SERVER-16574 Do not call Explain::getPlanSummary o... Closed
related to SERVER-16551 tcmalloc ReleaseToCentralCache accoun... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

It seems that for this particular workload, this problem is reproducible. So, please let me know what information would be helpful, and we can gather it.

For now, we are going to downgrade this secondary.

In the opcounters chart:

  • Top line: insert
  • Second line: query
  • Third line: command
  • Fourth line: update



 Comments   
Comment by Cailin Nelson [ 16/Jan/15 ]

Yay!

Comment by Andy Schwerin [ 14/Jan/15 ]

All signs indicate that this is resolved by the fix for SERVER-16829, specifically the part that raises the ceiling on the total amount of RAM in per-thread free lists for tcmalloc from 32MB to 64MB.

Comment by Githook User [ 13/Jan/15 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-16829 Expose tcmalloc configuration options for per-thread cache size and decommit behavior.

Also, increases the default cap on the sum of all per-thread cache sizes from
32MB to 64MB, as advised by SERVER-16551. Should improve behavior of
SERVER-16517, as well.
Branch: master
https://github.com/mongodb/mongo/commit/a6ca16f211fe01d2870593d9ab9bfaaa88097a14

Generated at Thu Feb 08 03:41:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.