Open juliobetta opened 6 years ago
I've solved this issue by removing ?limit=0&descending=true
from the line below.
The timeout was happening because the last_seq
returned from this method was always different from update_seq
returned by <couchd_url>/<database_name>
. I don't know the side effects of this change, so I didn't send a PR. Maybe you have a better solutions for this...
Now I know the side effects... It degrades performance on large databases because it needs to load the entire _charges
to get last_seq
... 😩
sorry for not noticing this earlier. the update_seq strings aren't easily compared but couchdb-lucene should be building incrementally, it doesn't start from 0 each time. Initial search index build can take time, though.
I'm using CouchDB 2.0, and I'm calling the search directly from couchdb-lucene url.
The timeout happens after I synchronize a local database (PouchDB) with the server.
But it works when I run the
info
url.I've made an experience replicating the database in the server, and the issue is gone. I'm trying to understand why the timeout happens only after a synchronization... 🤔