-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating a duplicate mapping throws the whole cluster #39
Comments
Fixed one issue, where the proper exception was not raised (actually serialized) since you have ignoreDuplicates to false. Trying to recreate the problem you posted. |
Hopefully, its fixed now. Since the allocation of shards is async, the create/delete/create/delete cycle caused the delete api to hand in the ack phase. Can you give it a go? (note, I added a cluster health API where you can wait for the cluster to get to a certain state) |
This looks like it has been fixed |
This change will allow EC2 API to filter by tags, AZ, and instance state. In the situation where you have a large number of instances/reservations, this can be a performance boost. Note that we still do the security group filter locally due to the different strategies (all or some must match). Closes #39.
If you define some specific mapping for your file content, such as the following: ```javascript { "person": { "properties": { "file": { "type": "attachment", "path": "full", "fields": { "date": { "type": "string" } } } } } } ``` And then, if you ask back the mapping, you get: ```javascript { "person":{ "properties":{ "file":{ "type":"attachment", "path":"full", "fields":{ "file":{ "type":"string" }, "author":{ "type":"string" }, "title":{ "type":"string" }, "name":{ "type":"string" }, "date":{ "type":"date", "format":"dateOptionalTime" }, "keywords":{ "type":"string" }, "content_type":{ "type":"string" } } } } } } ``` All your settings have been overwrited by the mapper plugin. See also issue elastic#22 where the issue was found. Closes elastic#39.
It is sometimes challenging to work out the sequence of events that led to a test failure, and a contributing factor is that scheduled tasks are identified only by their scheduled time and not by any more useful identifier. This change adds simple descriptions to these tasks to help untangle things a bit.
With this commit we implement the property `pecent_completed` on the Elasticlogs bulk source to provide an informational progress indication for the challenge `index-logs-fixed-daily-volume`. Because we cannot specify a total number of iterations or a specific time-period we need to rely on feedback from the generator when all data has been ingested and thus we also need to rely on the generator to indicate progress. Relates elastic#39
With this commit we add a new ML-related challenge to our benchmarks. Closes elastic#39 Relates elastic#84
With this commit we ensure that ML-related benchmarks can be run for all release benchmarks starting with Elasticsearch 5.4.0. Relates elastic#39 Relates elastic#85
Hiya
I'm starting 3 nodes, then creating a mapping, then creating a duplicate (with ignoreDuplicate=false).
It is sufficient to throw the whole cluster out. It doesn't seem to recover.
Run this script a few times, and watch the server logs:
The text was updated successfully, but these errors were encountered: