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 "Francesco Mari (JIRA)" <ji...@apache.org> on 2018/05/22 12:14:00 UTC

[jira] [Created] (OAK-7504) Include dynamic commit information in the persisted repository data

Francesco Mari created OAK-7504:
-----------------------------------

             Summary: Include dynamic commit information in the persisted repository data
                 Key: OAK-7504
                 URL: https://issues.apache.org/jira/browse/OAK-7504
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: segment-tar
            Reporter: Francesco Mari
             Fix For: 1.10


The data in the Segment Store doesn't provide any information about the dynamic behaviour of the system. For example, who performed the commit? How many commits were performed from the same committer?

In order to simplify debugging the dynamic behaviour of a system, it should be possible to store metadata about the commit in the super-root generated by that commit. For example, the following information might be attached to the super-root:
* The name of the thread performing the commit. This solution might prove expensive in terms of consumed disk space, but would be the most precise tool to identify the author of a commit.
* A hash of the thread name. If storing thread names proves expensive, a hash of the thread name can be stored instead. This doesn't allow to exactly identify the author of the commit, but would allow us to correlated different commits as performed by the same thread.
* Both the thread name and its hash, with the thread name stored only every Nth commit. This solution is not as precise as storing the thread name for every commit but, if there is a frequent committer, its thread name will be more likely to be sampled, thus providing a precise identity to a thread name hash.



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