【问题描述(我做了什么)】通过loader导入数据,有一个tikv的pod出现fatal:[2019/10/28 06:22:25.999 +00:00] [FATAL] [server.rs:145] [“failed to create raft engine: RocksDb IO error: No space left on deviceWhile appending to file: /var/lib/tikv/raft/000725.sst: No space left on device”]
diff --git a/charts/tidb-cluster/values.yaml b/charts/tidb-cluster/values.yaml
index 22f2978..4818fdb 100644
--- a/charts/tidb-cluster/values.yaml
+++ b/charts/tidb-cluster/values.yaml
@@ -190,7 +190,8 @@ tikv:
# Please refer to https://pingcap.com/docs-cn/v3.0/reference/configuration/tikv-server/configuration-file/
# (choose the version matching your tikv) for detailed explanation of each parameter.
config: |
- log-level = "info"
+ #log-level = "info"
+ log-level = "error"
# # Here are some parameters you MUST customize (Please configure in the above `tikv.config` section):
#
# [readpool.coprocessor]
@@ -226,7 +227,8 @@ tikv:
# different classes might map to quality-of-service levels, or to backup policies,
# or to arbitrary policies determined by the cluster administrators.
# refer to https://kubernetes.io/docs/concepts/storage/storage-classes
- storageClassName: local-storage
+ #storageClassName: local-storage
+ storageClassName: standard
# Image pull policy.
imagePullPolicy: IfNotPresent
@@ -239,7 +241,7 @@ tikv:
requests:
# cpu: 12000m
# memory: 24Gi
- storage: 10Gi
+ storage: 60Gi
## affinity defines tikv scheduling rules,affinity default settings is empty.
## please read the affinity document before set your scheduling rule:
@@ -293,7 +295,8 @@ tidb:
# (choose the version matching your tidb) for detailed explanation of each parameter.
config: |
[log]
- level = "info"
+ #level = "info"
+ level = "error"
# # Here are some parameters you MUST customize (Please configure in the above 'tidb.config' section):
# [performance]