Hi Lars, we are running Solr in kubernetes and after some initial problems we are running quite stable now.
Here is the setup we choose for solr: - separate service for external traffic to solr (called “solr”) - statefulset for solr with 3 replicas with another service (called “solr-discovery”) We set the SOLR_HOST (which is used for intra cluster communication) to the pod inside the statefulset (solr-0.solr-discovery.default.svc.cluster.local. This ensures that on solr pod restart the intra cluster communication still continues to work. In the beginning we used the IP address of the pod, this caused problems when restarting pods, they tried to talk with the old ip addresses. Zookeeper inside kubernetes is a different story. Use the latest version of kubernetes, because old versions never reresolved dns names. For connecting to zookeeper we use the same approach, one service-ip for all pods. The statefulset works again with a different service name. The problems we are currently facing: - Client timeouts whenever a solr pod stops and starts again, we currently try to solve this with better readiness probes, no success yet - Sometimes solr collections do not recover completely after a pod restart and we manually have to force recovery, still not investigated fully Hope this helps you! Thanks Björn > On 26. Aug 2017, at 12:08, Lars Karlsson <lars.karlsson.st...@gmail.com> > wrote: > > Hi, I wanted to hear if anyone successfully got solr cloud running on > kubernetes and can share challenges and limitations. > > Can't find much uptodate github projects, would be great if you can point > out blogposts or other useful links. > > Thanks in advance.
