lucidworks/solr-helm-chart

A helm chart to install solr into kubernetes

solr-helm-chart's Issues

Newbie to Kubernetes: SolrCloud Cluster status API returns internal kubernetes hostnames which can't be reached from outside the kubernetes cluster

How can I get IP addresses and ports for each of the three Solr nodes so they can be used in a SolrJ Cloud Client connection from outside the cluster? Unless there is a better way?
Thank you for any assistance you can provide.

What would be the best approach to import your own schema?

What would be the best approach to import your own schema?

Build your own solr image, copy over your schema and then leverage this chart while referencing your own solr image?

Change Timezone

How can change the timezone in Solr values? Thanks

Does lucidworks intend on resuming ownership of this chart?

Hello,

A few months ago, I put up a PR to the Helm charts repository for this chart helm/charts#22863

After pinging a number of folks, I was able to get some initial feedback from @scottrigby about the PR.

He noted the deprecation timeline for the stable and incubator charts and pinged @ian-thebridge-lucidworks asking if lucidworks intends on resuming ownership of this repository. I'm just following up with an issue here, since I believe this was the original repository that populated the incubator chart.

As noted in the Helm issue, I work within a community that uses Solr as a dependency for several applications, and we are increasingly relying on this chart for Helm deployments. We're primarily wondering if this is something that you all intend to continue supporting going forward, or whether we should look at considering ownership on our end.

Thank you!

Missing imagePullSecrets

I noticed that it is missing the imagePullSecrets flag.
Sometimes we will have to host the repo in private registry and having this flag helps with it

pod has unbound immediate PersistentVolumeClaims

Trying to run the Helm chart on Minikube and getting "pod has unbound immediate PersistentVolumeClaims" in the dashboard. Doing a Google Search found that having "affinity" rules could do this, so I removed them, but the issue persists.

Any help would be appreciated.

Thanks.

config script persmission on ZK instance(s)

mkdir: cannot create directory ‘/data/log’: Permission denied
/config-scripts/run: line 44: /data/myid: Permission denied

ZK 3.5.5

Add node selector support

Similar to the zookeeper chart. Please add node selector support. Happy to do a pull request if you’re interested.

Error cannot find the solr-0 solr-1 servers

Hi

I am using the following code to index into the SOLR from the dataproc

val df = spark.read.format("csv").option("header", "true").load("gs://a-google-repository/books.csv")
df.show(15)
val zkhost = "exposed-loadbalancer-ip-for-zookeeper:2181"
val collection = "my-collection"
val writeOpts = Map("zkhost" -> zkhost, "collection" -> collection, "batch_size" -> "10000", "commit_within" -> "30000")
df.write.format("solr").options(writeOpts).save
com.lucidworks.spark.util.SolrSupport.getCachedCloudClient(zkhost).commit(collection)

I am getting the error that it cannot find a live server solr-0 solr-1 etc. I suspect that the using loadbalancer for exposing the service might be the issue because of the statefulset, if that is the case is how can I get IP address and can access from outside to the headless zookeeper service? Thanks

Support for Kubernetes 1.16.2

Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "StatefulSet" in version "apps/v1beta1"

apps/v1beta1 has been disabled in 1.16.2

License?

Could you please add a LICENSE file to let us know under what open source license you distribute this. As it currently stands this is closed source, but we would like to use this chart potentially.

Healthcheck breaks with Basic Auth enabled

The current healthcheck endpoint defined, http://:8983/solr/admin/info/system breaks when activating Basic Authentication. After a few seconds the pod is marked as healthy as docker is failing to connect to that endpoint

SSL initContainer failed with "keytool error: java.io.IOException: keystore password was incorrect"

I followed the instructions given for enabling SSL. The init container setup-keystore-and-properties errors out with the following output. I have used the default password of 'changeit' for the password.

unable to write 'random state'
Importing keystore /tmp/keystore.pkcs12 to /tmp/keystore/solr.jks...
keytool error: java.io.IOException: keystore password was incorrect

solr cloud metrics is not visible in prometheus, when using inbuilt exporter

We are using latest version of solr cloud and we deployed it while enabling exporter services. We have found out that it is not providing any metrics to the prometheus. Logs of the exporter pods looks fine and are as below:

/opt/solr/contrib/prometheus-exporter/bin/solr-exporter -p 9984 -z solr-intranet2-zookeeper-0.solr-intranet2-zookeeper-headless:2181 -n 7 -f  /opt/solr/contrib/prometheus-exporter/conf/solr-exporter-config.xml
INFO  - 2020-01-09 12:07:22.473; org.apache.solr.core.SolrResourceLoader; solr home defaulted to 'solr/' (could not find system property or JNDI)
INFO  - 2020-01-09 12:07:23.443; org.apache.solr.common.cloud.SolrZkClient; Using ZkCredentialsProvider: org.apache.solr.common.cloud.VMParamsSingleSetCredentialsDigestZkCredentialsProvider
INFO  - 2020-01-09 12:07:23.535; org.apache.solr.common.cloud.ConnectionManager; zkClient has connected
INFO  - 2020-01-09 12:07:23.589; org.apache.solr.common.cloud.ZkStateReader; Updated live nodes from ZooKeeper... (0) -> (3)
INFO  - 2020-01-09 12:07:23.650; org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at solr-intranet2-zookeeper-0.solr-intranet2-zookeeper-headless:2181 ready
INFO  - 2020-01-09 12:07:23.696; org.apache.solr.prometheus.exporter.SolrExporter; Starting Solr Prometheus Exporting
INFO  - 2020-01-09 12:07:23.709; org.apache.solr.prometheus.collector.SchedulerMetricsCollector; Beginning metrics collection
INFO  - 2020-01-09 12:07:23.763; org.apache.solr.prometheus.exporter.SolrExporter; Solr Prometheus Exporter is running
INFO  - 2020-01-09 12:07:23.880; org.apache.solr.prometheus.collector.SchedulerMetricsCollector; Completed metrics collection
INFO  - 2020-01-09 12:08:23.881; org.apache.solr.prometheus.collector.SchedulerMetricsCollector; Beginning metrics collection
INFO  - 2020-01-09 12:08:23.899; org.apache.solr.prometheus.collector.SchedulerMetricsCollector; Completed metrics collection
INFO  - 2020-01-09 12:09:23.899; org.apache.solr.prometheus.collector.SchedulerMetricsCollector; Beginning metrics collection
INFO  - 2020-01-09 

On 9983 port, Exporter pod is providing only below limited information:
http://127.0.0.1:9983/solr/admin/metrics

# HELP solr_collections_live_nodes See following URL: https://lucene.apache.org/solr/guide/collections-api.html#clusterstatus
# TYPE solr_collections_live_nodes gauge
solr_collections_live_nodes{zk_host="solr-intranet2-zookeeper-headless:2181",} 3.0
# HELP solr_exporter_scrape_error_total Number of scrape error.
# TYPE solr_exporter_scrape_error_total counter
solr_exporter_scrape_error_total 0.0
# HELP solr_exporter_duration_seconds Duration taken to record all metrics
# TYPE solr_exporter_duration_seconds histogram
solr_exporter_duration_seconds_bucket{le="0.005",} 0.0
solr_exporter_duration_seconds_bucket{le="0.01",} 0.0
solr_exporter_duration_seconds_bucket{le="0.025",} 1.0
solr_exporter_duration_seconds_bucket{le="0.05",} 2.0
solr_exporter_duration_seconds_bucket{le="0.075",} 2.0
solr_exporter_duration_seconds_bucket{le="0.1",} 2.0
solr_exporter_duration_seconds_bucket{le="0.25",} 3.0
solr_exporter_duration_seconds_bucket{le="0.5",} 3.0
solr_exporter_duration_seconds_bucket{le="0.75",} 3.0
solr_exporter_duration_seconds_bucket{le="1.0",} 3.0
solr_exporter_duration_seconds_bucket{le="2.5",} 3.0
solr_exporter_duration_seconds_bucket{le="5.0",} 3.0
solr_exporter_duration_seconds_bucket{le="7.5",} 3.0
solr_exporter_duration_seconds_bucket{le="10.0",} 3.0
solr_exporter_duration_seconds_bucket{le="+Inf",} 3.0
solr_exporter_duration_seconds_count 3.0
solr_exporter_duration_seconds_sum 0.219441417

Also, made below changes in the exporter file as it was point to .Values.port.
ports:
- containerPort: {{ .Values.exporter.port }}
name: solr-client

Please let me know, if I have missed anything.

Solr with BasicAuth

Is there any way to configure Solr with basic auth with this helm chart so that we can specify a custom password during deployment?

Create multiple zookeeper services and update zkhosts

Right now it seems as though this chart only creates 1 service for zookeeper and because of this if you have one of the pods fail for zookeeper and its the leader, solr goes down for a few minutes.

I suggest having the chart create 3 services, 1 per zookeeper pod and then update the zkhosts accordingly.

Each service could be similar to the one below.

kind: Service
apiVersion: v1
metadata:
  name: solr-zookeeper-0-service
  labels:
    app: zookeeper
spec:
  selector:
    statefulset.kubernetes.io/pod-name: solr-zookeeper-0
  ports:
  - protocol: TCP
    port: 2180
    targetPort: 2181
  type: ClusterIP