[
https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189802#comment-14189802
]
Forest Soup edited comment on SOLR-6675 at 10/30/14 8:33 AM:
-------------------------------------------------------------
The callstack.png file in the attachment is the call stack of the long blocking
thread which is doing statistics calculation.
was (Author: forest_soup):
The call stack of the long blocking thread which is doing statistics
calculation.
> Solr webapp deployment is very slow with <jmx/> in solrconfig.xml
> -----------------------------------------------------------------
>
> Key: SOLR-6675
> URL: https://issues.apache.org/jira/browse/SOLR-6675
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.7
> Environment: Linux Redhat 64bit
> Reporter: Forest Soup
> Priority: Critical
> Labels: performance
> Attachments: callstack.png
>
>
> We have a SolrCloud with Solr version 4.7 with Tomcat 7. And our solr
> index(cores) are big(50~100G) each core.
> When we start up tomcat, the solr webapp deployment is very slow. From
> tomcat's catalina log, every time it takes about 10 minutes to get deployed.
> After we analyzing java core dump, we notice it's because the loading process
> cannot finish until the MBean calculation for large index is done.
>
> So we tried to remove the <jmx/> from solrconfig.xml, after that, the loading
> of solr webapp only take about 1 minute. So we can sure the MBean calculation
> for large index is the root cause.
> Could you please point me if there is any async way to do statistic
> monitoring without <jmx/> in solrconfig.xml, or let it do calculation after
> the deployment? Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
