What I've noticed is after my cluster (0.19.12) has been running for a few
days, trying to create a brand new index fails with an index already exists
exception. This is a brand new index, with a different, unique name. The
"type" is the same. So I might have:
index_a, type book mapping
index_b, type book mapping
then I try to create index_c, type book mapping, and get an index already
exists exception. Using the "head" plugin, I see the index gets created,
but it exists in a funky state. The primary seems OK, but the replica is
During this time, "head" reports the cluster as red. But queries against
existing indexes seem OK.
I manually delete the bad index_c then restart the cluster. Now my code can
create index_c. A few minutes later, it can also create index_d.
Only thing that seems consistent is that the cluster
- has been running for at least a few days. It's like after a few days the
cluster has some issues?
- restarting the cluster solves the issue
Obviously I don't want to restart the cluster because I'm trying to
automatically create these indexes....
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.