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

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/08/24 00:30:22 UTC

[jira] [Resolved] (KUDU-1077) Dont trace ProbeStats on a per-mutation basis

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

Todd Lipcon resolved KUDU-1077.
-------------------------------
       Resolution: Fixed
         Assignee: Todd Lipcon
    Fix Version/s: 0.8.0

this was fixed for 0.8 by ac3771f4078c1f23545494f63384c724f73cc0af

> Dont trace ProbeStats on a per-mutation basis
> ---------------------------------------------
>
>                 Key: KUDU-1077
>                 URL: https://issues.apache.org/jira/browse/KUDU-1077
>             Project: Kudu
>          Issue Type: Improvement
>          Components: ops-tooling, tablet
>    Affects Versions: Private Beta
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.8.0
>
>
> Right now we end up with a ProbeStats() entry in the log for each individual write within a batch. It's not useful in any way. We should probably just have a single trace message with the summary statistics for the whole op.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)