stack outputs taken when the query was executing are
>available at http://pastebin.com/eJrEy2Wb
>
>Any suggestions would be appreciated. Or would it make sense to just
>file a JIRA issue?
>
>--Ere
>
>3.3.2015, 0.48, Matt Hilt kirjoitti:
>> Short form:
>> While test
Short form:
While testing Solr 5.0.0 within our staging environment, I noticed that
highlight enabled queries are much slower than I saw with 4.10. Are there any
obvious reasons why this might be the case? As far as I can tell, nothing has
changed with the default highlight search component or i
If you are issuing writes to shard non-leaders, then there is a large overhead
for the eventual redirect to the leader. I noticed a 3-5 times performance
increase by making my write client leader aware.
On Oct 30, 2014, at 2:56 PM, Ian Rose wrote:
>>
>> If you want to increase QPS, you shoul
rect node in the
> cloud (which is what we ended up using through JNI which was
> "interesting"), but if you are using HTTP to index, that's something your
> application has to take care of.
>
> On 28 October 2014 19:29, Matt Hilt wrote:
>
>> I have three e
I have three equal machines each running solr cloud (4.8). I have multiple
collections that are replicated but not sharded. I also have document
generation processes running on these nodes which involves querying the
collection ~5 times per document generated.
Node 1 has a replica of collection