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

logging write conflicts at log level 0 is too aggressive

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.8.0-rc4
    • Fix Version/s: 2.8.0-rc5
    • Component/s: Logging, Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL

      Description

      Since write conflicts are normal in multi-threaded workload that heavily updates same documents (ex: YCSB with latest or zipf distribution), the logging of it should be significantly lower.

      Recommendation:

      • LogLevel 0: log nothing (updates with a lot of writeConflicts will be logged as slow ops if they exceed slowMS threshold)
      • LogLevel 1: log update conflicts > 100 attempts
      • LogLevel 2: log update conflicts > 10 attempts
      • LogLevel 3+ : keep at current logging or log all.

        Attachments

          Activity

            People

            Assignee:
            eliot Eliot Horowitz (Inactive)
            Reporter:
            asya Asya Kamsky
            Participants:
            Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: