From d2270feecec6715d01201ad0eb009423c2301cc7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Soko=C5=82owski?= Date: Thu, 12 Oct 2023 18:56:21 +0200 Subject: [PATCH] logs.nimbus: increase total_fields.limit to 1500 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This is a special case since these logs are all custom JSON, so increasing this is fine for now. I can't control what they put in logs. https://discuss.elastic.co/t/approaches-to-deal-with-limit-of-total-fields-1000-in-index-has-been-exceeded/241039 Signed-off-by: Jakub SokoĊ‚owski --- ansible/group_vars/logs.nimbus.yml | 2 ++ ansible/requirements.yml | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/ansible/group_vars/logs.nimbus.yml b/ansible/group_vars/logs.nimbus.yml index 53832e6..c43668c 100644 --- a/ansible/group_vars/logs.nimbus.yml +++ b/ansible/group_vars/logs.nimbus.yml @@ -35,6 +35,8 @@ es_master_nodes: | es_number_of_shards: 3 # Since Nimbus logs are low-value we don't need replicas. es_number_of_replicas: 0 +# Bump due to large number of fields in JSON logs. +es_mapping_total_fields_limit: 1500 # JVM Memory settings es_jvm_g1gc_enabled: true diff --git a/ansible/requirements.yml b/ansible/requirements.yml index 6235de6..de87870 100644 --- a/ansible/requirements.yml +++ b/ansible/requirements.yml @@ -95,7 +95,7 @@ - name: elasticsearch src: git@github.com:status-im/infra-role-elasticsearch.git - version: a989381d59e1e0fdeab3a7911a0124a19f68698a + version: 7ec1d25604800e0b5b3172d08e938bef564a2c22 scm: git - name: elasticsearch-lb