Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-8397

Integrate individual uses '__wt_msg' into the verbose messaging subsystem

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.1, 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5
    • Storage - Ra 2021-11-29

      With the introduction of WT-8254 & WT-8258, the WiredTiger verbose messaging system can now use verbosity levels and produce JSON encoded message strings.

      Currently 'wt_msg' does not follow the same code paths as the other internal message interfaces (i.e. doesn't call 'eventv'), rather short circuits and calls the 'WT_EVENT_HANDLER:handle_message' interface function directly. The intention of this ticket is to more closely integrate uses of 'wt_msg' with the verbose messaging system (such that it unifies the message interfaces), allowing it to benefit from the new additions introduced in WT-8254 & WT-8258. (e.g. JSON-encoded strings).

      Definition of Done:

      • Introduce a new verbosity level i.e. 'WT_VERBOSE_NOTICE' (in-between 'WT_VERBOSE_INFO' & 'WT_VERBOSE_WARNING'). 'WT_VERBOSE_NOTICE' is an always-on verbosity level used for printing messages, this matching the always on visibility requirements of 'wt_msg'.
      • Update uses of 'wt_msg' with an equivalent 'wt_verbose' call (using the 'WT_VERBOSE_NOTICE' level).
        • Previous uses of '__wt_msg' will now need to be accompanied with a verbose category.

       

            Assignee:
            alison.felizzi@mongodb.com Alison Felizzi (Inactive)
            Reporter:
            alison.felizzi@mongodb.com Alison Felizzi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: