Not able to import the content this exports

OK, the next thing I tried was:

1. Create a "Simple" content type as simple as I can make it. I created a content type with just a body field.
2. Create content using this simple content type.
3. Export that using the drush content:export --entities=
4. Import content using drush content:import scs-export/

That succeeded but also included the error:

Drupal\search_api\SearchApiException while trying to index items on Acquia Search Solr Index: Could not index items on index 'Acquia Search Solr Index' because pending server tasks could not be executed. in Drupal\search_api\Entity\Server->indexItems() (line 363 of /var/www/html/docroot/modules/contrib/search_api/src/Entity/Server.php). 

Now, I have no evidence that my previous attempts were successful. I don't think it succeeded, didn't report its success, because of a search indexing error that occurred at the end.

But the fact that import can succeed if the complexity of the import is small enough points to a resource allocation issue. Do we know roughly how much resources one would need to import the giant files that export process can produce?

I've never seen that issue before, could you please try UI import and see if there are any errors

/admin/content/import

I did this test:

1. Create the simplest content type. A content type with a title and body field
2. Create content with this CT
3. Export the content using the command line.
4. Import the content using the command line.

That succeeded. So even in my case I can prove that the system works (if given enough resources)

It is notable that the yaml file this export produced was about 63MB in size. (Uncompressed)

When I Previously ran into trouble, the content I was exporting was 173 MB in size.

After talking on slack with a few people, I've come to understand that this size is excessive. I would challenge you to test the size of your exports when working with content that has reference fields. I suspect that the export not only includes the content that was referenced (fully) but also the content that the reference references.

That would explain why the size of the export balloons.

I think for now you can try to apply a patch from from this issue 🐛 Handle potential exceptions on batch content import Active

I was exporting and importing zip files over 500 mb, and didn’t have memory issues, maybe there is some kind of recursion issue that causes infinite loop.

In any case, there is an issue that will optimize export ✨ Allow to partially export content Active , still need to find time to develop it