I use the shingle filter to help with the “one word or two” problem. Is it
“baby sitter” or “babysitter”? With the shingle filter, searches for
“babysitter” will work for content with “baby sitter”, but not the other way
around.
If you can identify a list of the one/two-word compounds that are
Hi everyone,
I was thinking of using the Shingle Filter to help solve an issue I'm
facing. I can see this working in the analysis panel in the Solr admin, but
not when I make my queries.
I find out it's because of the query parser splitting up the tokens on
white space before passing them along.
bq: "I will try some traces when I'm not under stress test myself"
Been there, done that, got the t-shirt ;).
19 seconds is, indeed, worrying. How much memory are you allocating to
the JVM? I'm just skimming, but I've seen situations where Solr runs
very close to the limit of your heap and the GC
Getting rid of
group.truncate=true
group.facet=true
group=true
group.field=edition
group.limit=30
group.ngroups=true
group.format=grouped
makes the solr behave again under the normal load but of course the
results are a bit messed up with a kind of duplicates (the point of
grouping is call
On 3/3/2017 11:28 PM, Daniel Miller wrote:
> What I think I want is create a single collection, with a
> shard/replica/core per user. Or maybe I'm wanting a separate
> collection per user - which would again mean a single
> shard/replica/core. But it seems like each shard/replica/core is a
> sepa
Hi,
thanks for the quick response.
We have meanwhile tried to remove the group.facet=true from the set of
parameters and couldn't reproduce the problem using the same stress
test, so I think 80% chance this is the root cause.
We have tried solr 6.4.1, same problem occurs.
There is only a very few s
The "Unable to write response, client closed connection or we are
shutting down" bits mean you're timing out. Or maybe something much
more serious. You can up the timeouts, but that's not particularly
useful since the response is so long anyway.
Before jumping to conclusions, I'd _really_ recommen
I’m using guzzle 3 for HTTP (it’s old but it’s the only one that works in 5.3)
and the documentation says that use persistent connection (but you know … is
PHP, weird things happen).
Maybe I need to dump data to disk an use Java to post it ...
--
/Yago Riveiro
On 4 Mar 2017 16:50 +, Walte
PHP uses the curl library for HTTP. It is a bit of a mess. It opens a new
connection for every request.
I would not try to pool client connections with PHP. PHP starts over with a new
environment for each page, so that will be very hard to manage.
I would suggest running haproxy or something si
Hi,
I'm in a bit of a crisis here. Trying to deploy a new search on an
ecommerce website which has been tested (but not stress tested). The
core has been running for years without any performance problems but we
have now changed two things:
1) started using group.facet=true in a rather complicate
The weird thing is that the lsof command shows that connections are made
between 2 solr instances and not from the origin of new income data ...
--
/Yago Riveiro
On 4 Mar 2017 10:32 +, Mikhail Khludnev , wrote:
> I hardly can comment regarding PHP. But if you call curl as an external
> prog
I hardly can comment regarding PHP. But if you call curl as an external
program it.s a dead end. However, giving
http://stackoverflow.com/questions/972925/persistent-keepalive-http-with-the-php-curl-library
you can reuse a 'context' across curl library calls and make sure that's
keep-alive pool is
Hi Mikhail,
I’m not using SSL, and the way I call Solr is through a php script that use Curl
--
/Yago Riveiro
On 4 Mar 2017 08:54 +, Mikhail Khludnev , wrote:
> Hello, Yago.
> It usually happens when client doesn't reuse http connections. How do you
> call Solr? Is there SSL?
>
> 04 марта 2
Hello, Yago.
It usually happens when client doesn't reuse http connections. How do you
call Solr? Is there SSL?
04 марта 2017 г. 3:33 пользователь "Yago Riveiro"
написал:
> Hello,
>
> I have this log in my dmesg: possible SYN flooding on port 8983. Sending
> cookies.
>
> The Solr instance (6.3.0
14 matches
Mail list logo
