-
Notifications
You must be signed in to change notification settings - Fork 258
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 configure Redis Sentinel or Redis Cluster with official Helm, standalone Redis works fine #543
Comments
Sorry for the delay! I edited your description to make it a little easier to read by adding collapsibles and syntax highlighting. If you're trying to use redis cluster vs stand alone, the seeds param you specified should be correct according to docs.nextcloud.com/server/29: <?php
$CONFIG = array (
'memcache.distributed' => '\OC\Memcache\Redis',
'memcache.locking' => '\OC\Memcache\Redis',
'redis.cluster' => array(
'seeds' => array(
'redis-cluster-headless:6379'
),
'password' => getenv('REDIS_HOST_PASSWORD'),
),
); I don't use redis cluster, but if I'm understanding correctly, the seed should be the name of the redis service right? - which should be whatever this is: https://github.com/bitnami/charts/blob/1a5338daf534b712823a407b409f7b71b9ddb294/bitnami/redis-cluster/templates/redis-svc.yaml#L9 - which should be whatever your helm release name is for the redis cluster helm chart release, or the Some minor follow up questions:
If others in the community have better information or suggestions here, please feel free to chime in, as I haven't been using redis lately. |
To be honest I long gave up on this but in case we manage to figure it out:
1. Yep, deleting the persistent storage each time.
2. Confirmed the service name many a time.
…-------- Original Message --------
On 9/06/24 22:14, JesseBot wrote:
Sorry for the delay! I edited your description to make it a little easier to read by adding collapsibles and syntax highlighting.
If you're trying to use redis cluster vs stand alone, the seeds param you specified should be correct according to [docs.nextcloud.com/server/29](https://docs.nextcloud.com/server/29/developer_manual/how_to/index.html#redis-cluster):
<?php
$
CONFIG
=
array
(
'memcache.distributed'
=>
'\OC\Memcache\Redis'
,
'memcache.locking'
=>
'\OC\Memcache\Redis'
,
'redis.cluster'
=>
array
(
'seeds'
=>
array
(
'redis-cluster-headless:6379'
),
'password'
=> getenv(
'REDIS_HOST_PASSWORD'
),
),
);
I don't use redis cluster, but if I'm understanding correctly, the seed should be the name of the redis service right? - which should be whatever this is: https://github.com/bitnami/charts/blob/1a5338daf534b712823a407b409f7b71b9ddb294/bitnami/redis-cluster/templates/redis-svc.yaml#L9 - which should be whatever your helm release name is for the redis cluster helm chart release, or the fullnameOverride parameter value for that chart.
Some minor follow up questions:
-
Are you doing a fresh install of nextcloud in between testing different redis installations? I ask because I noticed you have persistence enabled in your values.yaml. If not, can you try a fresh install without persistence while also using a fresh install of redis-cluster?
-
Can you verify the name of the redis service when using bitnami's redis-cluster chart?
If others in the community have better information or suggestions here, please feel free to chime in, as I haven't been using redis lately.
—
Reply to this email directly, [view it on GitHub](#543 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ADUNCRQ2LX47VD6IECOLGD3ZGQTG3AVCNFSM6AAAAABEOZFGGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWGQZDONRVGE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Describe your Issue
Using the official Helm chart I am able to configure Redis in standalone mode with the following values:
values.yaml
When when I setup Redis with sentinel using the Bitnami Redis helm chart and the following values in the redis.config.php section:
(only host and port changes)
I get the following errors in the logs and I am usually unable to see any files in the webUI, or unable to login:
click me for logs
And when I spin up bitnami's redis cluster chart and change the redis.config.php to the following:
(I have aslo tried
redis-cluster:6379
for the seed, I get the same result)I get the following errors in the logs and an internal system error on loading the webui:
click me for more logs
Indicating it can't see any of the redis nodes at all.
Logs and Errors
As above
Describe your Environment
K3s on Ubuntu
Helm Version (or App that manages helm): k3s and fluxio
Helm Chart Version: 4.latest
values.yaml
:Included above
The text was updated successfully, but these errors were encountered: