Closed LucaCinquini closed 8 years ago
This is now fixed in the esg-search installation script, which starts the slave:8983 and all replica shard with both flags enabled: -Denable.master=true and -Denable.slave=true.
Verified by Luca on esgf-dev and Katharina @ DKRZ.
Currently, changes to the Solr schema.xml do NOT propagate to the slave or replica shards. This is because the slave on port 8983 is NOT acting as a Solr repeater.