You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2023/05/01 15:47:00 UTC

[jira] [Updated] (HBASE-27762) Include EventType and ProcedureV2 pid in logging via MDC

     [ https://issues.apache.org/jira/browse/HBASE-27762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Dimiduk updated HBASE-27762:
---------------------------------
    Fix Version/s: 2.6.0
                   2.5.5
                   2.4.18

> 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, 2.4.17
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Major
>             Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.5, 2.4.18
>
>
> 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)