-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to deploy tb-integration-executor with redis sentinel #88
Comments
EDIT: I forgot to mention currently we are running TB 3.6.2 as a k8 deployment. |
The documentation of the integration executor should be updated to reflect this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
i'm facing an issue with deployment of tb-integration-executor and redis sentinel. I was able to deploy tb-node with sentinel configured
(even tho some important information is missing in the TB Core component docs) with the following StatefulSet env vars:
So after seeing that the tb-integration-executor also specifies redis as a parameters in the minikube deployment yaml files. I thought i could just copy this configuration and it will work. But to my surprise it didn't.
When is set my thingsboard.yaml for the integration-executor env vars like this:
the pod logs look like this :
thingsboard-tb-integration-executor-0-1725375316634848100.log
So after looking in some thingsboard code i found that the key to provide redis sentinel master name is: redis.sentinel.master So i thought of env variable would look like this: REDIS_SENTINEL_MASTER, when i tried that in the env vars for the integration-executor i got the following logs:
thingsboard-tb-integration-executor-0-1725375710414817500.log
Please bear in mind that this redis sentinel cluster is working fine for the tb-node.
Any help is appreciated, Thank you
Sam
The text was updated successfully, but these errors were encountered: