richardbadman commented on issue #618: URL: https://github.com/apache/solr-operator/issues/618#issuecomment-6471286777
Hey, I know this is a bit of an old issue. But we've revisited using the solr operator again in our company. In our bare metal environments for each cluster we have typically; - X number of machines for Solr only. 95% of these instances are typical solr cloud instances, and the remaining 5% are dedicated coordinator instances. - 3 number of machines for ZK and a small solr instance for solr overseer. I was curious how I would go about this when using the solr operator, and came across this issue. The way I have gone around this (as I couldn't see anything in the change log about this) was having 3 manifests, 1 for the main bulk of the cluster which was the data nodes and the zookeeper creation & management, the other two are almost identical, but differentiate their roles of coordinator and overseer with differing resource allocations. These two also referenced the zookeeper ensemble in the first manifest, and it seems to have worked well. More than happy to provide a code example if needed. It might not be the _best_ solution, but it is one that seemed trivial and worked. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
