jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomek Rękawek (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (OAK-6582) Review MBean interactions in a composite setup
Date Fri, 15 Sep 2017 10:03:00 GMT

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

Tomek Rękawek edited comment on OAK-6582 at 9/15/17 10:02 AM:
--------------------------------------------------------------

I've analyzed the MBeans registered by the DocumentNodeStoreService and SegmentNodeStoreService:
h3. SegmentNodeStoreService
h4. CacheStatsMBean:

* Segment Cache
* String Cache
* Template Cache
* String deduplication cache stats
* Template deduplication cache stats
* Node deduplication cache stats

h4. Maintenance MBeans:

* Segment node store revision garbage collection (SegmentRevisionGC)
* Revision garbage collection (RevisionGCMBean)
* FileStore statistics (FileStoreStatsMBean)
* Segment node store checkpoint management (CheckpointMBean, for role=null)
* Segment node store blob garbage collection (BlobGCMBean, for role=null)
* Segment node store backup/restore (FileStoreBackupRestoreMBean)
* SegmentNodeStore statistics (SegmentNodeStoreStatsMBean)

h3. DocumentNodeStoreService registers:

h4. CacheStatsMBean:

* Document-NodeState
* Document-NodeChildren
* many diff cache stats
* many DocumentStore cache stats
* BlobStore-MemCache
* PersistentCache.NodeCache.* (PersistentCacheStatsMBean)

h4. Maintenance MBeans:

* Document node store checkpoint management (CheckpointMBean)
* Document node store management (DocumentNodeStoreMBean)
* DocumentStore Statistics (DocumentStoreStatsMBean)
* Document node store blob garbage collection (BlobGCMBean)
* Document node store revision garbage collection (RevisionGCMBean)
* Document node store revision garbage collection statistics (RevisionGCStatsMBean)
* BundlingConfigObserver (BackgroundObserverMBean)

h3. Summary

The "common" set of the registered MBeans between implementations is as follows: CacheStatsMBean,
RevisionGCMBean, BlobGCMBean, CheckpointMBean.

*CacheStatsMBean*
Composite node store doesn't have any cache, so there's no need to create stats.

*RevisionGCMBean, BlobGCMBean*
Composite node store doesn't write any data/blobs on its own, so these MBeans shouldn't be
required as well. The GC mbeans for the underlying node store are available normally in the
composite setup.

*CheckpointMBean*
It's available for the Composite Node Store as well: CompositeCheckpointMBean.

Other than that, each implementation provides a specific management (DocumentNodeStoreMBean)
and stats (DocumentStoreStatsMBean, FileStoreStatsMBean) MBeans. It may make sense to gather
and expose internal composite node store stats. There are no management operations that can
be exposed. Created OAK-6675 to cover this.


was (Author: tomek.rekawek):
I've analyzed the MBeans registered by the DocumentNodeStoreService and SegmentNodeStoreService:
h3. SegmentNodeStoreService
h4. CacheStatsMBean:

* Segment Cache
* String Cache
* Template Cache
* String deduplication cache stats
* Template deduplication cache stats
* Node deduplication cache stats

h4. Maintenance MBeans:

* Segment node store revision garbage collection (SegmentRevisionGC)
* Revision garbage collection (RevisionGCMBean)
* FileStore statistics (FileStoreStatsMBean)
* Segment node store checkpoint management (CheckpointMBean, for role=null)
* Segment node store blob garbage collection (BlobGCMBean, for role=null)
* Segment node store backup/restore (FileStoreBackupRestoreMBean)
* SegmentNodeStore statistics (SegmentNodeStoreStatsMBean)

h3. DocumentNodeStoreService registers:

h4. CacheStatsMBean:

* Document-NodeState
* Document-NodeChildren
* many diff cache stats
* many DocumentStore cache stats
* BlobStore-MemCache
* PersistentCache.NodeCache.* (PersistentCacheStatsMBean)

h4. Maintenance MBeans:

* Document node store checkpoint management (CheckpointMBean)
* Document node store management (DocumentNodeStoreMBean)
* DocumentStore Statistics (DocumentStoreStatsMBean)
* Document node store blob garbage collection (BlobGCMBean)
* Document node store revision garbage collection (RevisionGCMBean)
* Document node store revision garbage collection statistics (RevisionGCStatsMBean)
* BundlingConfigObserver (BackgroundObserverMBean)

h3. Summary

The "common" set of the registered MBeans between implementations is as follows: CacheStatsMBean,
RevisionGCMBean, BlobGCMBean, CheckpointMBean.

*CacheStatsMBean*
Composite node store doesn't have any cache, so there's no need to create stats.

*RevisionGCMBean, BlobGCMBean*
Composite node store doesn't write any data/blobs on its own, so these MBeans shouldn't be
required as well. The GC mbeans for the underlying node store are available normally in the
composite setup.

*CheckpointMBean*
It's available for the Composite Node Store as well: CompositeCheckpointMBean.

Other than that, each implementation provides a specific management (DocumentNodeStoreMBean)
and stats (DocumentStoreStatsMBean, FileStoreStatsMBean) MBeans. It may make sense to gather
and expose internal composite node store stats. There are no management operations that can
be exposed.

> Review MBean interactions in a composite setup
> ----------------------------------------------
>
>                 Key: OAK-6582
>                 URL: https://issues.apache.org/jira/browse/OAK-6582
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: composite
>            Reporter: Robert Munteanu
>            Assignee: Tomek Rękawek
>             Fix For: 1.8, 1.7.8
>
>
> We should validate how the MBeans currently behave in a composite setup, whether any
unwelcome interactions arise due to that, and also see if we need to add/change MBeans.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message