bq. 2. Did you take the solrconfig that came with 7.5 and modify it rather than copy your 5.3 solrconfig? No, We have adjusted existing 5.3.1 config when we used for couple years to SOLR 7.5.0.
I don't think this is the root of your problem, but this is always suspect. Not only can the format of solrconfig change, but certain values don't make any sense, e.g. LuceneMatchVersion would be 2 major versions back, which is unsupported. You may well have changed _that_ value, but can you guarantee all _other_ changes are accounted for? So I'd takethe 7.x solrconfig (and schema for that matter) and overlay your changes rather than try to update the 5x configs. Best, Erick On Thu, Feb 14, 2019 at 1:59 AM Jan Høydahl <jan....@cominvent.com> wrote: > > You may of course ignore the warning in the UI, it is just a warning intended > to help you avoid mis-configurations. > But there may be side effects of placing a load balancer in between client > and zk cluster, see > https://stackoverflow.com/questions/30905007/load-balancer-with-zookeeper > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > > 14. feb. 2019 kl. 01:24 skrev ramyogi <ramy...@gmail.com>: > > > > Thanks Jan, I am unaware how our Devops team decided this But this was > > working well without any issues with SOLR 5.3.1 for couple of years. Just > > wanted to make any changes in SOLR7 mandates . > > > > > > > > -- > > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html >
