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

"[ftdc] serverStatus was very slow" due to which mongo daemon stopping abruptly & becomes stale

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.4
    • Component/s: None
    • Labels:
    • ALL
    • Hide

      since ftdc data is not human readable how do we interpret this issue and what's the solution to this. I've many servers where I see this issue and causing many issues with replication between nodes.

      Show
      since ftdc data is not human readable how do we interpret this issue and what's the solution to this. I've many servers where I see this issue and causing many issues with replication between nodes.

      since ftdc data is not human readable how do we interpret this issue and what's the solution to this. I've many servers where I see this issue and causing many issues with replication between nodes.

       

      Error log:

      2021-04-21T04:56:39.729+0000 I COMMAND [ftdc] serverStatus was very slow: { after basic: 2165, after asserts: 3087, after backgroundFlushing: 8785, after connections: 11612, after dur: 12922, after extra_info: 19620, after globalLock: 27972, after locks: 41890, after logicalSessionRecordCache: 51379, after network: 55947, after opLatencies: 62013, after opcounters: 67473, after opcountersRepl: 70586, after repl: 74168, after security: 78481, after storageEngine: 78629, after tcmalloc: 78629, after transactions: 78629, after transportSecurity: 78629, after wiredTiger: 78813, at end: 79004 }

            Assignee:
            dmitry.agranat@mongodb.com Dmitry Agranat
            Reporter:
            bharath_achar@outlook.com Bharath Kumar CM
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: