Closed scheiblr closed 3 years ago
Thanks for the report. Off the top of my head I don't know what might cause this. I'll do some investigations with my local cluster over the weekend.
I'm unable to re-create this, but it looks like you're getting a 408 back, which is a "request timeout", so I've added a retry for this, up to 10 times.
I guess what's happening is it's taking your cluster longer to turn (at least) yellow (which means all primary shards are online) than whatever the default timeout for waiting is.
I'll a fix pushed in a bit and then I think I'll be able to make a final release!
slight change of plans. I'm just going to bump the request timeout for the cluster health request from 30s to 5m. That's the same thing as retrying up to 10 times.
This will be released in v3000.0.0 -- which is happening now.
ZomboDB version: v3000.0.0-beta1 Postgres version: 13.2 Elasticsearch version: 7.12
Problem Description: I expected the new version to treat as the old one. So basically I just updated a running software setup (es, pg & zdb). Zdb creates an index on the side of ES which remains in status red and as far as I see, does not contain any data.
Error Message (if any):
Index Definition:
The ES cluster was setup according to the ES documentation.