Closed naughtyGitCat closed 5 years ago
problem node config
db:
logging:
level: info
metrics:
prometheus:
handlerPath: /metrics
sanitization: prometheus
samplingRate: 1.0
extended: detailed
hostID:
resolver: config
value: SATA001
config:
service:
env: default_env
zone: embedded
service: m3db
cacheDir: /data1/m3db/cache
etcdClusters:
- zone: embedded
endpoints:
- 127.0.0.1:2379
listenAddress: 0.0.0.0:9000
clusterListenAddress: 0.0.0.0:9001
httpNodeListenAddress: 0.0.0.0:9002
httpClusterListenAddress: 0.0.0.0:9003
debugListenAddress: 0.0.0.0:9004
client:
writeConsistencyLevel: majority
readConsistencyLevel: unstrict_majority
gcPercentage: 100
writeNewSeriesAsync: true
writeNewSeriesLimitPerSecond: 1048576
writeNewSeriesBackoffDuration: 2ms
bootstrap:
bootstrappers:
- filesystem
- commitlog
- peers
- uninitialized_topology
fs:
numProcessorsPerCPU: 0.125
cache:
series:
policy: lru
postingsList:
size: 262144
commitlog:
flushMaxBytes: 524288
flushEvery: 1s
blockSize: 10m
queue:
calculationType: fixed
size: 2097152
fs:
filePathPrefix: /data1/m3db
@naughtyGitCat Whats your namespace configuration? The messed up node is trying to bootstrap all the way back from 1973 :/ Do you have some kind of crazy long retention, or is a zero value sneaking in there somehow?
thanks to Evan, I turn the shards num from 192 to 48, then the cluster boots up successfully. perhaps my SAS disk doesn`t fit this config.
problem binary
m3dbnode
problem occurs
Initializing a three RF with three isolation_group, one of the three m3dbnodes stuck in bootstrapping default namespace
the m3dbnode
environments
pstack m3dbnode process
tailf m3dbnode log
strace m3dbnode process