# X of Y shards failed in 7.12 **URL:** \ **Category:** Kibana\ **Created:** [April 23, 2021, 8:14am UTC](https://discuss.elastic.co/t/x-of-y-shards-failed-in-7-12/271052 "2021-04-23T08:14:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![d4nnyx](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@d4nnyx](https://discuss.elastic.co/u/d4nnyx)\ **Post date:** [April 23, 2021, 8:14am UTC](https://discuss.elastic.co/t/x-of-y-shards-failed-in-7-12/271052/1 "2021-04-23T08:14:49Z")
Hello there, after upgrade Elastic Stack from 7.10 to 7.12 a lot of dasboards, visualization and searches in discover shows the error message `X of Y shards failed`. In most cases, reason is that the specific field is not leaf field. These conflicted field had always been there, but always this error showed up only if I search this particular field. Now error shows up even if I simply want to view some documents, where is field present. I cannot find anything in release notes about this or something like that and it causes us a lot of trouble, especially when logging something like Response body, which often differs if I request multiple APIs. Is there any way to make Kibana less strict about mapping again? Custom mapping is probably not an option for us, we have 10K+ diferrent indices. ---
**Author:** ![dosant](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dosant/32/64489_2.png) [@dosant](https://discuss.elastic.co/u/dosant)\ **Post date:** [May 11, 2021, 10:37am UTC](https://discuss.elastic.co/t/x-of-y-shards-failed-in-7-12/271052/2 "2021-05-11T10:37:16Z")
Hi @d4nnyx, Looks like your are hitting: [Discover: Rollup index pattern doesn't work with source fetching · Issue #92362 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/92362) Rollup indices have issues in Discover then `discover:searchFieldsFromSource` advanced option is enabled. Could you check if this is the case for you? ---
**Author:** ![d4nnyx](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@d4nnyx](https://discuss.elastic.co/u/d4nnyx)\ **Post date:** [May 11, 2021, 10:58am UTC](https://discuss.elastic.co/t/x-of-y-shards-failed-in-7-12/271052/3 "2021-05-11T10:58:23Z")
Hello @dosant , yes, we enabled this setting, because the new multi-field view is really confusing. We use dynamic mapping and every text field has its keyword type, so basically every field has another field which I dont want to care about. Is there any workaround for this issue? ---
**Author:** ![dosant](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dosant/32/64489_2.png) [@dosant](https://discuss.elastic.co/u/dosant)\ **Post date:** [May 11, 2021, 11:14am UTC](https://discuss.elastic.co/t/x-of-y-shards-failed-in-7-12/271052/4 "2021-05-11T11:14:24Z")
I am not aware of a workaround ☹ Could you please contribute to the discussion [Discover: Rollup index pattern doesn't work with source fetching · Issue #92362 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/92362) with your use case? That would be helpful. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [June 1, 2021, 8:27pm UTC](https://discuss.elastic.co/t/x-of-y-shards-failed-in-7-12/271052/5 "2021-06-01T20:27:42Z")
Hello, I just updated to 7.12.1 yesterday and now I'm seeing this in Discover, We have `discover:searchFieldsFromSource` enabled because we need to see the json structure, but We do not have rollup indices, this is an indice create by logstash. Shoud I update this issue or create another one since I do not use rollup indices but I'm facing the same error reported on the issue? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 29, 2021, 8:28pm UTC](https://discuss.elastic.co/t/x-of-y-shards-failed-in-7-12/271052/6 "2021-06-29T20:28:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.