Hi, using the Full Text Search we are currently running into an “LCB_HTTP_ERROR” with code 59. Searching the logs makes us think it is a memory issue: “2019-03-04T10:06:06.501+01:00 [INFO] rest: error code: 429, msg: rest_index: Query, indexName: ibe, err: query request rejected\n”, “2019-03-04…

The issue as you noted here is the huge memory requirement for running the incoming queries. If you can afford more RAM/ FTS quota, that is one way to buy some short term relief to the problem. Reducing the amount of data delivered in a response for example. There are multiple fields we don’t ac…

Currently there is no way to do this. Thanks that is what I wanted to know. Looking at the high memory estimate for the query (may be too many concurrent/slow queries?) We managed to improve the performance and amount of queries are not running into the issue anymore. Thank you!

LCB_HTTP_ERROR memory optimization

Full Text Search

avsej March 4, 2019, 11:16am 2

It seems like this is a server issue. @keshav_m, could you take a look?

Topic		Replies	Views
Full text search total_hits wrong by changing from Full Text Search	6	1604	June 26, 2020
Full Text Search Utilization 100% with no Indexes Couchbase Server fts	3	904	December 16, 2022
Couchbase Full Text Search Crashes Full Text Search	9	874	June 12, 2023
Limit 20 MB of Response of Query FTS N1QL and CURL Full Text Search n1ql	11	1558	June 25, 2021
Full Text Search LIMIT using JAVA SDK Full Text Search java	10	3409	October 11, 2019

LCB_HTTP_ERROR memory optimization

Related topics