Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-27762

Include EventType and ProcedureV2 pid in logging via MDC

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.6.0, 3.0.0-alpha-4, 2.5.3, 2.4.17
    • 2.6.0, 3.0.0-alpha-4, 2.5.5, 2.4.18
    • None
    • None
    • Hide
      <!-- markdown -->
      Log the `o.a.h.hbase.executor.EventType` and ProcedureV2 pid in log messages via MDC. PatternLayouts on master and branch-2 have been updated to make use of the MDC variables. Note that due to LOG4J2-3660, log lines for which the MDC is empty will have extraneous characters. To opt-in on branch-2.5 or branch-2.4, make an appropriate change to `conf/log4j2.properties`.
      Show
      <!-- markdown --> Log the `o.a.h.hbase.executor.EventType` and ProcedureV2 pid in log messages via MDC. PatternLayouts on master and branch-2 have been updated to make use of the MDC variables. Note that due to LOG4J2-3660 , log lines for which the MDC is empty will have extraneous characters. To opt-in on branch-2.5 or branch-2.4, make an appropriate change to `conf/log4j2.properties`.

    Description

      Tracing the distributed actions of ProcedureV2 RemoteProcedure execution is painful. We are pretty good about logging the proc_id most of the time, but we don't catch them all. Now that we're up on log4j2, let's use the MDC feature to include some basic information universally.

      Attachments

        Issue Links

          Activity

            People

              ndimiduk Nick Dimiduk
              ndimiduk Nick Dimiduk
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: