Closed xrow closed 3 years ago
Hi there, I think you are looking at the wrong issue, it should be https://issues.apache.org/jira/browse/SOLR-13801 which is duplicated by https://issues.apache.org/jira/browse/SOLR-14389 mentioned in SOLR-14371 you provided.
This issue is mentioned in the chart README.md
The idea might be to hand over all svcs instead of the headless service.
What do you mean by "hand over all svcs"?
Here is a sample of what i did for varnish for a ENV parameter
HTTPCACHE_PURGE_SERVER: "{{- range $index, $v := until ( int .Values.varnish.replicas ) -}}http://{{ include "call-nested" (list $ "varnish" "varnish.fullname") }}-{{$index}}.{{ include "call-nested" (list $ "varnish" "varnish.fullname") }}.{{ $.Release.Namespace }}.svc.cluster.local:6081{{- if ne (add $index 1) ( int $.Values.varnish.replicas) -}},{{- end -}}{{- end -}}"
It’s a possible solution. But there is a drawback.
If auto scaling were to be enabled on ZK for example, then the connection string will not change, which can be an issue. Using the current way will allow Solr to randomly connect to any number of ZK.
Like I’ve addressed in the README.md it is merely a cosmetic issue, I don’t see the value of resolving a cosmetic issue and incurring a functional drawback.
Ok I though i better raise the finding. I thought it is some defect.
No worries! Good to be on the safe side. Thanks for understanding
If you would like to know more refer to #21
Affected chart Lastest version and before
Describe the bug
When
is set it will lead to a warning in the solr backend. I think this can be improved.
The idea might be to hand over all svcs instead of the headless service.
The warning is:
Errors: Your ZK connection string (2 hosts) is different from the dynamic ensemble config (3 hosts). Solr does not currently support dynamic reconfiguration and will only be able to connect to the zk hosts in your connection string. ZK connection string: zookeeper-headless:2181,zookeeper-headless:2181 Ensemble size: 3 Ensemble mode: ensemble Dynamic reconfig enabled: true
To Reproduce Use Config
Expected behavior
No warning in SOLR backend
Screenshots If applicable, add screenshots to help explain your problem.
Helm and Kubernetes: does not matter
Additional context https://issues.apache.org/jira/browse/SOLR-14371