Removing a huge amount of content objects in one go leads to serious Solr index inconsistencies. The plausible reason is the fact that eZ Platform sends separated document removal request for each content objects.

Steps to reproduce

1. Install clean eZ Platform,
2. Configure Solr (ref: https://doc.ezplatform.com/en/2.4/guide/solr/)
3. Set following values in solrconfig.xml to let Solr index immediately:

       <autoCommit>
         <maxTime>${solr.autoCommit.maxTime:1}</maxTime>
         <openSearcher>false</openSearcher>
       </autoCommit>
   

       <autoSoftCommit>
         <maxTime>${solr.autoSoftCommit.maxTime:1}</maxTime>
       </autoSoftCommit>
   

1. Create a folder, for instance, Test under the project root folder,
2. Create 3000 folder objects under the parent created in the previous step,
3. Go to project root folder,
4. Select Test folder from the sub-items list and click on remove,
5. Confirm bulk removal,
6. Go to Content structure -> Search, from filters list select Folder and perform search.
7. On the result list you should see a lot of results (in my test case around 2k)
8. Go to trash, click on Empty trash,
9. Repeat step 9. You should still see lots of contents. If you try to go to the content preview, you should see 404 page.

Current result:
Not all of the content objects are removed from the search index.

Expected result:
All of the content objects should be removed from the search index.

Note:
**Current implementation triggers sending HTTP requests to Solr on kernel.terminate what should probably be changed.