Re: AlreadyClosedException on new index

2015-01-06 Thread Brian Call
combined with not protecting against this possibility. Thanks for your assistance guys! -Brian > On Jan 6, 2015, at 10:22 AM, Brian Call wrote: > > No exception at all… and that’s the crazy part. I create a new IndexWriter > and then immediately create a new SearcherManager using

Re: AlreadyClosedException on new index

2015-01-06 Thread Brian Call
index. > > > -- > Ian. > > > On Tue, Jan 6, 2015 at 5:05 PM, Brian Call > mailto:brian.c...@soterawireless.com>> wrote: >> Hi Tomoko, >> >> Thank you for your response! We’ve actually never seen this before in the >> three+ years of

Re: AlreadyClosedException on new index

2015-01-06 Thread Brian Call
ments. > > Regards, > Tomoko > > > 2015-01-06 8:32 GMT+09:00 Brian Call <mailto:brian.c...@soterawireless.com>>: > >> Hi Guys, >> >> So I’m seeing a problem in production that is very bizarre and I wanted to >> see if anyone else has encount

AlreadyClosedException on new index

2015-01-05 Thread Brian Call
closed? I’m completely baffled on this one guys… so many thanks in advance for your help! I’ll take any suggestions on a possible mitigation too if anyone thinks of any. Blessings, Brian Call Manager, Systems Software Development Work: +1 (619) 373-4840 | Cell: +1 (619) 344-1013 <h

Re: Caused by: java.lang.OutOfMemoryError: Map failed

2014-11-08 Thread Brian Call
I’ll try bumping up the per-process file max and see if that fixes it. Thanks for all your help and suggestions guys! -Brian On Nov 7, 2014, at 5:00 PM, Toke Eskildsen wrote: > Brian Call [brian.c...@soterawireless.com] wrote: >> Yep, you guys are correct, I’m supporting a sligh

Re: Caused by: java.lang.OutOfMemoryError: Map failed

2014-11-07 Thread Brian Call
Half of those indexes max out at about 1.3G, the other half will always stay very small < 5m total. We keep an index for “raw” data and another index for events and “trended” data. Possible design changes may make this number go up to 4-5G per index, but definitely no more than that. We’re ind

Re: Caused by: java.lang.OutOfMemoryError: Map failed

2014-11-07 Thread Brian Call
Yep, you guys are correct, I’m supporting a slightly older version of our product based on Lucene 3. In my previous email I forgot to mention that I also bumped up the maximum allowable file handles per process to 16k, which had been working well. Here’s the ulimit -a output from our server: co

Caused by: java.lang.OutOfMemoryError: Map failed

2014-11-07 Thread Brian Call
-process map count using cat /proc//maps | wc -l and that returned around 4k maps, well under the 65k limit. Does anyone have any ideas on what to check out next? I’m running out of things to try… Many, many thanks in advance! Blessings, Brian Call