Hi,
We have some custom code that extends SearchHandler to be able to :
- do an extra request
- merge/combine the original request and the extra request results
On Solr 5.x, our code was working very well, now with Solr 6.x we
have the following issue: the number of SolrI
Hi,
The custom code we have is something like this :
public class MySearchHandlerextends SearchHandler {
@Override public void handleRequestBody(SolrQueryRequest req, SolrQueryResponse
rsp)throws Exception {
SolrIndexSearcher searcher =req.getSearcher();
try{
the past to
investigate a performance problem. But it might not help if the problem
only occurs at 165 queries per second (is that true?).
cheers -- Rick
On 2017-01-30 04:02 AM, Gerald Reinhart wrote:
Hello,
In addition to the following settings, we have tried to :
- force Jetty to
,
Gérald Reinhart
On 01/27/2017 11:22 AM, Gerald Reinhart wrote:
Hello,
We are migrating our platform
from
- Solr 5.4.1 hosted by a Tomcat
to
- Solr 5.4.1 standalone (hosted by Jetty)
=> Jetty is 15% slower than Tomcat in the same conditions.
Here are deta
Hello,
We are migrating our platform
from
- Solr 5.4.1 hosted by a Tomcat
to
- Solr 5.4.1 standalone (hosted by Jetty)
=> Jetty is 15% slower than Tomcat in the same conditions.
Here are details about the benchmarks :
Context :
- Index with 9 000 000 docume
ould in fact take longer than copying over all the index files from
leader)
On Thu, Oct 6, 2016 at 5:23 AM, Gerald Reinhart
mailto:gerald.reinh...@kelkoo.com>> wrote:
Hello everyone,
Our Solr Cloud works very well for several months without any significant
changes: the traffic to s
Hello everyone,
Our Solr Cloud works very well for several months without any significant
changes: the traffic to serve is stable, no major release deployed...
But randomly, the Solr Cloud leader puts all the replicas in recovery at the
same time for no obvious reason.
Hence, we ca
toSoftCommit nodes in the solrconfig.xml.
Set them to reasonable values. The idea is that if you commit too often,
searchers will be warmed up and thrown away. If at any point in time you
get overlapping commits, there will be several searchers sitting on the
deck.
Dmitry
On Mon, Feb 29, 2016 at 4:20 PM, G
Hi,
In short: backup on a recovering index should fail.
We are using the backup command "http:// ...
/replication?command=backup&location=/tmp" against one server of the
cluster.
Most of the time there is no issue with this command.
But in some particular case, the server can be in
Hi,
We are facing an issue during a migration from Solr4 to Solr5.
Given
- migration from solr 4.10.4 to 5.4.1
- 2 collections
- cloud with one leader and several replicas
- in solrconfig.xml: maxWarmingSearchers=1
- no code change
When collection reload using /admin/collectio
acility to remove phrase
terms. edismax has some stop word (inclusion, rather than exclusion, though)
magic with the pf2 and pf3 and stopwords parameters - maybe worth leveraging
something like how that works or maybe adding some options or pluggability to
the edismax phrase/stopword facility?
On 02/02/2016 03:20 PM, Erik Hatcher wrote:
On Feb 2, 2016, at 8:57 AM, Elodie Sannier wrote:
Hello,
We are using solr 4.10.4 and we want to update to 5.4.1.
With solr 4.10.4:
- we extend PhraseQuery with a custom class in order to remove some
terms from phrase queries with phrase slop (updat
12 matches
Mail list logo
