改M3DB后,transfer启动卡在这里:
{"level":"info","ts":1615712676.6585393,"msg":"waiting for dynamic topology initialization, if this takes a long time, make sure that a topology/placement is configured"}
transfer配置如下:
backend:
datasource: "m3db"
m3db:
enabled: true
name: "m3db"
namespace: "default"
seriesLimit: 0
docsLimit: 0
daysLimit: 7 # max query time
# https://m3db.github.io/m3/m3db/architecture/consistencylevels/
writeConsistencyLevel: "majority" # one|majority|all
readConsistencyLevel: "unstrict_majority" # one|unstrict_majority|majority|all
config:
service:
# KV environment, zone, and service from which to write/read KV data (placement
# and configuration). Leave these as the default values unless you know what
# you're doing.
env: default_env
zone: embedded
service: m3db
etcdClusters:

在配置滴滴夜莺并使用M3DB后,遇到transfer服务启动时端口监听失效的问题。通过调用M3DB的/api/v1/database/create接口创建数据库并设置retentionTime为48小时解决了该问题,但新出现CPU指令集缺少rdtscp支持的问题。
最低0.47元/天 解锁文章
5889

被折叠的 条评论
为什么被折叠?



