- Issue created by @c-logemann
- 🇩🇪Germany c-logemann Frankfurt/M, Germany
Research Update:
This situation seems to be very special because of another customer project with has many things in common. Especially actually the same combination of PHP 7.4 LTS and even lot's of custom code but works already in productive with the setup described above.
So we now concentrate of the differences between this two projects and figure out what is the reason of this bug. - Assigned to c-logemann
- 🇩🇪Germany c-logemann Frankfurt/M, Germany
@mkalkbrenner Not yet because we are currently very busy in several customer projects. Because of the very special situation described above I assign myself. As soon we find out more I will report here.
- 🇩🇪Germany c-logemann Frankfurt/M, Germany
One thing I forgot to report: I figured out that the upload itself does not fail. Because of error reports in Solr I'm sure that the generated config itself is corrupt under this special circumstances.
- Status changed to Postponed: needs info
about 1 year ago 4:09pm 1 November 2023 - 🇩🇪Germany c-logemann Frankfurt/M, Germany
The customer system will be upgrade soon to php 8.1. So I re-tested with Search API Solr version:
4.3.0 and updates of all modules and libraries to php 8.1 code and now it's working.I currently don't have the time to figure what exactly went wrong. But I believe there was a library involved to generate corrupted config. Because the very bad impact to the solr cloud config in this case I think it would be fine if there will be a config validation in future before uploading to solr. So I change the this issue category "Feature request" and change the title.
@mkalkbrenner When I find some time for this will set up a test system and will try to reproduce this error.
- Issue was unassigned.
- Status changed to Closed: won't fix
about 1 year ago 4:54pm 11 November 2023 - 🇩🇪Germany mkalkbrenner 🇩🇪
I don't think that such a validation is possible. Only Solr itself could tell you if something is wrong. The only way would be to upload and test the config-set using a test collection. That seems to be related to
✨ Swap cores when reindexing Active - 🇩🇪Germany c-logemann Frankfurt/M, Germany
Because the impact is a complete corrupted solr cloud setup it can only help to work with two cloud setup not only different collections.
I finally found the configuration which caused the problem which was based on copying drupal config from one project to another but there was no error on import. SO maybe there is a bug in core or this module.
I only disabled it as workaround and will analyze it when I find some time to. And I will try to create some anonymized config and try to get something which can be used to reproduce this error in a vanilla setup.