Star

nebula2容器镜像从v2-preview-nightly升级到v2-nightly字后使用match查询出错

  • nebula 版本:v2.0.0beta
  • 部署方式(分布式 / 单机 / Docker / DBaaS):docker (镜像版本 v2-nightly)
  • 硬件信息
    • 磁盘( 必须为 SSD ,不支持 HDD)500G SSD
    • CPU、内存信息:40C,128G
  • 出问题的 Space 的创建方式:
  • 问题的具体描述
    镜像版本升级后,使用match查询无法正常返回。
    如在console中使用以下语句:

   match (v) where id(v) == "A8FD901F-4942-47D2-9954-F198AE44A2E3" return v;

报错内容如下:


2021/01/08 10:11:15 Loop error, *graph.ExecutionResponse error reading struct: *nebula.DataSet error reading struct: *nebula.Row error reading struct: *nebula.Value error reading struct: *nebula.Vertex error reading struct: error reading field 1: read tcp 127.0.0.1:45291->127.0.0.1:3699: i/o timeout

在nebula-graph前端页面进行match查询也是运行长时间后,无返回值。估计后端也是上述错误。

docker-compose.yaml文件如下:

version: '3.4'
services:
  metad0:
    image: vesoft/nebula-metad:v2-nightly
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:45500,metad1:45500,metad2:45500
      - --local_ip=metad0
      - --ws_ip=metad0
      - --port=45500
      - --ws_http_port=11000
      - --data_path=/data/meta
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://metad0:11000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - 45500
      - 11000
      - 11002
    volumes:
      - ./data/meta0:/data/meta
      - ./logs/meta0:/logs
    networks:
      - nebula-net
    restart: on-failure
    cap_add:
      - SYS_PTRACE

  metad1:
    image: vesoft/nebula-metad:v2-nightly
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:45500,metad1:45500,metad2:45500
      - --local_ip=metad1
      - --ws_ip=metad1
      - --port=45500
      - --ws_http_port=11000
      - --data_path=/data/meta
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://metad1:11000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - 45500
      - 11000
      - 11002
    volumes:
      - ./data/meta1:/data/meta
      - ./logs/meta1:/logs
    networks:
      - nebula-net
    restart: on-failure
    cap_add:
      - SYS_PTRACE

  metad2:
    image: vesoft/nebula-metad:v2-nightly
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:45500,metad1:45500,metad2:45500
      - --local_ip=metad2
      - --ws_ip=metad2
      - --port=45500
      - --ws_http_port=11000
      - --data_path=/data/meta
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://metad2:11000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - 45500
      - 11000
      - 11002
    volumes:
      - ./data/meta2:/data/meta
      - ./logs/meta2:/logs
    networks:
      - nebula-net
    restart: on-failure
    cap_add:
      - SYS_PTRACE

  storaged0:
    image: vesoft/nebula-storaged:v2-nightly
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:45500,metad1:45500,metad2:45500
      - --local_ip=storaged0
      - --ws_ip=storaged0
      - --port=44500
      - --ws_http_port=12000
      - --data_path=/data/storage
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://storaged0:12000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - 44500
      - 12000
      - 12002
    volumes:
      - ./data/storage0:/data/storage
      - ./logs/storage0:/logs
    networks:
      - nebula-net
    restart: on-failure
    cap_add:
      - SYS_PTRACE

  storaged1:
    image: vesoft/nebula-storaged:v2-nightly
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:45500,metad1:45500,metad2:45500
      - --local_ip=storaged1
      - --ws_ip=storaged1
      - --port=44500
      - --ws_http_port=12000
      - --data_path=/data/storage
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://storaged1:12000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - 44500
      - 12000
      - 12002
    volumes:
      - ./data/storage1:/data/storage
      - ./logs/storage1:/logs
    networks:
      - nebula-net
    restart: on-failure
    cap_add:
      - SYS_PTRACE

  storaged2:
    image: vesoft/nebula-storaged:v2-nightly
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:45500,metad1:45500,metad2:45500
      - --local_ip=storaged2
      - --ws_ip=storaged2
      - --port=44500
      - --ws_http_port=12000
      - --data_path=/data/storage
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://storaged2:12000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - 44500
      - 12000
      - 12002
    volumes:
      - ./data/storage2:/data/storage
      - ./logs/storage2:/logs
    networks:
      - nebula-net
    restart: on-failure
    cap_add:
      - SYS_PTRACE

  graphd:
    image: vesoft/nebula-graphd:v2-nightly
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:45500,metad1:45500,metad2:45500
      - --port=3699
      - --ws_ip=graphd
      - --ws_http_port=13000
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://graphd:13000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - "3699:3699"
      - 13000
      - 13002
    volumes:
      - ./logs/graph:/logs
    networks:
      - nebula-net
    restart: on-failure
    cap_add:
      - SYS_PTRACE

  graphd1:
    image: vesoft/nebula-graphd:v2-nightly
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:45500,metad1:45500,metad2:45500
      - --port=3699
      - --ws_ip=graphd1
      - --ws_http_port=13000
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://graphd1:13000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - 3699
      - 13000
      - 13002
    volumes:
      - ./logs/graph1:/logs
    networks:
      - nebula-net
    restart: on-failure
    cap_add:
      - SYS_PTRACE

  graphd2:
    image: vesoft/nebula-graphd:v2-nightly
    environment:
      USER: root
      TZ:   "${TZ}"
    command:
      - --meta_server_addrs=metad0:45500,metad1:45500,metad2:45500
      - --port=3699
      - --ws_ip=graphd2
      - --ws_http_port=13000
      - --log_dir=/logs
      - --v=0
      - --minloglevel=0
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://graphd2:13000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - 3699
      - 13000
      - 13002
    volumes:
      - ./logs/graph2:/logs
    networks:
      - nebula-net
    restart: on-failure
    cap_add:
      - SYS_PTRACE

networks:
  nebula-net:

启动后的进程如下:

稍微给你排版了下,\ 这个符号是反解析用的 :joy: 你如果要用代码段格式包裹东西的话,需要去掉的。

1赞

yml更新了端口号,使用新的端口号建议删除之前的数据重新导入。

1赞

2021/01/08 10:11:15 Loop error, *graph.ExecutionResponse error reading struct: *nebula.DataSet error reading struct: *nebula.Row error reading struct: *nebula.Value error reading struct: *nebula.Vertex error reading struct: error reading field 1: read tcp 127.0.0.1:45291->127.0.0.1:3699: i/o timeout

感谢您的反馈,新版本的vertex和edge数据结构有所变动,你需要升级下console。

1赞

多谢各位,确实是web-docker和console-docker的版本问题,同步更新到最新版本后,执行可以正常返回了

1赞

浙ICP备20010487号