# Post upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [May 20, 2019, 4:44pm UTC](https://discuss.elastic.co/t/post-upgrade/181875 "2019-05-20T16:44:58Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Jonathan\_Tarro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonathan_tarro/32/46488_2.png) [@Jonathan\_Tarro](https://discuss.elastic.co/u/Jonathan_Tarro)\ **Post date:** [May 20, 2019, 4:44pm UTC](https://discuss.elastic.co/t/post-upgrade/181875/1 "2019-05-20T16:44:58Z")
Recently upgrade my elasticsearch to version 6.7.2 (along with upgrading graylog to 3.0.2). Now whenever rotate my active write index my elasticsearch cluster goes to red (this is a VM and so I have since reverted to before the rotate). Running "curl -XGET :9200/\_cluster/allocation/explain?pretty" gives me an explanation of "no allocations are allowed due to cluster setting [cluster.routing.allocation.enable=none]". I am not able to figure out from my elasticsearch log (below) what the problem could be. Could anyone be of any help here? > [2019-05-20T11:58:17,181][DEBUG][o.e.a.b.TransportShardBulkAction] [bwFrRi0] [graylog\_74][3] failed to execute bulk item (index) index {[graylog\_deflector][message][8d8f6801-7af6-11e9-b59b-0050568daa06], source[{"Task":0,"Keywords":4611686018429487122,"MachineEnvironment":"production","EventType":"ERROR","gl2\_remote\_ip":"","gl2\_remote\_port":54780,"Opcode":"Info","source":"computer.domain","gl2\_source\_input":"5877c7f3b85fe8038960fafa","SeverityValue":4,"Version":0,"UserID":"S-1-5-18","gl2\_source\_node":"75678ef0-d302-48d8-8b5e-f9a439b9e7d1","ProcessID":5836,"timestamp":"2019-05-20 11:58:14.000","OpcodeValue":0,"SourceModuleType":"im\_msvistalog","level":3,"Channel":"Microsoft-Windows-LiveId/Operational","streams":["000000000000000000000001"],"SourceName":"Microsoft-Windows-LiveId","Severity":"ERROR","message":"SOAP Request of type Service for user CID 'NULL' in production e","AccountType":"User","EventReceivedTime":"2019-05-20 07:58:16","SourceModuleName":"in","ProviderGuid":"{05F02597-FE85-4E67-8542-69567AB8FD4F}","full\_message":"SOAP Request of type Service for user CID 'NULL' in production environment received the following error code from the Microsoft Account server: 0x80041F0D.","ThreadID":18752,"EventID":6114,"ErrorCode":"2147753741","Domain":"NT AUTHORITY","RecordNumber":7407,"AccountName":"SYSTEM","RequestType":"1","cid":"NULL"}]} > java.lang.IllegalArgumentException: Limit of total fields [1000] in index [graylog\_74] has been exceeded > at org.elasticsearch.index.mapper.MapperService.checkTotalFieldsLimit(MapperService.java:639) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:520) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:403) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:338) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.applyRequest(MetaDataMappingService.java:330) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.execute(MetaDataMappingService.java:231) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:643) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:270) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:200) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:135) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:252) ~[elasticsearch-6.7.2.jar:6.7.2] > at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:215) ~[elasticsearch-6.7.2.jar:6.7.2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_212] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_212] > at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_212] > [2019-05-20T12:12:08,508][INFO][o.e.c.m.MetaDataIndexTemplateService] [bwFrRi0] adding template [graylog-internal] for index patterns [graylog\_\*] > [2019-05-20T12:12:08,596][INFO][o.e.c.m.MetaDataCreateIndexService] [bwFrRi0] [graylog\_75] creating index, cause [api], templates [graylog-internal], shards [4]/[0], mappings [message] > [2019-05-20T12:12:08,611][INFO][o.e.c.r.a.AllocationService] [bwFrRi0] Cluster health status changed from [YELLOW] to [RED] (reason: [index [graylog\_75] created]). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 20, 2019, 5:08pm UTC](https://discuss.elastic.co/t/post-upgrade/181875/2 "2019-05-20T17:08:58Z")
It looks like allocation has been disabled. What instructions did you follow to upgrade? ---
**Author:** ![Jonathan\_Tarro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonathan_tarro/32/46488_2.png) [@Jonathan\_Tarro](https://discuss.elastic.co/u/Jonathan_Tarro)\ **Post date:** [May 20, 2019, 6:57pm UTC](https://discuss.elastic.co/t/post-upgrade/181875/3 "2019-05-20T18:57:21Z")
Oh ok, I see what you are saying (and now what the cluster allocation explain is saying). Yes, so to clarify - if it helps anyone - what my problem was 1. during my upgrade I disabled shard allocation with the following: > curl -X PUT :9200/\_cluster/settings -d '{"persistent": {"cluster.routing.allocation.enable": "none"}}' 1. After upgrading to version 6.7.2 new syntax is required per this link [https://www.elastic.co/blog/strict-content-type-checking-for-elasticsearch-rest-requests](https://www.elastic.co/blog/strict-content-type-checking-for-elasticsearch-rest-requests). I didn't notice the failure ({"error":"Content-Type header [application/x-www-form-urlencoded] is not support). Reenabling the shard allocation required "-H 'Content-Type: application/json'" so: > curl -X PUT :9200/\_cluster/settings -H 'Content-Type: application/json' -d '{"persistent": {"cluster.routing.allocation.enable": "all"}}' Thanks so much for your help with this! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 17, 2019, 6:57pm UTC](https://discuss.elastic.co/t/post-upgrade/181875/4 "2019-06-17T18:57:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.