Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-48400

Secondary node memory arise while balancer doing work

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.13
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL

      Hi,

      We have an sharding instance configured a balancer window for 3:00am - 6:00am(GMT+8) and we observed that while balancer is doing work, all shard's secondary nodes' memory would arise. Such things would not happen on primary nodes. This may be related with the fact that all query requests are on secondary nodes. I have enabled one shard's heapProfiling and uploaded FTDC data and related logs. Please help identify this issue. Thanks!

        1. diagnostic.data.tar.gz
          149.30 MB
        2. inserts.png
          inserts.png
          73 kB
        3. mongod.log.tar.gz
          17.87 MB
        4. planCacheTotalSizeEstimateBytes.png
          planCacheTotalSizeEstimateBytes.png
          258 kB
        5. SERVER-48400.png
          SERVER-48400.png
          271 kB

            Assignee:
            dmitry.agranat@mongodb.com Dmitry Agranat
            Reporter:
            mingyan.zc@gmail.com Cen Zheng
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: