[
https://issues.apache.org/jira/browse/ZOOKEEPER-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150657#comment-13150657
]
Camille Fournier commented on ZOOKEEPER-1239:
---------------------------------------------
Eh, I guess the popular consensus has changed on using nanotime for this sort
of thing, so disregard my question. I'll put this in shortly.
> add logging/stats to identify fsync stalls
> ------------------------------------------
>
> Key: ZOOKEEPER-1239
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1239
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.3.4, 3.4.0, 3.5.0
>
> Attachments: ZOOKEEPER-1239_br33.patch, ZOOKEEPER-1239_br34.patch
>
>
> We don't have any logging to identify fsync stalls. It's a somewhat common
> occurrence (after gc/swap issues) when trying to diagnose pipeline stalls -
> where outstanding requests start piling up and operational latency increases.
> We should have some sort of logging around this. e.g. if the fsync time
> exceeds some limit then log a warning, something like that.
> It would also be useful to publish "stat" information related to this.
> min/avg/max latency for fsync.
> This should also be exposed through JMX.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
