Hi Shawn, Erik
> updates should slow down but not deadlock.
The net effect is the same. As the CLOSE_WAITs increase, jvm ultimately
stops accepting new socket requests, at which point `kill ` is the
only option.
This means if replication handler is invoked which sets the deletion policy,
the th
Thanks Erick!
On Sat, Feb 10, 2018 at 11:37 PM, Erick Erickson
wrote:
> "I also see some segment merges before the hard-commit executes, which
> make me think that flush converts the in-memory data-structures into
> Lucene"
>
> That's my understanding. Essentially each flush creates a new segmen
Hi Dominique,
Looks like it’s a bug, not sure where exactly though. Can you please create a
JIRA?
I can see the same behavior on master too, not just on the
releases/lucene-solr/6.6.2 tag.
One interesting thing I found is that if I remove the stop filter from the
query analyzer, I get the fo
"I also see some segment merges before the hard-commit executes, which
make me think that flush converts the in-memory data-structures into
Lucene"
That's my understanding. Essentially each flush creates a new segment
that gets merged sometime.
"How is a flushed-but-not-committed segment differen
I really have no idea how that would work. If you don't copy the index
somewhere, you simply can't restore it. If you're thinking about
selectively copying index files out then back in, you'll have to
somehow lock it at point X until your delta-copy is done.
"read the snapshot's XML description an
In general, trying to impose a strict ordering by this kind of
boosting is a losing proposition. Any change to the underlying index
will alter the term and doc stats and your particular use-case won't
work at some point.
So I'd just go with a "constant score boost", see:
https://lucene.apache.org/
If you flood the system with updates, eventually you run out of merge
threads and then updates block until the merge is done. It's may be
that at this point you get into some deadlocked state, updates should
slow down but not deadlock.
How are you updating? Are you stringing together a zillion cli
On 2/9/2018 4:00 PM, Randall Chamberlin wrote:
I am experiencing this too. For me the "solr" user is running "fs-manager"
from with the directory "/var/tmp/.X1M-Unix. There is a "config.json",
"out.log" and "xmrig.log" file present. The json looks like this:
{
"algo": "cryptonight",
On 2/9/2018 8:20 PM, mmb1234 wrote:
Ran /solr/58f449cec94a2c75-core-248/admin/luke at 7:05pm PST
It showed "lastModified: 2018-02-10T02:25:08.231Z" indicating commit blocked
for about 41 mins.
Hard commit is set as 10secs in solrconfig.xml
Other cores are also now blocked.
https://jstack.revie
Hi,
More info.
When I test the analisys for the field type the synonyms are correctly
expanded for both expressions
om maillot
maillot om
olympique de marseille maillot
maillot olympique de marseille
resulting outputs always include the following terms (obvioulsly not always
in the same order)
10 matches
Mail list logo
