M3DB集群
M3DB
分别配置Coordinator和dbnode
Coordinator配置文件
Coordinator是在prometheus侧负责将数据读写到DBnode,Coordinator本身不存储任何数据
listenAddress:
type: "config"
value: "0.0.0.0:7201" # 交互端口
metrics: # coordinator本身的metric
scope:
prefix: "coordinator"
prometheus:
handlerPath: /monitor/metrics
listenAddress: 0.0.0.0:7203 # until https://github.com/m3db/m3/issues/682 is resolved
sanitization: prometheus
samplingRate: 1.0
extended: none
limits:
maxComputedDatapoints: 10000
tagOptions:
# Configuration setting for generating metric IDs from tags.
idScheme: quoted
clusters:
## Fill-out the following and un-comment before using, and
### make sure indent by two spaces is applied.
- namespaces:
- namespace: metrics
retention: 48h
type: unaggregated
client:
config:
service:
env: default_env
zone: embedded
service: m3db
cacheDir: /var/lib/m3kv
etcdClusters:
- zone: embedded
endpoints:
- HOST1_STATIC_IP_ADDRESS:2379
- HOST2_STATIC_IP_ADDRESS:2379
- HOST3_STATIC_IP_ADDRESS:2379
## - M3DB_NODE_02_STATIC_IP_ADDRESS:2379
## - M3DB_NODE_03_STATIC_IP_ADDRESS:2379
### ... etc, list only M3DB seed nodes
writeConsistencyLevel: majority
readConsistencyLevel: unstrict_majority
writeTimeout: 10s
fetchTimeout: 15s
connectTimeout: 20s
writeRetry:
initialBackoff: 500ms
backoffFactor: 3
maxRetries: 2
jitter: true
fetchRetry:
initialBackoff: 500ms
backoffFactor: 2
maxRetries: 3
jitter: true
backgroundHealthCheckFailLimit: 4
backgroundHealthCheckFailThrottleFactor: 0.5
相关文章