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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2018/04/24 08:58:00 UTC

[jira] [Resolved] (OAK-7402) Expose UI for collecting IO traces

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

Michael Dürig resolved OAK-7402.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.1

Fixed at http://svn.apache.org/viewvc?rev=1829969&view=rev

> Expose UI for collecting IO traces
> ----------------------------------
>
>                 Key: OAK-7402
>                 URL: https://issues.apache.org/jira/browse/OAK-7402
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: oak-run, segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Major
>              Labels: tooling
>             Fix For: 1.10, 1.9.1
>
>
> [http://svn.apache.org/viewvc?view=revision&revision=1827841] introduced utility classes to collect IO traces. See e.g. https://issues.apache.org/jira/browse/OAK-5655?focusedCommentId=16415730&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16415730. Currently the only way to run such traces is via code or JUnit (see {{IOTracerRunner}}).
> Going forward we should wire this functionality to {{oak-run}} to make it more generally useful. 
>  
> [~frm], FYI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)