Hi Robert, No, you're right, this was on a lone BigCouch test node, I'll bring up a full cluster and test again. I'm assuming I have to install and configure couchdb-lucene identically on all nodes?
Martin On 26 Apr 2012, at 22:39, Robert Newson wrote: > I can reproduce it. You have not brought up a full cluster, right? > Local docs don't have quorum, so the attempt to make _local/lucene > gives a 202 but the subsequent GET is a 404. couchdb-lucene doesn't > expect this (because it's nuts) and so you get an NPE when the uuid > is null when it 'cannot' be. > > Bringing up the full cluster and I can get search results against > bigcouch 0.4. I also fixed a bug when resuming from a checkpoint. > > B. > > On 26 April 2012 21:03, Martin Hewitt <[email protected]> wrote: >> Robert, >> >> If it's any use, I've put the consolidated BigCouch (log level = debug) and >> couchdb-lucene output here: >> >> https://gist.github.com/2502614 >> >> Martin >> >> >> On 26 Apr 2012, at 19:04, Martin Hewitt wrote: >> >>> Hi Robert, >>> >>> I've cleaned back, re-cloned and re-mvn'd, and I now get the following >>> error when loading a view: >>> >>> 2012-04-25 20:44:31,321 WARN [db1] Exiting after init() raised exception. >>> java.lang.NullPointerException >>> at >>> com.github.rnewson.couchdb.lucene.DatabaseIndexer.uuidDir(DatabaseIndexer.java:223) >>> at >>> com.github.rnewson.couchdb.lucene.DatabaseIndexer.viewDir(DatabaseIndexer.java:228) >>> at >>> com.github.rnewson.couchdb.lucene.DatabaseIndexer.viewDir(DatabaseIndexer.java:862) >>> at >>> com.github.rnewson.couchdb.lucene.DatabaseIndexer.init(DatabaseIndexer.java:805) >>> at >>> com.github.rnewson.couchdb.lucene.DatabaseIndexer.run(DatabaseIndexer.java:462) >>> at java.lang.Thread.run(Thread.java:662) >>> >>> Martin >>> >>> >>> On 26 Apr 2012, at 17:40, Robert Newson wrote: >>> >>>> Point 2 is fixed. >>>> >>>> On 26 April 2012 17:08, Robert Newson <[email protected]> wrote: >>>>> A few things are happening here; >>>>> >>>>> 1) URL dispatching on the front port (5984) is done in code, not the >>>>> configuration file. >>>>> 2) couchdb-lucene doesn't yet understand the new BigCouch 0.4 update >>>>> sequence format (I will have a word with the author). >>>>> >>>>> B. >>>>> >>>>> On 26 April 2012 16:38, Martin Hewitt <[email protected]> wrote: >>>>>> Hi all, >>>>>> >>>>>> I've configured a three-node BigCouch cluster and am working on bringing >>>>>> up couchdb-lucene as part of it. >>>>>> >>>>>> I've installed, unpacked and started couchdb-lucene, and have added the >>>>>> requisite lines into default.ini. >>>>>> >>>>>> The first thing that struck me was that I could only access it on the >>>>>> backedn (...:5986) port rather than the primary (...:5984) port, but I >>>>>> figured I could deal with that, for now. >>>>>> >>>>>> However, once I query a database view, I get the following error: >>>>>> >>>>>> 2012-04-25 19:41:56,352 WARN [db1] Exiting after init() raised exception. >>>>>> java.lang.IllegalArgumentException: >>>>>> [79521,"g1AAAAGbeJzLYWBg4MhgTmEQT8pMT84vTc5wMDQ30jM00zO0BGJjgxygAqZEhiT5____ZyUxMKi1EVSdpAAkk-yhGtRdCWtwAGmIh9lwi7CGBJCGepgN0gQ15LEASYYGIAXUMx-syYlITQsgmvaDneZDpKYDEE33wZpOE6npAUQTJBA6sgABPG9K"] >>>>>> not recognized. >>>>>> at >>>>>> com.github.rnewson.couchdb.lucene.couchdb.UpdateSequence.parseUpdateSequence(UpdateSequence.java:183) >>>>>> at >>>>>> com.github.rnewson.couchdb.lucene.couchdb.DatabaseInfo.getUpdateSequence(DatabaseInfo.java:15) >>>>>> at >>>>>> com.github.rnewson.couchdb.lucene.DatabaseIndexer.init(DatabaseIndexer.java:794) >>>>>> at >>>>>> com.github.rnewson.couchdb.lucene.DatabaseIndexer.run(DatabaseIndexer.java:462) >>>>>> at java.lang.Thread.run(Thread.java:662) >>>>>> >>>>>> If I load ...:5986/_fti/ I get: >>>>>> >>>>>> { >>>>>> • couchdb-lucene: "Welcome", >>>>>> • version: "0.9.0-SNAPSHOT" >>>>>> } >>>>>> >>>>>> I've tried adding the couchdb-lucene config as: >>>>>> >>>>>> [chttpd_global_handlers] >>>>>> _fti = {couch_httpd_proxy, handle_proxy_req, <<"http://127.0.0.1:5985";>>} >>>>>> >>>>>> in an effort to get it to use the frontend port, but no dice. >>>>>> >>>>>> I currently have: >>>>>> >>>>>> [httpd_global_handlers] >>>>>> _fti = {couch_httpd_proxy, handle_proxy_req, <<"http://127.0.0.1:5985";>>} >>>>>> >>>>>> In my /opt/bigcouch/etc/default.ini file, and I'm using the example >>>>>> design doc from the README.md, with fields adjusted to match my documents >>>>>> >>>>>> I'm using: >>>>>> >>>>>> { >>>>>> • couchdb: "Welcome", >>>>>> • version: "1.1.1", >>>>>> • bigcouch: "0.4.0" >>>>>> } >>>>>> >>>>>> On CentOS 6.2. >>>>>> >>>>>> Any ideas what could be going on? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Martin >>> >>
