Solr Cloud

[mkalkbrenner]

I took a look at ddev-typo3-solr and wonder why it still uses Solr Standalone. Nowadays most of the Solr hosting providers run Solr Cloud. From my experience, even legacy PHP applications that aren't aware of additional Solr Cloud features run perfectly well on Solr Cloud. And they still could connect to it without modifications to the code or configs.
This was the reason why we decided to go for Solr Cloud in ddev-solr.

But in the past, you needed to adjust things in ddev-solr or ddev's config.yaml to get an application to work that "expects" Solr Standanlone. But I talked to others to better understand their issues and helped porting an old ddev setup to use ddev-solr and to switch from standalone to cloud. As a result, now with ddev-solr 0.4.0 I added some convenient functions to better support such applications:

• third party Solr plugins/modules/libs could be installed by copying jar files into .ddev/solr/libs
• configsets could be deployed and corresponding "collections" could be created by just copying a configset into .ddev/solr/configsets
• read and write access to an "index" is possible without basic authentication
• ...

I was able to "deploy" a German and an English "typo3 core" as collections within a few minutes, including the typo3 Solr plugin.

But I don't want to include any typo3-specific stuff into ddev-solr. Just like we don't put any drupal-specific stuff into it ... except documentation.

On the other hand, we should avoid to have different "official" solr modules for ddev. And sooner or later, typo3 must move to Solr Cloud.

So my suggestion is to modify ddev-typo3-solr to depend on ddev-solr and to just take care about deploying the required language-specific "cores" (in fact collections) and the the typo3 plugin.

@ochorocho @rfay What do you think about that?

[ochorocho]

This is what i got from apache-solr-for-typo3/solr Maintainers

I fear that we do not support this.

Great you've got solr cloud working! It didn't work for me. I'm pretty sure the maintainers will accept a PR to add support for solr cloud on their repository

Once that is done, i am happy to change my addon or merge my features into the "ddev solr" addon (if needed) so there is only one solr add-on for all.

[mkalkbrenner]

@ochorocho thanks for the reply.
I worked with @timohund in the past and helped to migrate typo3's ext-solr to solarium. But I don't have time to contribute to ext-solr.

My suggestion is something else. They should not modify ext-solr to support solr-cloud explicitly, at least it is not required just for ddev.
We could simply deploy it on cloud in ddev. Typo3 should not notice that as the single cloud node behaves like Standalone for ext-solr.

[ochorocho]

Ok, that is interessting. That would be great if we could get it to work without modification of ext-solr.

Thank you!

[bmack]

Hey @mkalkbrenner ,

thanks for picking this up. I will be at a TYPO3-solr code sprint next week with @dkd-kaehm @dkd-friedrich and @dkd-dobberkau - I will bring this topic up and see what needs to be done to support SolrCloud.

OTOH if we stick with SolrCloud as a best practice for DDEV we need to educate people to not use Solr Standalone anymore in their prod envs.

[mkalkbrenner]

@bmack thanks for that!