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 2020/07/01 23:41:00 UTC
[jira] [Commented] (HBASE-24669) Logging of ppid should be
consistent across all occurrences
[ https://issues.apache.org/jira/browse/HBASE-24669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149743#comment-17149743 ]
Nick Dimiduk commented on HBASE-24669:
--------------------------------------
The log line I noticed is this:
{noformat}
2020-07-01 06:17:31,449 INFO org.apache.hadoop.hbase.procedure2.ProcedureExecutor: Finished subprocedure pid=116623, resume processing parent pid=116621, state=RUNNABLE:SERVER_CRASH_DELETE_SPLIT_MET
A_WALS_DIR, locked=true; ServerCrashProcedure server=hbasedn189.example.com,16020,1593583050478, splitWal=true, meta=true
{noformat}
> Logging of ppid should be consistent across all occurrences
> -----------------------------------------------------------
>
> Key: HBASE-24669
> URL: https://issues.apache.org/jira/browse/HBASE-24669
> Project: HBase
> Issue Type: Improvement
> Components: Operability, proc-v2
> Reporter: Nick Dimiduk
> Priority: Minor
>
> Most places we log {{pid}} and {{ppid}} I noticed at least one occurrence of {{parent pid}} instead of {{ppid}}. All this logging should be uniform so that it's easy to grep the logs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)