Skip to content

Commit 13a5749

Browse files
authoredAug 2, 2023
[bitnami/redis] fix redis sentinel start up (#17932)
Signed-off-by: xudong.wang <xudong.wang@chaitin.com> Co-authored-by: xudong.wang <xudong.wang@chaitin.com>
1 parent b84ef51 commit 13a5749

File tree

3 files changed

+3
-4
lines changed

3 files changed

+3
-4
lines changed
 

‎bitnami/redis/Chart.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -25,4 +25,4 @@ maintainers:
2525
name: redis
2626
sources:
2727
- https://github.com/bitnami/charts/tree/main/bitnami/redis
28-
version: 17.14.4
28+
version: 17.14.5

‎bitnami/redis/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -353,7 +353,7 @@ The command removes all the Kubernetes components associated with the chart and
353353
| `sentinel.annotations` | Additional custom annotations for Redis&reg; Sentinel resource | `{}` |
354354
| `sentinel.masterSet` | Master set name | `mymaster` |
355355
| `sentinel.quorum` | Sentinel Quorum | `2` |
356-
| `sentinel.getMasterTimeout` | Amount of time to allow before get_sentinel_master_info() times out. | `220` |
356+
| `sentinel.getMasterTimeout` | Amount of time to allow before get_sentinel_master_info() times out. | `200` |
357357
| `sentinel.automateClusterRecovery` | Automate cluster recovery in cases where the last replica is not considered a good replica and Sentinel won't automatically failover to it. | `false` |
358358
| `sentinel.redisShutdownWaitFailover` | Whether the Redis&reg; master container waits for the failover at shutdown (in addition to the Redis&reg; Sentinel container). | `true` |
359359
| `sentinel.downAfterMilliseconds` | Timeout for detecting a Redis&reg; node is down | `60000` |

‎bitnami/redis/values.yaml

+1-2
Original file line numberDiff line numberDiff line change
@@ -1058,9 +1058,8 @@ sentinel:
10581058
##
10591059
quorum: 2
10601060
## @param sentinel.getMasterTimeout Amount of time to allow before get_sentinel_master_info() times out.
1061-
## NOTE: This is directly related to the startupProbes which are configured to run every 10 seconds for a total of 22 failures. If adjusting this value, also adjust the startupProbes.
10621061
##
1063-
getMasterTimeout: 220
1062+
getMasterTimeout: 200
10641063
## @param sentinel.automateClusterRecovery Automate cluster recovery in cases where the last replica is not considered a good replica and Sentinel won't automatically failover to it.
10651064
## This also prevents any new replica from starting until the last remaining replica is elected as master to guarantee that it is the one to be elected by Sentinel, and not a newly started replica with no data.
10661065
## NOTE: This feature requires a "downAfterMilliseconds" value less or equal to 2000.

0 commit comments

Comments
 (0)
Please sign in to comment.