# Kibana error on migration saved-object **URL:** \ **Category:** Kibana\ **Created:** [September 13, 2021, 3:41pm UTC](https://discuss.elastic.co/t/kibana-error-on-migration-saved-object/284098 "2021-09-13T15:41:52Z")\ **Posts on this page:** 5\ **Page:** 2
**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\ **Post date:** [September 15, 2021, 10:02pm UTC](https://discuss.elastic.co/t/kibana-error-on-migration-saved-object/284098/21 "2021-09-15T22:02:35Z")
The logs are mysteriously truncated. It might be that Kibana is running out of memory, if you're running Kibana in docker you should see the stack trace, but I'm not sure how this works with docker-compose. I'd suggest running Kibana without docker compose to see if you can't see the logs. Without logs anything we do is just guessing. I missed this previously: > The amount of total data is not more than 250MB By default Kibana will read 1000 documents during a migration and try to write all 1000 of them using a bulk index. In your case this will create a bulk indexing payload of at least 250MB which will run into Elasticsearch's `http.max_content_length` limit which defaults to 100MB. You can try to set `migrations.batchSize: 1` to see if migrations would pass. If each of your 19 saved objects are 250/19=13MB that would be fine, but if one of them are larger than 100MB this would still fail. So you might have to trim back your jupyter notebooks before importing them into Kibana. ---
**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\ **Post date:** [September 15, 2021, 10:05pm UTC](https://discuss.elastic.co/t/kibana-error-on-migration-saved-object/284098/22 "2021-09-15T22:05:00Z")
We've fixed the problem of migration batches exceeding ES's max\_content\_length in 7.15 (yet to be released) [https://github.com/elastic/kibana/pull/109540](https://github.com/elastic/kibana/pull/109540) ---
**Author:** ![LombardoAndrea195](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lombardoandrea195/32/88080_2.png) [@LombardoAndrea195](https://discuss.elastic.co/u/LombardoAndrea195)\ **Post date:** [September 16, 2021, 7:19am UTC](https://discuss.elastic.co/t/kibana-error-on-migration-saved-object/284098/23 "2021-09-16T07:19:35Z")
Thanks for the explanation. I could guess about the memory size in kibana but i don't know what is in particular the problem. Can I ask you, how can I solve the problem? I think a solution could be remouve only the saved\_object. I can guess the name of the visualization but how can I remouve from bash, becuase kibana doesn't work? Or in faster way I can remouve .kibana index such that I can restore the index-patterns and visualization. ---
**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\ **Post date:** [September 16, 2021, 10:56am UTC](https://discuss.elastic.co/t/kibana-error-on-migration-saved-object/284098/24 "2021-09-16T10:56:15Z")
The best way to do this is to rollback to a previous version of Kibana. I'm guessing you might not have backup snapshots so then you'll need to follow these instructions: [Upgrade migrations | Kibana Guide [7.14] | Elastic](https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html#_not_recommended_rollback_without_a_backup_snapshot) Once you've rolled back you can use saved objects management to delete the visualization. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 14, 2021, 10:57am UTC](https://discuss.elastic.co/t/kibana-error-on-migration-saved-object/284098/25 "2021-10-14T10:57:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. [Previous page](https://discuss.elastic.co/t/kibana-error-on-migration-saved-object/284098.md?page=1)