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

Posted to issues@kudu.apache.org by "Anupama (JIRA)" <ji...@apache.org> on 2018/05/29 23:27:00 UTC

[jira] [Resolved] (KUDU-702) Add block IDs to more log messages

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

Anupama resolved KUDU-702.
--------------------------
    Resolution: Fixed

> Add block IDs to more log messages
> ----------------------------------
>
>                 Key: KUDU-702
>                 URL: https://issues.apache.org/jira/browse/KUDU-702
>             Project: Kudu
>          Issue Type: Bug
>          Components: tablet
>    Affects Versions: Private Beta
>            Reporter: Todd Lipcon
>            Assignee: Anupama
>            Priority: Trivial
>              Labels: newbie
>             Fix For: 1.8.0
>
>
> When debugging KUDU-701, I found it somewhat difficult because many of our block IDs never get logged. We should add the block ID to the INFO log when we open new cfiles, the bloom file, etc.
> Similarly, we should output the new DRS IDs when a compaction finishes (right now it's difficult to see when a DRS first gets written)



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