failed to write ingestion access log

[golsk]

{"level":"error","module":"LIAISON-GRPC","error":"access log is full","time":"2025-11-08T08:37:27Z","message":"failed to write ingestion access log"}

[wu-sheng]

What is your case? A single error message doesn't help.
We are going to release 0.9 soon, with fully test report.

[golsk]

1、version

component	version
skywalking-oap	10.2.0
banyanDB	0.8.0

2、deploy

docker-compose

banyanDB liasion

services:
  banyanDB:
    container_name: banyanDB
    image: registry.ztoky.cn/apache/skywalking-banyandb:0.7.0
    network_mode: host
    restart: always
    extra_hosts:
      - "etcd01:10.202.12.211"
      - "etcd02:10.202.12.212"
      - "etcd03:10.202.12.213"
    environment:
      - TZ=Asia/Shanghai
    volumes:
      - ./data:/banyanDB/data
      - ./cert:/banyanDB/cert
    command:
      - '--max-recv-msg-size=209715200'
      - '--node-host-provider=ip'
      - '--observability-modes=native'
      - '--etcd-endpoints=etcd01:2379,etc02:2379,etcd03:2379'
      - '--etcd-tls-ca-file=/banyanDB/cert/ca.crt'
      - '--etcd-tls-cert-file=/banyanDB/cert/client.crt'
      - '--etcd-tls-key-file=/banyanDB/cert/client.key'
      - 'liaison'
      - '--access-log-root-path=/banyanDB/data'
      - '--enable-ingestion-access-log'
      - '--node-registry-timeout=150s'

banyanDB data

services:
  banyanDB:
    container_name: banyanDB
    image: registry.ztoky.cn/apache/skywalking-banyandb:0.7.0
    network_mode: host
    restart: always
    extra_hosts:
      - "etcd01:10.202.12.211"
      - "etcd02:10.202.12.212"
      - "etcd03:10.202.12.213"
    environment:
      - TZ=Asia/Shanghai
    volumes:
      - ./data:/banyanDB/data
      - ./cert:/banyanDB/cert
    command:
      - '--logging-env=dev'
      - '--logging-level=debug'
      - '--node-host-provider=ip'
      - '--observability-modes=native'
      - '--etcd-endpoints=etcd01:2379,etc02:2379,etcd03:2379'
      - '--etcd-tls-ca-file=/banyanDB/cert/ca.crt'
      - '--etcd-tls-cert-file=/banyanDB/cert/client.crt'
      - '--etcd-tls-key-file=/banyanDB/cert/client.key'
      - data
      - '--max-recv-msg-size=209715200'

skywalking

services:
  sw-oap-server:
    image: harbor.dev.ztoeco.com/library/apache/skywalking-oap-server:10.2.0
    container_name: sw-oap
    restart: always
    network_mode: host
    extra_hosts:
      - "message-deliver.ztoeco.com:10.196.40.65"
    environment:
      - "TZ=Asia/Shanghai"
      - "JAVA_OPTS=-Xms8g -Xmx8g -XX:MetaspaceSize=256m -XX:MaxMetaspaceSize=1g -XX:+UseG1GC -XX:G1HeapRegionSize=16m -XX:InitiatingHeapOccupancyPercent=40 -XX:MaxGCPauseMillis=100 -XX:+UnlockExperimentalVMOptions -XX:G1MaxNewSizePercent=70 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=../logs/heapdump.hprof"
      - "SW_CLUSTER=zookeeper"
      - "SW_CORE_ROLE=Receiver"
      - "SW_CLUSTER_ZK_HOST_PORT=10.202.16.204:2181,10.202.16.205:2181,10.202.16.206:2181"
      - "SW_CORE_GRPC_HOST=10.202.16.204"
      - "SW_STORAGE=banyandb"
      - "SW_STORAGE_BANYANDB_TARGETS=10.202.12.83:17912,10.202.12.84:17912,10.202.12.85:17912"
      - "SW_TELEMETRY=prometheus"
      - "SW_HEALTH_CHECKER=default"
      - "SW_CONFIGURATION=nacos"
      - "SW_CONFIG_NACOS_SERVER_ADDR=10.202.16.163"
      - "SW_CONFIG_NACOS_SERVER_PORT=8848"
      - "SW_CONFIG_NACOS_SERVER_GROUP=cuckoo_skywalking"
      - "SW_CONFIG_NACOS_SERVER_NAMESPACE=skywalking"
      - "SW_CONFIG_NACOS_PERIOD=60"
      - "SW_CONFIG_NACOS_USERNAME=nacos"
      - "SW_CONFIG_NACOS_PASSWORD=uat_nacos221"
    volumes:
      - ./conf:/skywalking/config
      - ./logs:/skywalking/logs

3、error

log	msg
liaison	{"level":"error","module":"LIAISON-GRPC","error":"access log is full","time":"2025-11-08T08:58:38Z","message":"failed to write ingestion access log"}
data	2025-11-08T08:56:30Z | ERROR | mnt/ssd/skywalking-banyandb/banyand/queue/sub/sub.go:124 > failed to send write response error="rpc error: code = Unavailable desc = transport is closing" module=SERVER-QUEUE-SUB written="topic:"v1:measure-write" message_id:1762592190561730491 body:{[type.googleapis.com/banyandb.measure.v1.InternalWriteRequest]:{series_hash:"%\xc3ڬ\x14H\x88\x11\xfd\x839\xbf\xab\xd6\xeb\xb4" entity_values:{str:{value:"ZmVlLXBvc3QtY2xpZW50X3VhdA==.1"}} request:{metadata:{group:"day" name:"service_sidecar_internal_resp_latency_nanos_day" mod_revision:8347} data_point:{timestamp:{seconds:1762531200} tag_families:{tags:{null:NULL_VALUE} tags:{null:NULL_VALUE} tags:{null:NULL_VALUE} tags:{null:NULL_VALUE} tags:{null:NULL_VALUE} tags:{null:NULL_VALUE}} tag_families:{tags:{str:{value:"ZmVlLXBvc3QtY2xpZW50X3VhdA==.1"}}} fields:{int:{}} fields:{int:{value:319}} fields:{int:{}}version:8197415144435} message_id:8197415144435}}} batch_mod:true"

[wu-sheng]

I am seeing you mentioned 10.2+db 0.78 but the image(from your private repo) is 0.7. What is your setup? 10.2 requires upstream 0.8 release of DB.

[golsk]

I have tried both 0.7.0 and 0.8.0, but I always get the same error

[wu-sheng]

10.2 works with 0.8, not 0.7. And as I mentioned, 10.3 will work with 0.9, which should be much better.

[golsk]

感谢大佬百忙之中的及时回复，同时期待新版本的发布。