Comments (6)
For some reason I swore the gossip behavior was deprecated/removed in Temporal as a step away from Cadence, but checking a quick tctl admin membership list_gossip
shows all the pods that I would expect. Thank you for redirecting me on this one, this probably helps explain some of the behavior I'm seeing.
from helm-charts.
@thempatel did you happen to resolve this in your environment? I believe I'm running into a similar issue.
from helm-charts.
@emmercm we ended up forking the helm chart for temporal to fix the various bugs in it. For this one, I did end up changing the hard coded port to instead be sourced from user configuration (values.yaml
).
note: it's been a really long time, so take this with a grain of salt:
IIRC, the localhost is OK because i think there's actually a proxy that listens on localhost for the frontend service, so connecting to localhost will just forward the connection to the internally configured frontend RPC service which will then forward to the actual services. 🤷🏽♂️
from helm-charts.
@thempatel we've also forked the chart, but more so we can better configure our unique Kubernetes environment and multi-cluster than anything.
The proxy would make a ton of sense, but I didn't find any trace of it in GitHub: https://github.com/search?q=org%3Atemporalio+7933&type=code. I would think localhost in this case would be Kube node-local rather than container-local, right? I'm running into issues with multi-cluster where I believe I'm getting some cross-talk, and I've convinced myself it's this localhost config.
from helm-charts.
@emmercm after reading #333 , noticed you're trying to run 2 unique temporal clusters. you cannot do this without isolating them, the services use a gossip protocol where they broadcast messages on a port. if your two clusters have services that are all broadcasting on the same port, but you've configured two different storage instances (sql, etc), you're going to run into problems.
The reason why I filed this (and subsequently forked) was exactly so that we could run multiple clusters all configured using different ports so that the two clusters don't run into each other.
One thing you could try to see if it solves your problem (if you haven't already), is to configure each of those clusters to be in their own K8s namespaces. If that works, then you'll just need to account for adding namespaces within the connection to the cluster in your clients.
from helm-charts.
This was super helpful! After a fresh deployment, no communications with the task queues were working. I was getting context deadline timeouts on tctl tq describe --taskqueue all
.
Then following this thread I changed the rpcAddress
to match the frontend service name and port in my cluster: rpcAddress: "temporal-frontend:7233"
Now I'm able to list task queues and I can see that the matching server joined tctl admin membership list_gossip
from helm-charts.
Related Issues (20)
- [Feature Request] sidecar container for schema creation & update jobs HOT 1
- [Bug] ElasticSearch index not created when using existing SQL/Cassandra HOT 4
- [Feature Request] Add TLS support for es-visibility in the helm chart
- Add to chat the ability to mount client certificates for admin tools deployment
- [Feature Request] Document installing from helm repo
- [Feature Request] Support Dual Visibility Setup
- [Feature Request] [Archival] [s3 provider] use IAM role + serviceAccount
- [Bug] self-hosted temporal with AWS RDS (Unable to connect to SQL database) HOT 1
- Visibility config doesn't get rendered if visibility and default store types are different HOT 3
- [Feature Request] Move cassandra from Deprecate version to version cassandra from bitnami HOT 1
- [Feature Request] Make Kubernetes Cluster Domain Dynamic/Configurable
- Pods Stuck in CrashLoopBackoff on Fresh Deployment to Fresh Kubernetes Cluster HOT 6
- Helm installation failure with opensearch as visibilitystore and postgres as defaultstore
- [Bug] Unable to use mTLS certs to connect to mysql in the schema setup/upgrade jobs
- [Feature Request] Installing Temporal in Kubernetes with TLS certs in existing secret/configmap. HOT 1
- Helm git tags don't match with main repo anymore HOT 2
- temporal-sql-tool does not accept hostnames longer than 68 characters HOT 2
- [Bug] Temporal helm-charts ownership and maintainability HOT 1
- [Feature Request] Add possibility to add annotations to server configmap HOT 1
- [Bug] Custom env variables for update schema job
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from helm-charts.