[bitnami/zookeeper] Fix backwards incompatibility issue (#3175)

This commit is contained in:
Juan Ariza Toledano
2020-07-21 15:11:19 +02:00
committed by GitHub
parent 53db7d033f
commit fd27fd3aa5
3 changed files with 9 additions and 5 deletions
+1 -1
View File
@@ -95,7 +95,7 @@ The following tables lists the configurable parameters of the ZooKeeper chart an
| `logLevel` | Log level of ZooKeeper server | `ERROR` |
| `jvmFlags` | Default JVMFLAGS for the ZooKeeper process | `nil` |
| `config` | Configure ZooKeeper with a custom zoo.conf file | `nil` |
| `dataLogDir` | Data log directory | `/bitnami/zookeeper/dataLog` |
| `dataLogDir` | Data log directory | `""` |
### Statefulset parameters
+4 -3
View File
@@ -176,9 +176,10 @@ heapSize: 1024
##
logLevel: ERROR
## Data log directory. Specifying this option will direct zookeeper to write the transaction log to the dataLogDir rather than the dataDir.
## This allows a dedicated log device to be used, and helps avoid competition between logging and snaphots.
dataLogDir: /bitnami/zookeeper/dataLog
## Example:
## dataLogDir: /bitnami/zookeeper/dataLog
##
dataLogDir: ""
## Default JVMFLAGS for the ZooKeeper process
##
+4 -1
View File
@@ -185,7 +185,10 @@ logLevel: ERROR
## Data log directory. Specifying this option will direct zookeeper to write the transaction log to the dataLogDir rather than the dataDir.
## This allows a dedicated log device to be used, and helps avoid competition between logging and snaphots.
dataLogDir: /bitnami/zookeeper/dataLog
## Example:
## dataLogDir: /bitnami/zookeeper/dataLog
##
dataLogDir: ""
## Default JVMFLAGS for the ZooKeeper process
##