We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
你好,不好意思还要麻烦一下,我按照readme中的所说的service label的方式配置了一个测试nginx,stack是这样的:
`version: '3.6' services:
nginx: image: nginx:latest environment: - TZ=Asia/Shanghai deploy: labels: swirl.scale: swirl.scale=min=1,max=5,cpu=20:50 restart_policy: condition: on-failure resources: limits: cpus: "0.01" memory: 200M update_config: parallelism: 1 # 每次更新1个副本 delay: 5s # 每次更新间隔 monitor: 10s # 单次更新多长时间后没有结束则判定更新失败 max_failure_ratio: 0.1 # 更新时能容忍的最大失败率 order: start-first # 更新顺序为新任务启动优先
ports: - 18081:80`
但是在后面的压测中,一直没有看到这个service进行scale的动作,请问是哪里配置有问题吗?谢谢!
The text was updated successfully, but these errors were encountered:
好像配置不太对,这个功能肯定没问题的,我们用了很久了,参考下图:
Sorry, something went wrong.
另外,调整完服务信息后不要马上压测,需要等几分钟(更新窗口期,默认 3 分钟),这是为了减少实际场景中的波动
No branches or pull requests
你好,不好意思还要麻烦一下,我按照readme中的所说的service label的方式配置了一个测试nginx,stack是这样的:
`version: '3.6'
services:
nginx:
image: nginx:latest
environment:
- TZ=Asia/Shanghai
deploy:
labels:
swirl.scale: swirl.scale=min=1,max=5,cpu=20:50
restart_policy:
condition: on-failure
resources:
limits:
cpus: "0.01"
memory: 200M
update_config:
parallelism: 1 # 每次更新1个副本
delay: 5s # 每次更新间隔
monitor: 10s # 单次更新多长时间后没有结束则判定更新失败
max_failure_ratio: 0.1 # 更新时能容忍的最大失败率
order: start-first # 更新顺序为新任务启动优先
但是在后面的压测中,一直没有看到这个service进行scale的动作,请问是哪里配置有问题吗?谢谢!
The text was updated successfully, but these errors were encountered: