Thanks for the help -- after fortuitously looking at a separate thread:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201403.mbox/%3CCAJYe0M4qNKzqT4gB-qib0T6%3DY1KYr7vKcNEYDHWH1MnMoCLtYw%40mail.gmail.com%3E
I upgraded to 7u25 and all is well!
On a separate note, you'd mentioned DocVa
On 3/25/2014 4:06 PM, harish.agarwal wrote:
I'm having a very similar issue to this currently on 4.6.0 (large
java.lang.ref.Finalizer usage, many open file handles to long gone files) --
were you able to make any progress diagnosing this issue?
A few questions:
Are you using any contrib or thi
I'm having a very similar issue to this currently on 4.6.0 (large
java.lang.ref.Finalizer usage, many open file handles to long gone files) --
were you able to make any progress diagnosing this issue?
--
View this message in context:
http://lucene.472066.n3.nabble.com/leaks-in-solr-tp3992047p41
Just in case, if someone else is stomping on to the same kind of issue,
check the tomcat webapps directory and try deploying it after cleaning it
out..
I had a version without subQueries.get(i).close(); deployed earlier and
then added a new version with subQueries.get(i).close(); But the tomca
subQueries.get(i).close() is nothing but pulling the refrence from the
vector and closing it. So yes. it wouldnt throw exception.
vector subQueries
Please let me know if you need any more information
On Fri, Jul 27, 2012 at 10:14 PM, Karthick Duraisamy Soundararaj <
karthick.soundara...@gmail.co
SimpleOrderedMap commonRequestParams; //This holds the common
request params.
Vector> subQueryRequestParams; // This holds the
request params of sub Queries
I use the above to create multiple localQueryRequests. To add a little more
information, I create new ResponseBuilder for each request
I al
First no. Because i do the following
for(i=0;i wrote:
> A finally clause can throw exceptions. Can this throw an exception?
> subQueries.get(i).close();
>
> If so, each close() call should be in a try-catch block.
>
> On Fri, Jul 27, 2012 at 5:28 PM, Karthick Duraisamy Soundararaj
>
A finally clause can throw exceptions. Can this throw an exception?
subQueries.get(i).close();
If so, each close() call should be in a try-catch block.
On Fri, Jul 27, 2012 at 5:28 PM, Karthick Duraisamy Soundararaj
wrote:
> Hello all,
> While running in my eclipse and run a set of
Just to clarify, the leak happens everytime a new searcher is opened.
On Fri, Jul 27, 2012 at 8:28 PM, Karthick Duraisamy Soundararaj <
karthick.soundara...@gmail.com> wrote:
> Hello all,
> While running in my eclipse and run a set of queries, this
> works fine, but when I run it in t
Hello all,
While running in my eclipse and run a set of queries, this
works fine, but when I run it in test production server, the searchers are
leaked. Any hint would be appreciated. I have not used CoreContainer.
Considering that the SearchHandler is running fine, I am not able to th
I have tons of these open.
searcherName : Searcher@24be0446 main
caching : true
numDocs : 1331167
maxDoc : 1338549
reader : SolrIndexReader{this=5585c0de,r=ReadOnlyDirectoryReader@5585c0de
,refCnt=1,segments=18}
readerDir : org.apache.lucene.store.NIOFSDirectory@
/usr/local/solr/highlander/data/...
in my case, I see only 1 searcher, no field cache - still Old Gen is almost
full at 22 GB
Does it have to do with index or some other configuration
-Saroj
On Thu, Jul 26, 2012 at 7:41 PM, Lance Norskog wrote:
> What does the "Statistics" page in the Solr admin say? There might be
> several "se
What does the "Statistics" page in the Solr admin say? There might be
several "searchers" open: org.apache.solr.search.SolrIndexSearcher
Each searcher holds open different generations of the index. If
obsolete index files are held open, it may be old searchers. How big
are the caches? How long doe
Mark,
We use solr 3.6.0 on freebsd 9. Over a period of time, it
accumulates lots of space!
On Thu, Jul 26, 2012 at 8:47 PM, roz dev wrote:
> Thanks Mark.
>
> We are never calling commit or optimize with openSearcher=false.
>
> As per logs, this is what is happening
>
> openSearcher=true,
Thanks Mark.
We are never calling commit or optimize with openSearcher=false.
As per logs, this is what is happening
openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false}
--
But, We are going to use 4.0 Alpha and see if that helps.
-Saroj
On Thu, Jul 26, 2012 at
I'd take a look at this issue: https://issues.apache.org/jira/browse/SOLR-3392
Fixed late April.
On Jul 26, 2012, at 7:41 PM, roz dev wrote:
> it was from 4/11/12
>
> -Saroj
>
> On Thu, Jul 26, 2012 at 4:21 PM, Mark Miller wrote:
>
>>
>> On Jul 26, 2012, at 3:18 PM, roz dev wrote:
>>
>>>
it was from 4/11/12
-Saroj
On Thu, Jul 26, 2012 at 4:21 PM, Mark Miller wrote:
>
> On Jul 26, 2012, at 3:18 PM, roz dev wrote:
>
> > Hi Guys
> >
> > I am also seeing this problem.
> >
> > I am using SOLR 4 from Trunk and seeing this issue repeat every day.
> >
> > Any inputs about how to resol
On Jul 26, 2012, at 3:18 PM, roz dev wrote:
> Hi Guys
>
> I am also seeing this problem.
>
> I am using SOLR 4 from Trunk and seeing this issue repeat every day.
>
> Any inputs about how to resolve this would be great
>
> -Saroj
Trunk from what date?
- Mark
Hi Guys
I am also seeing this problem.
I am using SOLR 4 from Trunk and seeing this issue repeat every day.
Any inputs about how to resolve this would be great
-Saroj
On Thu, Jul 26, 2012 at 8:33 AM, Karthick Duraisamy Soundararaj <
karthick.soundara...@gmail.com> wrote:
> Did you find any m
Did you find any more clues? I have this problem in my machines as well..
On Fri, Jun 29, 2012 at 6:04 AM, Bernd Fehling <
bernd.fehl...@uni-bielefeld.de> wrote:
> Hi list,
>
> while monitoring my solr 3.6.1 installation I recognized an increase of
> memory usage
> in OldGen JVM heap on my slave.
20 matches
Mail list logo
