zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3019) Add a metric to track number of slow fsyncs
Date Wed, 25 Apr 2018 12:12:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452134#comment-16452134

ASF GitHub Bot commented on ZOOKEEPER-3019:

Github user nkalmar commented on the issue:

    Removed fsyncExceed from stats command, but the tracking variable still remains in ServerStats.
I was thinking of moving it to for example zkDb, but that wouldn't make any more sense in
my opinion. 
    The other option is to leave it in FileTxnLog as a static variable, that was my original
idea actually. 
    So if that is a better solution, I will change it.

> Add a metric to track number of slow fsyncs
> -------------------------------------------
>                 Key: ZOOKEEPER-3019
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3019
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: jmx, server
>    Affects Versions: 3.5.3, 3.4.11, 3.6.0
>            Reporter: Norbert Kalmar
>            Assignee: Norbert Kalmar
>            Priority: Major
>             Fix For: 3.5.4, 3.6.0, 3.4.13
> Add jmx bean and Command to ZooKeeper server to expose the the number of slow fsyncs
as a metric.
> FileTxnLog.commit() should count the number of times fsync exceeds fsyncWarningThresholdMS.

This message was sent by Atlassian JIRA

View raw message