Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-2501

add more trace-logging to mongoMk to debug performance issues

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.11
    • Fix Version/s: 1.0.12, 1.1.7
    • Component/s: core
    • Labels:
      None

      Description

      Debugging performance issues within mongoMk is currently somewhat more challenging that it would have to - IMO because there is no easy logger that can be turned on to get some performance numbers. Ie currently for figuring out what's going on in mongoMk you can set the log level to TRACE for the following loggers:

      org.apache.jackrabbit.oak.plugins.observation.EventGenerator
      org.apache.jackrabbit.oak.plugins.document.mongo.MongoDocumentStore
      org.apache.jackrabbit.oak.plugins.document.NodeDocument
      org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore 
      

      while you might still not catch all interesting and crucial details.

      So the suggestion is to add a dedicated logger which is used at a couple of neuralgic locations (eg in observation event generation, cache handling, diffChildren, findUncached etc)

        Attachments

        1. oak.2501.patch
          24 kB
          Stefan Egli
        2. oak.2501.trunk.patch
          24 kB
          Stefan Egli

          Activity

            People

            • Assignee:
              mreutegg Marcel Reutegger
              Reporter:
              stefanegli Stefan Egli
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: