lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Rowe <sar...@gmail.com>
Subject Re: SolrCloud constantly crashes after upgrading to Solr 4.7
Date Mon, 17 Mar 2014 16:33:05 GMT
No, only QueryComponent.mergeIds() is only called for distributed queries.

Steve

On Mar 17, 2014, at 12:18 PM, Walter Underwood <wunder@wunderwood.org> wrote:

> Does this bug happen in the non-sharded case? --wunder
> 
> On Mar 17, 2014, at 9:15 AM, Steve Rowe <sarowe@gmail.com> wrote:
> 
>> Martin, I’ve committed the SOLR-5875 fix, including to the lucene_solr_4_7 branch.
>> 
>> Any chance you could test the fix?
>> 
>> Thanks,
>> Steve
>> 
>> On Mar 17, 2014, at 11:16 AM, Steve Rowe <sarowe@gmail.com> wrote:
>> 
>>> Martin,
>>> 
>>> You’re right, a bug was introduced by SOLOR-5354.  I’ve opened an issue <https://issues.apache.org/jira/browse/SOLR-5875>
and will commit the fix shortly.  I hope to include this fix in a 4.7.1 release.
>>> 
>>> Steve
>>> 
>>> On Mar 8, 2014, at 1:32 AM, Martin de Vries <martin@downnotifier.com> wrote:
>>> 
>>>>> The memory leak seems to be in:
>>>>> org.apache.solr.handler.component.ShardFieldSortedHitQueue
>>>> 
>>>> I think our issue might be related to this one, because this change has been
introduced in 4.7 and has changes to ShardFieldSortedHitQueue:
>>>> 
>>>> https://issues.apache.org/jira/browse/SOLR-5354
>>>> 
>>>> 
>>>> Is the memory leak a bug, or should a full reindex help?
>>>> 
>>>> 
>>>> Martin
>>> 
>> 
> 
> --
> Walter Underwood
> wunder@wunderwood.org
> 
> 
> 


Mime
View raw message