You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Michael McCaffrey <mm...@ittvis.com> on 2010/03/04 01:14:40 UTC
couchdb lucene error
Something's happened with my couchdb lucene implementation and I can't
get couch to start unless I comment out the indexer in the ini file.
I'm getting java heap errors.
I've tried cleaning out my indices folder but to no avail.
Don't know what happened, it was working fine, I made a change to a
database record to test a lucene query and it hung up. Had to kill the
couch session and now it won't restart.
Any ideas?
Thanks
1> 2010-03-03 17:07:52,027 [couchdb-lucene] WARN Forcibly unlocking
locked index at startup.
[info] [<0.62.0>] 127.0.0.1 - - 'GET' /_all_dbs 200
1> [info] [<0.62.0>] 127.0.0.1 - - 'GET'
/test/_all_docs?startkey=%22_design%22&endkey=%22_desig
1> [info] [<0.62.0>] 127.0.0.1 - - 'GET' /test 200
1> [info] [<0.62.0>] 127.0.0.1 - - 'GET'
/test/_all_docs_by_seq?startkey=0&limit=250&include_doc
1> Exception in thread "main" java.lang.OutOfMemoryError: Java heap
space
[error] [<0.52.0>] OS Process died with status: 0
RE: couchdb lucene error
Posted by Michael McCaffrey <mm...@ittvis.com>.
So it seems I needed to add the -Xmx parm on the indexer line for it to start up. I set it to 256m and it starts up.
Wonder why it all of a sudden started to fail? Been running with the original config for months.
Thanks for the help
-----Original Message-----
From: Robert Newson [mailto:robert.newson@gmail.com]
Sent: Wednesday, March 03, 2010 7:58 PM
To: user@couchdb.apache.org
Subject: Re: couchdb lucene error
you may need to add -Xmx1g to your java line to make this work;
B.
On Wed, Mar 3, 2010 at 9:36 PM, km <sr...@gmail.com> wrote:
> please check if
> 1) ur dir to store indexes (indexes dir ) is properly set in the local.ini
> config file
> 2) ownership of that indexes dir set to couchdb user recursively eg: chown
> -R couchdb:couchdb <indexesdir>
> 3) permissions of that indexes dir set appropriately eg: chmod -R 0770
> <indexesdir>
> restart couchdb and check now.
>
> HTH
> Krishna
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> On Thu, Mar 4, 2010 at 9:14 AM, Michael McCaffrey <mm...@ittvis.com>wrote:
>
>> Something's happened with my couchdb lucene implementation and I can't
>> get couch to start unless I comment out the indexer in the ini file.
>>
>> I'm getting java heap errors.
>>
>> I've tried cleaning out my indices folder but to no avail.
>>
>> Don't know what happened, it was working fine, I made a change to a
>> database record to test a lucene query and it hung up. Had to kill the
>> couch session and now it won't restart.
>>
>> Any ideas?
>>
>> Thanks
>>
>>
>> 1> 2010-03-03 17:07:52,027 [couchdb-lucene] WARN Forcibly unlocking
>> locked index at startup.
>> [info] [<0.62.0>] 127.0.0.1 - - 'GET' /_all_dbs 200
>> 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET'
>> /test/_all_docs?startkey=%22_design%22&endkey=%22_desig
>> 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET' /test 200
>> 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET'
>> /test/_all_docs_by_seq?startkey=0&limit=250&include_doc
>> 1> Exception in thread "main" java.lang.OutOfMemoryError: Java heap
>> space
>> [error] [<0.52.0>] OS Process died with status: 0
>>
>>
>
Re: couchdb lucene error
Posted by Robert Newson <ro...@gmail.com>.
you may need to add -Xmx1g to your java line to make this work;
B.
On Wed, Mar 3, 2010 at 9:36 PM, km <sr...@gmail.com> wrote:
> please check if
> 1) ur dir to store indexes (indexes dir ) is properly set in the local.ini
> config file
> 2) ownership of that indexes dir set to couchdb user recursively eg: chown
> -R couchdb:couchdb <indexesdir>
> 3) permissions of that indexes dir set appropriately eg: chmod -R 0770
> <indexesdir>
> restart couchdb and check now.
>
> HTH
> Krishna
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> On Thu, Mar 4, 2010 at 9:14 AM, Michael McCaffrey <mm...@ittvis.com>wrote:
>
>> Something's happened with my couchdb lucene implementation and I can't
>> get couch to start unless I comment out the indexer in the ini file.
>>
>> I'm getting java heap errors.
>>
>> I've tried cleaning out my indices folder but to no avail.
>>
>> Don't know what happened, it was working fine, I made a change to a
>> database record to test a lucene query and it hung up. Had to kill the
>> couch session and now it won't restart.
>>
>> Any ideas?
>>
>> Thanks
>>
>>
>> 1> 2010-03-03 17:07:52,027 [couchdb-lucene] WARN Forcibly unlocking
>> locked index at startup.
>> [info] [<0.62.0>] 127.0.0.1 - - 'GET' /_all_dbs 200
>> 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET'
>> /test/_all_docs?startkey=%22_design%22&endkey=%22_desig
>> 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET' /test 200
>> 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET'
>> /test/_all_docs_by_seq?startkey=0&limit=250&include_doc
>> 1> Exception in thread "main" java.lang.OutOfMemoryError: Java heap
>> space
>> [error] [<0.52.0>] OS Process died with status: 0
>>
>>
>
Re: couchdb lucene error
Posted by km <sr...@gmail.com>.
please check if
1) ur dir to store indexes (indexes dir ) is properly set in the local.ini
config file
2) ownership of that indexes dir set to couchdb user recursively eg: chown
-R couchdb:couchdb <indexesdir>
3) permissions of that indexes dir set appropriately eg: chmod -R 0770
<indexesdir>
restart couchdb and check now.
HTH
Krishna
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Thu, Mar 4, 2010 at 9:14 AM, Michael McCaffrey <mm...@ittvis.com>wrote:
> Something's happened with my couchdb lucene implementation and I can't
> get couch to start unless I comment out the indexer in the ini file.
>
> I'm getting java heap errors.
>
> I've tried cleaning out my indices folder but to no avail.
>
> Don't know what happened, it was working fine, I made a change to a
> database record to test a lucene query and it hung up. Had to kill the
> couch session and now it won't restart.
>
> Any ideas?
>
> Thanks
>
>
> 1> 2010-03-03 17:07:52,027 [couchdb-lucene] WARN Forcibly unlocking
> locked index at startup.
> [info] [<0.62.0>] 127.0.0.1 - - 'GET' /_all_dbs 200
> 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET'
> /test/_all_docs?startkey=%22_design%22&endkey=%22_desig
> 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET' /test 200
> 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET'
> /test/_all_docs_by_seq?startkey=0&limit=250&include_doc
> 1> Exception in thread "main" java.lang.OutOfMemoryError: Java heap
> space
> [error] [<0.52.0>] OS Process died with status: 0
>
>