temporalio / temporalio/temporal
temporal frontend unable to connect to elasticsearch visibilitystore
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
I am trying to deploy temporal with visibility set as elastic search... but I am getting this error.
Error: INSTALLATION FAILED: execution error at (temporal/templates/server-deployment.yaml:37:28): Please specify cassandra port for visibility store.
Thus is my values.custom.yaml file:
server:
enabled: true
config:
persistence:
defaultStore: default
advancedVisibilityStore: es-visibility
datastores: {}
default:
driver: "sql"
sql:
driver: "mysql"
host: "10.24.40.101"
port: 4000
database: "temporal"
user: "readwrite"
password: "2UQs4+iw0U"
maxConns: 500
maxConnLifetime: "1h"
es-visibility:
driver: "elasticsearch"
elasticsearch:
version: "v8"
logLevel: "error"
url:
scheme: "http"
host: "chanakya-temporal-playground-es-http.ekl-cl-chanakya-playground.svc.cluster.local:9200"
indices:
visibility: "temporal_visibility"
cassandra:
enabled: false
config:
ports:
cql: 9042
mysql:
enabled: false # We're using external MySQL
postgresql:
enabled: false
elasticsearch:
enabled: false # Using external Elasticsearch
external: true
version: "v8"
scheme: "http"
host: "chanakya-temporal-playground-es-http.ekl-cl-chanakya-playground.svc.cluster.local"
port: "9200"
username: ""
password: ""
visibilityIndex: "temporal_visibility_v1"
logLevel: "error"
prometheus:
enabled: false
grafana:
enabled: false
schema:
setup:
enabled: false # Schema already set up
update:
enabled: false # Schema already set up
I am not even using cassandra enywhere but still getting this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with temporal/templates/server-deployment.yaml:37:28 and compare its Cassandra port validation with the persistence and external Elasticsearch settings in values.custom.yaml. Reproduce the Helm installation using the supplied configuration, then verify that an external Elasticsearch visibility store with Cassandra disabled no longer triggers the Cassandra-port error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, helm, mysql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100