[
https://issues.apache.org/jira/browse/HBASE-27762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-27762:
---------------------------------
Release Note:
<!-- markdown -->
Log the `o.a.h.hbase.executor.EventType` and ProcedureV2 pid in log messages
via MDC. Enabled by default on master and branch-2. To opt-in for a branch-2.5
or branch-2.4 release, make an appropriate change to `conf/log4j2.properties`.
was:
<!-- markdown -->
Log the `o.a.h.hbase.executor.EventType` and ProcedureV2 pid in log messages
via MDC. Enabled by default on master and branch-2. To opt-in for a branch-2.5
release, make an appropriate change to `conf/log4j2.properties`.
> Include EventType and ProcedureV2 pid in logging via MDC
> --------------------------------------------------------
>
> Key: HBASE-27762
> URL: https://issues.apache.org/jira/browse/HBASE-27762
> Project: HBase
> Issue Type: Task
> Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.5.3
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
> Fix For: 3.0.0-alpha-4
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
