Re: solr 5.3.0 master-slave: TWO segments after optimize

2015-10-29 Thread Andrii Berezhynskyi
Erick, they are not going away after reload. Emir, increased cpu and response time are on slaves. On all slaves. Here is a thread dump https://gist.github.com/andriiberezhynskyi/739d59cf78b043d653da (though not sure that I did it right, I used jstack -F PID). Thanks for your help!

solr 5.3.0 master-slave: TWO segments after optimize

2015-10-28 Thread Andrii Berezhynskyi
Hi all! We have master-slave configuration. Slaves are replicated on optimize. Sometimes (not always) it happens that slave has two segments after replication. I always thought that optimize is all about having only one segment in your read replica. During this time when slave has two segments we

Re: Deadlock-like behavior when new IndexWriter created

2015-08-12 Thread Andrii Berezhynskyi
Sure, Eric. Here it is Attaching to process ID 9429, please wait... Debugger attached successfully. Server compiler detected. JVM version is 25.51-b03 Deadlock Detection: No deadlocks found. Thread 9578: (state = BLOCKED) - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; informatio

Deadlock-like behavior when new IndexWriter created

2015-08-11 Thread Andrii Berezhynskyi
Hi, I have solr5.2.1 set up in master-slave configuration. Very often it happens that solr slave starts replicating (I can see it in admin panel) but it is getting stuck at 0% and never proceeds further. Usually restart of slave helps. Relevant logs from slave: INFO - 2015-08-11 07:56:00.184; o

Re: Solr 5.1 json facets: buckets are empty for TrieIntField

2015-05-15 Thread Andrii Berezhynskyi
> -Yonik > > > On Fri, May 15, 2015 at 4:04 AM, Andrii Berezhynskyi > wrote: > > I have a strange issue of facet buckets being empty for tint fields. > > I have the following schema: > > > > > omitNorms="true"/> > > > &g

Solr 5.1 json facets: buckets are empty for TrieIntField

2015-05-15 Thread Andrii Berezhynskyi
I have a strange issue of facet buckets being empty for tint fields. I have the following schema: ... Then I just import: [{ "sku": "TEST_FACET", "color": "yellow", "width": 100.23, "price": 1200 }] when I do the following faceting request: json.facet={ colors:{ter

Re: How is the most relevant document of each group chosen when group.truncate is used?

2015-05-13 Thread Andrii Berezhynskyi
ng to collapsing query. On Tue, May 12, 2015 at 6:15 PM, Andrii Berezhynskyi < andrii.berezhyns...@home24.de> wrote: > Hi all, > > When I use group.truncate and filtering I'm getting strange faceting > results. If I use just grouping without filtering: > > > group=true&

Re: How is the most relevant document of each group chosen when group.truncate is used?

2015-05-12 Thread Andrii Berezhynskyi
Forgot to mention that I'm using solr 5.0

How is the most relevant document of each group chosen when group.truncate is used?

2015-05-12 Thread Andrii Berezhynskyi
Hi all, When I use group.truncate and filtering I'm getting strange faceting results. If I use just grouping without filtering: group=true&group.field=parent_sku&group.ngroups=true&group.truncate=true&facet=true&facet.field=color, then I get: facet_fields": { "color": [ "white", 19742, 19742