Marty Schoch
Marty Schoch
Support for this is at the goforestdb level is now under review in gerrit: http://review.couchbase.org/#/c/57242/
This is partially done, the request: ``` curl -H "Content-Type: application/json" -XPOST http://localhost:9200/api/index/bs/query -d '{"query":{"match": "water"}, "size":1}' ``` Now produces the result: ``` { "request": { "query": { "match": "water",...
The goforestdb level support has been added as a part of this review: http://review.couchbase.org/#/c/57242
Seems like the exponential backoff function in cbdatasource is the most likely place. Still digging, any thoughts @steveyen ?
While it was repeatable for a while... as I added code to try and track it down, it has now stopped happening...
Also, I'm not entirely sure cbft is to blame. It seems like it could be anything using go-couchbase (or a fork of go-couchbase)
I have looked into the odd User-Agent. That is what Go sends by default. It does NOT correspond to the Go version. Regarding these messages, this is ns_server logging the...
I have separately opened up #161 because cbft messages don't end up anywhere.
OK, I've added a line "refreshing cluster" and confirmed this is where this happening. Its easiest to repeat when I create index, let it finish, kill all servers. Wait 1...
I just checked, in the most recent version of this, the cluster was refreshed 1927 times before it stopped.