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

Rishabh Kumar commented on OAK-9913:
------------------------------------

Hi

Currently, we are using 
[DocumentStoreStats|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-store-document/src/main/java/org/apache/jackrabbit/oak/plugins/document/DocumentStoreStats.java]
 class to collect mongo document store operation stats.

We plan to update this existing class DocumentStoreStats.java to add metrics 
for mongo DB operations while throttling is ON.

We have figured out that only 4 existing APIs i.e. doneCreate, 
doneCreateOrUpdate, doneFindAndModify & doneRemove needs to be updated to 
collect the stats for mongo operations while throttling is ON.

Our changes depend upon the 
[Throttler|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-store-document/src/main/java/org/apache/jackrabbit/oak/plugins/document/Throttler.java]
 object and the following are the 2 ways in which we can pass this object to 
DocumentStoreStats.java:
 # Update the signature of above mentioned 4 APIs to give the throttler object 
from MongoDocumentStore.java
 ## We need to change the existing APIs and all the client code must be updated 
to pass the new variable.
 # Add another API in DocumentStoreStats.java to set the throttler.
 ##  This must be explicitly called to set the required throttler instance from 
the respective document store.

 

cc [~mreutegg] [~stefanegli] 

> Expose Metrics for Mongo DocumentStore throttling
> -------------------------------------------------
>
>                 Key: OAK-9913
>                 URL: https://issues.apache.org/jira/browse/OAK-9913
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>            Reporter: Rishabh Kumar
>            Priority: Major
>
> Expose metrics for the Mongo DocumentStore throttling feature. This allows us 
> to better observe when the DocumentStore is throttled.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to