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

Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2016/07/07 15:52:10 UTC

[jira] [Resolved] (OAK-4534) add trace logging to CommitRateLimiter

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

Stefan Egli resolved OAK-4534.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.5

done in trunk in http://svn.apache.org/viewvc?rev=1751813&view=rev

> add trace logging to CommitRateLimiter
> --------------------------------------
>
>                 Key: OAK-4534
>                 URL: https://issues.apache.org/jira/browse/OAK-4534
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.5.4
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.5.5
>
>
> When debugging issues around CommitRateLimiter it would be useful to have more insight about what delays are actually applied. As that's rather noisy info {{log.trace}} is probably appropriate.



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