nebula 2.6.1查询报错

  • nebula 版本:2.6.1
  • 部署方式: 单机
  • 安装方式:Docker
  • 是否为线上版本:Y
  • 硬件信息
    • 磁盘( 推荐使用 SSD)
    • CPU、内存信息
  • 问题的具体描述
  • 相关的 meta / storage / graph info 日志信息(尽量使用文本形式方便检索)

-使用nebula-go查询时报错如下

{"errors":[{"message":"Used memory hits the high watermark(0.800000) of total system memory.","code":-1005}],"results":[{"spaceName":"event","errors":{"message":"Used memory hits the high watermark(0.800000) of total system memory.","code":-1005},"latencyInUs":2635}]}

-参照 nebualGraph2.5.0 查询提示内存Used memory(178593436KB) hits the high watermark(0.800000) of total system memory(196268364KB). - #18,来自 zcs540061627 这篇帖子对graph.conf做了修改 配置也没生效

来,贴一下配置文件,可能是加错地方了。

    --system_memory_high_watermark_ratio = 1.0
    --local_conf=false
    --daemonize=true
    --pid_file=pids/nebula-graphd.pid
    --log_dir=logs
    --minloglevel=2
    --v=0

我的锅。。可以划去敏感的信息,把整个 graph 的配置贴一下吗

nebula-graphd.conf: |-
    --system_memory_high_watermark_ratio = 1.0
    --local_conf=false
    --daemonize=true
    --pid_file=pids/nebula-graphd.pid
    --log_dir=logs
    --minloglevel=2
    --v=0
    # Maximum seconds to buffer the log messages
    --logbufsecs=0
    # Whether to redirect stdout and stderr to separate output files
    --redirect_stdout=true
    # Destination filename of stdout and stderr, which will also reside in log_dir.
    --stdout_log_file=nebula-graphd.log
    --stderr_log_file=nebula-graphd.log
    # Copy log messages at or above this level to stderr in addition to logfiles. The numbers of severity levels INFO, WARNING, ERROR, and FATAL are 0, 1, 2, and 3, respectively.
    --stderrthreshold=2

    ########## networking ##########
    # Meta Server Address
    --meta_server_addrs=172.16.2.60:9559
    # Local ip
    --local_ip=172.16.2.62
    # Network device to listen on
    --listen_netdev=any
    # Port to listen on
    --port=9669
    # To turn on SO_REUSEPORT or not
    --reuse_port=false
    # Backlog of the listen socket, adjust this together with net.core.somaxconn
    --listen_backlog=1024
    # Seconds before the idle connections are closed, 0 for never closed
    --client_idle_timeout_secs=0
    # Seconds before the idle sessions are expired, 0 for no expiration
    --session_idle_timeout_secs=60000
    # The number of threads to accept incoming connections
    --num_accept_threads=1
    # The number of networking IO threads, 0 for # of CPU cores
    --num_netio_threads=0
    # The number of threads to execute user queries, 0 for # of CPU cores
    --num_worker_threads=0
    # HTTP service ip
    --ws_ip=0.0.0.0
    # HTTP service port
    --ws_http_port=19669
    # HTTP2 service port
    --ws_h2_port=19670
    # The default charset when a space is created
    --default_charset=utf8
    # The defaule collate when a space is created
    --default_collate=utf8_bin

    ########## authorization ##########
    # Enable authorization
    --enable_authorize=true

    ########## Authentication ##########
    # User login authentication type, password for nebula authentication, ldap for ldap authentication, cloud for cloud authentication
    --auth_type=password

你们是不是多机器部署的?是的话,所有的 graph 都要改下配置哈。等等,:thinking: @weiGaoCheng 说你们是单机部署的?理论上应该不用多处修改水位线的。

是的 我们是单机部署的,–local_conf=false 这个改成true也不生效

稍等,我喊个技术支持同学来哈。

好嘞 谢谢

–local_config=true 啊啊

1 个赞

OK 那我再试试

--system_memory_high_watermark_ratio = 1.0
--local_config=true

更改后仍未生效啊 , 别的配置有问题吗

要不用curl查询下配置有没有生效?参考:配置管理 - Nebula Graph Database 手册

才看到你是docker 部署,docker 是把参数用 cmd arg 传给 graphd 的优先级超过配置文件会覆盖同参数的文件里的配置,所以不要改文件,去改 compose 的 yaml 文件像这样

  graphd:
    image: vesoft/nebula-graphd:v2.0.0
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:9559
      - --port=9669
      - --ws_ip=graphd
      - --ws_http_port=19669
      - --ws_meta_http_port=19559
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
      - --system_memory_high_watermark_ratio=1.0
    depends_on:
      - metad0

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