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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/06/16 20:25:00 UTC

[jira] [Updated] (HBASE-20745) Log when master proc wal rolls

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

stack updated HBASE-20745:
--------------------------
    Attachment: HBASE-20745.master.001.patch

> Log when master proc wal rolls
> ------------------------------
>
>                 Key: HBASE-20745
>                 URL: https://issues.apache.org/jira/browse/HBASE-20745
>             Project: HBase
>          Issue Type: Sub-task
>          Components: debugging
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 2.0.2
>
>         Attachments: HBASE-20745.master.001.patch
>
>
> Emit when we roll master proc WAL so can see when they happen. Want to correlate instances of corruption w/ events on Master. Currently hard to do on  a server where log-level is INFO (default for many deploys).
> Also, we log STUCK regions every 5 seconds. If a bundle of regions get stuck, we can log so frequently, we roll away where the problem happened so lose the chance to debug. Let me fix that too....
> Need both debugging instances of parent issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)