accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1508) Improve MajC logging
Date Tue, 11 Jun 2013 23:18:19 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680801#comment-13680801
] 

Mike Drob commented on ACCUMULO-1508:
-------------------------------------

Looking at {{Tablet.java}} line 3235 I see:
{code}
log.debug(String.format("MajC initiate lock %.2f secs, wait %.2f secs", (t3 - t2) / 1000.0,
(t2 - t1) / 1000.0));
{code}
I don't see any log statements before that to indicate what it is about to compact.

There is a log statements after it is done compacting, but that's not always useful when trying
to figure out where compactions may be having/causing issues.
                
> Improve MajC logging
> --------------------
>
>                 Key: ACCUMULO-1508
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1508
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.4.3, 1.5.0
>            Reporter: Mike Drob
>            Priority: Minor
>              Labels: newbie
>             Fix For: 1.4.4, 1.5.1, 1.6.0
>
>
> MajC logging prints messages when a compaction starts and finishes, but it doesn't provide
any mechanism to match the start/end. It would be useful to include a table extent or fate
ID or both or even just a one-up counter in the logs to add some value.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message