You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2015/03/05 17:00:42 UTC
[jira] [Resolved] (SOLR-7194) solrCloud LoadRunner Test
[ https://issues.apache.org/jira/browse/SOLR-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson resolved SOLR-7194.
----------------------------------
Resolution: Invalid
Please raise issues like this on the user's list rather than JIRAs, and if
the consensus is that it's really a code problem as opposed to
usage, _then_ raise a JIRA.
See "Mailing lists" here.
We can re-open this if it really turns out to be something we need to change code to address.
> solrCloud LoadRunner Test
> -------------------------
>
> Key: SOLR-7194
> URL: https://issues.apache.org/jira/browse/SOLR-7194
> Project: Solr
> Issue Type: New Feature
> Components: clients - java, search, Tests
> Affects Versions: 4.6.1
> Environment: three shard,two replications;two computer;every computer:eight cores;12G memory
> Reporter: chengyunyun
> Priority: Blocker
>
> loadRunner Test Environment:
> 3 million datas;
> 500 user;
> in search client,SolrServer.query(SolrQuery query) methods need much time;even 30s;but in every solr shard,need only 30ms;
> search client and solr are in tomcat server.Are CPU and memory resulting in these problems? or others?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org