bq: In yesterday's test run I actually had only one node
I think it's still the same issue. The update happens too
fast for the core reload. Don't know that for sure mind
you...
A cheap solution would be to wait a bit before sending
the update. Clumsy but maybe good enough for now?
Or put in som
Thanks, I knew I had seen a bug like this somewhere but could not find
it yesterday.
In yesterday's test run I actually had only one node and still got this
problem. So I'll keep the collection reload until switching to 6.1 then.
On 19/04/16 01:51, Erick Erickson wrote:
> The key here is you say
The key here is you say "sometimes". It takes a while for the reload
operation to propagate to _all_ the replicas that makeup your
collection. My bet is that by immediately indexing after changing the
data, your updates are getting to a core that hasn't reloaded yet.
That said, https://issues.apac
