AtoM qa/2.5 and Elasticsearch 5 - Error when rebuilding index: "Limit of total fields  in index [atom] has been exceeded"
|Assignee:||Nick Wilkinson||% Done:|
|Category:||Search / Browse|
|Target version:||Release 2.5.0|
|Google Code Legacy ID:||Tested version:||2.5|
Working on https://projects.artefactual.com/issues/12221 we have found that the default seeting for "index.mapping.total_fields.limit" (2000) on the ansible-atom role is inssuficient.
Counting the fields in an imprecise way, it seems that this value would be higher than 2000 and lower than 3000:
artefactual@bis-test:~$ curl -s -XGET localhost:9200/atom/_mapping?pretty | grep type | wc -l 2894
So this default value I think should be changed to a higher value:
#6 Updated by José Raddaoui Marín 11 months ago
- Status changed from New to In progress
I think this issue comes from:
And maybe another ones where we're adding new fields to the Elasticsearch index. I'll increase the limit to 3000 for now, but we should look for a better solution where you don't have to be that careful each time you make changes to the index, maybe looking for the exact fields on index creation and updating that value.
#8 Updated by José Raddaoui Marín 11 months ago
- Status changed from In progress to Code Review
- Assignee changed from José Raddaoui Marín to Nick Wilkinson
ansible-atom PR: https://github.com/artefactual-labs/ansible-atom/pull/25
No PR is needed in deploy-pub as it's using the default from ansible-atom.