You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Andrzej Bialecki (JIRA)" <ji...@apache.org> on 2017/08/07 14:25:00 UTC
[jira] [Updated] (SOLR-11061) Add a spins metric for all directory
paths
[ https://issues.apache.org/jira/browse/SOLR-11061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrzej Bialecki updated SOLR-11061:
-------------------------------------
Attachment: SOLR-11061.patch
This patch exposes {{CONTAINER.fs.spins}}, {{CONTAINER.fs.coreRoot.spins}} and per-core {{CORE.fs.dataDir.spins}}.
> Add a spins metric for all directory paths
> ------------------------------------------
>
> Key: SOLR-11061
> URL: https://issues.apache.org/jira/browse/SOLR-11061
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: metrics
> Reporter: Shalin Shekhar Mangar
> Assignee: Andrzej Bialecki
> Fix For: 7.1
>
> Attachments: SOLR-11061.patch
>
>
> See org.apache.lucene.util.IOUtils.spins. It currently only works for linux and is used by ConcurrentMergeScheduler to set defaults for maxThreadCount and maxMergeCount.
> We should expose this as a metric for solr.data.home and each core's data dir. One thing to note is that the CMS overrides the value detected by the spins method using {{lucene.cms.override_spins}} system property. This property is supposed to be for tests but if it is set then the metrics API should also take that into account.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org