Couchbase elasticsearch sync issue

I've been investigating whether to use couchbase with elasticsearch.
There's an excellent bloghttp://blog.couchbase.com/couchbase-and-full-text-search-couchbase-transport-elastic-searchon how to set this up. I have one issue.
If elasticsearch is down, and you send a document to couchbase, then bring
back up elasticsearch, the document won't be indexed by elasticsearch.
I've tried flushing the index to have elasticsearch pick up the document,
but flushing doesn't seem to work. In fact, I see that only half the shards
flushed successfully.
curl -XPOST http://localhost:9200/beer-sample/_flush
{"ok":true,"_shards":{"total":10,"successful":5,"failed":0}}
I'm not sure if this is an issue as half my shards seem to be under the
name "Unassigned".
My only current solution is to restart Couchbase, but obviously I wouldn't
want to do that in production.
Am I missing something?

--

Hi Amy,

I think that's really the Q for CouchBase people. I spoke to the author of
that plugin and if I remember correctly, he said CouchBase should attempt
reindexing. So I'd check with CouchBase people.

Otis

Search Analytics - http://sematext.com/search-analytics/index.html
Performance Monitoring - http://sematext.com/spm/index.html

On Friday, October 5, 2012 9:25:36 AM UTC-4, Amy wrote:

I've been investigating whether to use couchbase with elasticsearch.
There's an excellent bloghttp://blog.couchbase.com/couchbase-and-full-text-search-couchbase-transport-elastic-searchon how to set this up. I have one issue.
If elasticsearch is down, and you send a document to couchbase, then bring
back up elasticsearch, the document won't be indexed by elasticsearch.
I've tried flushing the index to have elasticsearch pick up the document,
but flushing doesn't seem to work. In fact, I see that only half the shards
flushed successfully.
curl -XPOST http://localhost:9200/beer-sample/_flush
{"ok":true,"_shards":{"total":10,"successful":5,"failed":0}}
I'm not sure if this is an issue as half my shards seem to be under the
name "Unassigned".
My only current solution is to restart Couchbase, but obviously I wouldn't
want to do that in production.
Am I missing something?

--

Hi Amy,

Just saw this post here and wasn't sure if it was before or after our email
exchange about this. The XDCR process used to send data to the Couchbase
ElasticSearch adapter follows an exponential backoff process when retrying
connections to an ElasticSearch cluster that was down. Depending on how
long your ES cluster was down, this could cause significant delays before
those changes are propagated.

I'm still working to reproduce the scenario you described and get
clarification on the parameters of the backoff. I'll update you when I
know more.

marty

On Friday, October 5, 2012 9:25:36 AM UTC-4, Amy wrote:

I've been investigating whether to use couchbase with elasticsearch.
There's an excellent bloghttp://blog.couchbase.com/couchbase-and-full-text-search-couchbase-transport-elastic-searchon how to set this up. I have one issue.
If elasticsearch is down, and you send a document to couchbase, then bring
back up elasticsearch, the document won't be indexed by elasticsearch.
I've tried flushing the index to have elasticsearch pick up the document,
but flushing doesn't seem to work. In fact, I see that only half the shards
flushed successfully.
curl -XPOST http://localhost:9200/beer-sample/_flush
{"ok":true,"_shards":{"total":10,"successful":5,"failed":0}}
I'm not sure if this is an issue as half my shards seem to be under the
name "Unassigned".
My only current solution is to restart Couchbase, but obviously I wouldn't
want to do that in production.
Am I missing something?

--

Hi,

was any foolow up on this issue? Is it still valid or not?

Cheers,
Dany