You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Qingdi <qi...@nextbio.com> on 2009/01/29 22:06:10 UTC
got background_merge_hit_exception during optimization
We got the following background_merge_hit_exception during optimization:
exception:
)background_merge_hit_exception__4zsgC136887658__50nfC995992__51i9C995977__52d5C995968__537yC995999__54xmC1892345__54xlC99593_into__54xn_optimize__javaioIOException_background_merge_hit_exception__4zsgC136887658__50nfC995992__51i9C995977__52d5C995968__537yC995999__54xmC1892345__54xlC99593_into__54xn_optimize__at_orgapacheluceneindexIndexWriteroptimizeIndexWriterjava2346__at_orgapacheluceneindexIndexWriteroptimizeIndexWriterjava2280__at_orgapachesolrupdateDirectUpdateHandler2commitDirectUpdateHandler2java355__at_orgapachesolrupdateprocessorRunUpdateProcessorprocessCommitRunUpdateProcessorFactoryjava77__at_orgapachesolrhandlerRequestHandlerUtilshandleCommitRequestHandlerUtilsjava104__at_orgapachesolrhandlerXmlUpdateRequestHandlerhandleRequestBodyXmlUpdateRequestHandlerjava113__at_orgapachesolrhandlerRequestHandlerBasehandleRequestRequestHandlerBasejava131__at_orgapachesolrcoreSolrCoreexecuteSolrCorejava1204__at_orgapachesolrservletSolrDispatchFilterexecuteSolrDispatchFilterjava303__at_orgapachesolrservletSolrDispatchFilterdoFilterSolrDispatchFilterjava232__at_orgmortbayjettyservletServletHandler$CachedChaindoFilterServletHandlerjava1089__at_orgmortbayjettyservletServletHandlerhandleServletHandlerjava365__at_orgmortbayjettysecuritySecurityHandlerhandleSecurityHandlerjava216__at_orgmortbayjettyservletSessionHandlerhandleSessionHandlerjava181__at_orgmortbayjettyhandlerContextHandlerhandleContextHandlerjava712__at_orgmortbayjettywebappWebAppContexthandleWebAppContextjava405__at_orgmortbayjettyhandlerContextHandlerCollectionhandleContextHandlerCollectionjava211__at_orgmortbayjettyhandlerHandlerCollectionhandleHandlerCollectionjava114__at_orgmortbayjettyhandlerHandlerWrapperhandleHandlerWrapperjava139__at_orgmortbayjettyServerhandleServerjava285__at_orgmortbayjettyHttpConnectionhandleRequestHttpConnectionjava502__a
Does anyone know what could be the cause of the exception? what should we do
to prevent this type of exception?
Some posts in the Lucene forum say the exception is usually related with
disk space issue. But there should be enough disk space in our system. Our
index size was about 56G. And before optimization, the disk had about 360G
free space.
After the above background_merge_hit_exception raised, solr kept generating
new segment files, which ate up all the CPU time and the disk space, so we
had to kill the solr server.
Thanks for your help.
Qingdi
--
View this message in context: http://www.nabble.com/got-background_merge_hit_exception-during-optimization-tp21735847p21735847.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: got background_merge_hit_exception during optimization
Posted by Otis Gospodnetic <ot...@yahoo.com>.
Hi,
I didn't look into this deeply, but you didn't say which version of Solr you are using (looks like it might be 1.3). If using a nightly build is an option, you might try that instead - Yonik updated the Lucene jars recently and that might be enough to solve this problem.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
> From: Qingdi <qi...@nextbio.com>
> To: solr-user@lucene.apache.org
> Sent: Thursday, January 29, 2009 4:06:10 PM
> Subject: got background_merge_hit_exception during optimization
>
>
> We got the following background_merge_hit_exception during optimization:
> exception:
>
)background_merge_hit_exception__4zsgC136887658__50nfC995992__51i9C995977__52d5C995968__537yC995999__54xmC1892345__54xlC99593_into__54xn_optimize__javaioIOException_background_merge_hit_exception__4zsgC136887658__50nfC995992__51i9C995977__52d5C995968__537yC995999__54xmC1892345__54xlC99593_into__54xn_optimize__at_orgapacheluceneindexIndexWriteroptimizeIndexWriterjava2346__at_orgapacheluceneindexIndexWriteroptimizeIndexWriterjava2280__at_orgapachesolrupdateDirectUpdateHandler2commitDirectUpdateHandler2java355__at_orgapachesolrupdateprocessorRunUpdateProcessorprocessCommitRunUpdateProcessorFactoryjava77__at_orgapachesolrhandlerRequestHandlerUtilshandleCommitRequestHandlerUtilsjava104__at_orgapachesolrhandlerXmlUpdateRequestHandlerhandleRequestBodyXmlUpdateRequestHandlerjava113__at_orgapachesolrhandlerRequestHandlerBasehandleRequestRequestHandlerBasejava131__at_orgapachesolrcoreSolrCoreexecuteSolrCorejava1204__at_orgapachesolrservletSolrDispatchFilterexecu
teSolrDispatchFilterjava303__at_orgapachesolrservletSolrDispatchFilterdoFilterSolrDispatchFilterjava232__at_orgmortbayjettyservletServletHandler$CachedChaindoFilterServletHandlerjava1089__at_orgmortbayjettyservletServletHandlerhandleServletHandlerjava365__at_orgmortbayjettysecuritySecurityHandlerhandleSecurityHandlerjava216__at_orgmortbayjettyservletSessionHandlerhandleSessionHandlerjava181__at_orgmortbayjettyhandlerContextHandlerhandleContextHandlerjava712__at_orgmortbayjettywebappWebAppContexthandleWebAppContextjava405__at_orgmortbayjettyhandlerContextHandlerCollectionhandleContextHandlerCollectionjava211__at_orgmortbayjettyhandlerHandlerCollectionhandleHandlerCollectionjava114__at_orgmortbayjettyhandlerHandlerWrapperhandleHandlerWrapperjava139__at_orgmortbayjettyServerhandleServerjava285__at_orgmortbayjettyHttpConnectionhandleRequestHttpConnectionjava502__a
>
> Does anyone know what could be the cause of the exception? what should we do
> to prevent this type of exception?
>
> Some posts in the Lucene forum say the exception is usually related with
> disk space issue. But there should be enough disk space in our system. Our
> index size was about 56G. And before optimization, the disk had about 360G
> free space.
>
> After the above background_merge_hit_exception raised, solr kept generating
> new segment files, which ate up all the CPU time and the disk space, so we
> had to kill the solr server.
>
> Thanks for your help.
>
> Qingdi
>
>
> --
> View this message in context:
> http://www.nabble.com/got-background_merge_hit_exception-during-optimization-tp21735847p21735847.html
> Sent from the Solr - User mailing list archive at Nabble.com.
Re: got background_merge_hit_exception during optimization
Posted by Qingdi <qi...@nextbio.com>.
We are on solr 1.3, and we use the default jetty server, which is included
in the solr 1.3 download package.
The java version is:
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_12-b04, mixed mode)
I checked the log files under logs and solr/logs, but don't see any error.
Would you please let me know how to get the stack trace from the solr logs?
Appreciate your help.
Qingdi
Yonik Seeley-2 wrote:
>
> What system and JVM was this using?
> Also, could you get the stack trace directly from the Solr logs and post
> it?
>
> -Yonik
>
> On Thu, Jan 29, 2009 at 4:06 PM, Qingdi <qi...@nextbio.com> wrote:
>>
>> We got the following background_merge_hit_exception during optimization:
>> exception:
>> )background_merge_hit_exception__4zsgC136887658__50nfC995992__51i9C995977__52d5C995968__537yC995999__54xmC1892345__54xlC99593_into__54xn_optimize__javaioIOException_background_merge_hit_exception__4zsgC136887658__50nfC995992__51i9C995977__52d5C995968__537yC995999__54xmC1892345__54xlC99593_into__54xn_optimize__at_orgapacheluceneindexIndexWriteroptimizeIndexWriterjava2346__at_orgapacheluceneindexIndexWriteroptimizeIndexWriterjava2280__at_orgapachesolrupdateDirectUpdateHandler2commitDirectUpdateHandler2java355__at_orgapachesolrupdateprocessorRunUpdateProcessorprocessCommitRunUpdateProcessorFactoryjava77__at_orgapachesolrhandlerRequestHandlerUtilshandleCommitRequestHandlerUtilsjava104__at_orgapachesolrhandlerXmlUpdateRequestHandlerhandleRequestBodyXmlUpdateRequestHandlerjava113__at_orgapachesolrhandlerRequestHandlerBasehandleRequestRequestHandlerBasejava131__at_orgapachesolrcoreSolrCoreexecuteSolrCorejava1204__at_orgapachesolrservletSolrDispatchFilterexecuteSolrDispatchFilterjava303__at_orgapachesolrservletSolrDispatchFilterdoFilterSolrDispatchFilterjava232__at_orgmortbayjettyservletServletHandler$CachedChaindoFilterServletHandlerjava1089__at_orgmortbayjettyservletServletHandlerhandleServletHandlerjava365__at_orgmortbayjettysecuritySecurityHandlerhandleSecurityHandlerjava216__at_orgmortbayjettyservletSessionHandlerhandleSessionHandlerjava181__at_orgmortbayjettyhandlerContextHandlerhandleContextHandlerjava712__at_orgmortbayjettywebappWebAppContexthandleWebAppContextjava405__at_orgmortbayjettyhandlerContextHandlerCollectionhandleContextHandlerCollectionjava211__at_orgmortbayjettyhandlerHandlerCollectionhandleHandlerCollectionjava114__at_orgmortbayjettyhandlerHandlerWrapperhandleHandlerWrapperjava139__at_orgmortbayjettyServerhandleServerjava285__at_orgmortbayjettyHttpConnectionhandleRequestHttpConnectionjava502__a
>>
>> Does anyone know what could be the cause of the exception? what should we
>> do
>> to prevent this type of exception?
>>
>> Some posts in the Lucene forum say the exception is usually related with
>> disk space issue. But there should be enough disk space in our system.
>> Our
>> index size was about 56G. And before optimization, the disk had about
>> 360G
>> free space.
>>
>> After the above background_merge_hit_exception raised, solr kept
>> generating
>> new segment files, which ate up all the CPU time and the disk space, so
>> we
>> had to kill the solr server.
>>
>> Thanks for your help.
>>
>> Qingdi
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/got-background_merge_hit_exception-during-optimization-tp21735847p21735847.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/got-background_merge_hit_exception-during-optimization-tp21735847p21751938.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: got background_merge_hit_exception during optimization
Posted by Yonik Seeley <yo...@lucidimagination.com>.
What system and JVM was this using?
Also, could you get the stack trace directly from the Solr logs and post it?
-Yonik
On Thu, Jan 29, 2009 at 4:06 PM, Qingdi <qi...@nextbio.com> wrote:
>
> We got the following background_merge_hit_exception during optimization:
> exception:
> )background_merge_hit_exception__4zsgC136887658__50nfC995992__51i9C995977__52d5C995968__537yC995999__54xmC1892345__54xlC99593_into__54xn_optimize__javaioIOException_background_merge_hit_exception__4zsgC136887658__50nfC995992__51i9C995977__52d5C995968__537yC995999__54xmC1892345__54xlC99593_into__54xn_optimize__at_orgapacheluceneindexIndexWriteroptimizeIndexWriterjava2346__at_orgapacheluceneindexIndexWriteroptimizeIndexWriterjava2280__at_orgapachesolrupdateDirectUpdateHandler2commitDirectUpdateHandler2java355__at_orgapachesolrupdateprocessorRunUpdateProcessorprocessCommitRunUpdateProcessorFactoryjava77__at_orgapachesolrhandlerRequestHandlerUtilshandleCommitRequestHandlerUtilsjava104__at_orgapachesolrhandlerXmlUpdateRequestHandlerhandleRequestBodyXmlUpdateRequestHandlerjava113__at_orgapachesolrhandlerRequestHandlerBasehandleRequestRequestHandlerBasejava131__at_orgapachesolrcoreSolrCoreexecuteSolrCorejava1204__at_orgapachesolrservletSolrDispatchFilterexecuteSolrDispatchFilterjava303__at_orgapachesolrservletSolrDispatchFilterdoFilterSolrDispatchFilterjava232__at_orgmortbayjettyservletServletHandler$CachedChaindoFilterServletHandlerjava1089__at_orgmortbayjettyservletServletHandlerhandleServletHandlerjava365__at_orgmortbayjettysecuritySecurityHandlerhandleSecurityHandlerjava216__at_orgmortbayjettyservletSessionHandlerhandleSessionHandlerjava181__at_orgmortbayjettyhandlerContextHandlerhandleContextHandlerjava712__at_orgmortbayjettywebappWebAppContexthandleWebAppContextjava405__at_orgmortbayjettyhandlerContextHandlerCollectionhandleContextHandlerCollectionjava211__at_orgmortbayjettyhandlerHandlerCollectionhandleHandlerCollectionjava114__at_orgmortbayjettyhandlerHandlerWrapperhandleHandlerWrapperjava139__at_orgmortbayjettyServerhandleServerjava285__at_orgmortbayjettyHttpConnectionhandleRequestHttpConnectionjava502__a
>
> Does anyone know what could be the cause of the exception? what should we do
> to prevent this type of exception?
>
> Some posts in the Lucene forum say the exception is usually related with
> disk space issue. But there should be enough disk space in our system. Our
> index size was about 56G. And before optimization, the disk had about 360G
> free space.
>
> After the above background_merge_hit_exception raised, solr kept generating
> new segment files, which ate up all the CPU time and the disk space, so we
> had to kill the solr server.
>
> Thanks for your help.
>
> Qingdi
>
>
> --
> View this message in context: http://www.nabble.com/got-background_merge_hit_exception-during-optimization-tp21735847p21735847.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>