zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2662) Export a metric for txn log sync times
Date Fri, 28 Apr 2017 16:17:04 GMT

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

Michael Han commented on ZOOKEEPER-2662:
----------------------------------------

bq. ZOOKEEPER-261 that both of us reviewed, but it got only committed on master.

There is a closely related issue ZOOKEEPER-2325 and both combined solved an issue of inconsistent
quorum in certain cases - since we have ZOOKEEPER-2325 committed in br-3.5, 261 should be
committed to br-3.5. I believe 261 fell out of radar when we did cherry picks for 3.5. If
no objection I'll port ZOOKEEPER-261 in br-3.5.

> Export a metric for txn log sync times
> --------------------------------------
>
>                 Key: ZOOKEEPER-2662
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2662
>             Project: ZooKeeper
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Edward Ribeiro
>             Fix For: 3.5.4, 3.6.0
>
>         Attachments: ZOOKEEPER-2662.diff
>
>
> In FileTxnLog there is code that records the amount of time required to fsync the txn
log in order to warn if that time exceeds a configurable threshold. This information should
also be exported as a metric available by JMX so an important aspect of quorum performance
can be monitored. 
> ZooKeeperServerMXBean carries some global latency information for the server process
already, seems like a good place to put it if not an entirely new bean for the TxnLog. After
ZOOKEEPER-2310 might want to collect the same information for snapshots. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message