Star

使用match i/o timeout

  • nebula 版本:v2.0.0-alpha
  • 部署方式(分布式 / 单机 / Docker / DBaaS): docker
  • 硬件信息
    • 磁盘( 必须为 SSD ,不支持 HDD):ssd
    • CPU、内存信息:12+8
  • 出问题的 Space 的创建方式:执行 describe space xxx;
  • 问题的具体描述
(root@nebula) [(none)]> describe space nba
+----+-------+------------------+----------------+---------+------------+-------------------+
| ID | Name  | Partition Number | Replica Factor | Charset | Collate    | Vid Type          |
+----+-------+------------------+----------------+---------+------------+-------------------+
| 1  | "nba" | 10               | 1              | "utf8"  | "utf8_bin" | "FIXED_STRING(8)" |
+----+-------+------------------+----------------+---------+------------+-------------------


(root@nebula) [nba]> GO FROM "00000100" OVER follow
+-------------+
| follow._dst |
+-------------+
| "00000101"  |
+-------------+
| "00000102"  |
+-------------+


(root@nebula) [nba]> match (v) where id(v)=="00000100"  return v
2021/01/06 07:12:23 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 172.18.0.11:42220->172.18.0.5:3699: **i/o timeout**

已知bug,用beta试试看?

怎么安装 beta有没有教程 ,我使用docker-compose 安装的,。不应该是直接安装 最新的beta版本吗?

docker-compose的话有文档的,直接用nightly就行了,master默认是最新的

1、拉最新镜像
docker-compose pull

2、用新镜像重启服务
docker-compose down && docker-compose up -d

:smirk:

怎么成这样了

刚连接上还是显示这个
image

镜像信息

刚边上显示的内容是正常的,你可以更新一下你的console,你最后一个镜像是V2-preview-nightly,这个不是最新的了

目测是没有选主成功,balance data试试呢

不行啊, 我另外三个都没上线是咋回事

数据问题,另外跟踪

看上去像是配置问题
通常storage使用的端口是44500
能否贴出来docker compose配置?


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

这部分够吗?

你用的是nightly还是alpha,nightly有个配置问题我们正在修

REPOSITORY                      TAG                  IMAGE ID       CREATED        SIZE
vesoft/nebula-console           v2-nightly           4a6922f28c87   9 hours ago    14.4MB
vesoft/nebula-graphd            v2-nightly           692bd91584ea   32 hours ago   292MB
vesoft/nebula-storaged          v2-nightly           eea6993270c5   32 hours ago   296MB
vesoft/nebula-metad             v2-nightly           483b91827aea   32 hours ago   295MB
vesoft/nebula-console           <none>               5ae37bb069c3   33 hours ago   14.4MB
vesoft/nebula-graphd            <none>               44fced1d2539   6 days ago     292MB
vesoft/nebula-metad             <none>               d74f4e26dd89   7 days ago     295MB

浙ICP备20010487号