请问docker环境下如何修改内存比例system_memory_high_watermark_ratio

  • nebula 版本:2.5
  • 部署方式:docker

docke环境下,我修改了system_memory_high_watermark_ratio为0.95后,重启了docker-compose又恢复为0.8了。请问我该如何操作呢?docker实在苦手 :joy:

您好,在 compose 的yaml里,找到 graphd 的 command: 加上一行 --system_memory_high_watermark_ratio=0.95

老铁,修改完了该怎么重启服务啊?啥命令?我用docker compose down和up ,结果这个值又变回0.8了

这个例子我只改了一个 graphd,实际上应该改三个,再执行 docker-compose up -d 就好了

$ vim docker-compose.yaml
$ git diff | cat
diff --git a/docker-compose.yaml b/docker-compose.yaml
index b706435..8e945a3 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -230,6 +230,7 @@ services:
       - --log_dir=/logs
       - --v=0
       - --minloglevel=0
+      - --system_memory_high_watermark_ratio=0.99
     depends_on:
       - storaged0
       - storaged1
$ docker-compose up -d

Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.

To deploy your application across the swarm, use `docker stack deploy`.

nebula-docker-compose_metad0_1 is up-to-date
nebula-docker-compose_metad1_1 is up-to-date
nebula-docker-compose_metad2_1 is up-to-date
nebula-docker-compose_storaged0_1 is up-to-date
nebula-docker-compose_storaged1_1 is up-to-date
nebula-docker-compose_storaged2_1 is up-to-date
nebula-docker-compose_graphd1_1 is up-to-date
nebula-docker-compose_graphd2_1 is up-to-date
Recreating nebula-docker-compose_graphd_1 ... done

原来docker-compose down不需要执行啊

嗯嗯,是的哈。

此话题已在最后回复的 7 天后被自动关闭。不再允许新回复。