日志无法限制大小,每天产生大量日志 导致磁盘不可用

提问参考模版:

  • nebula 版本:(为节省回复者核对版本信息的时间,首次发帖的版本信息记得以截图形式展示)
  • 部署方式(分布式 / 单机 / Docker / DBaaS):k8s集群
I0408 16:54:26.834738    59 Cpp2Worker.cpp:157] Cpp2Worker: created connection for socket 291
I0408 16:54:26.834750    59 AsyncSocket.cpp:2180] this=0x7fae5e230400, AsyncSocket::handleRead() got 234 bytes
I0408 16:54:26.834807    59 AsyncSocket.cpp:2180] this=0x7fae5e230400, AsyncSocket::handleRead() got -2 bytes
I0408 16:54:26.834834    43 RaftPart.cpp:1717] [Port: 9560, Space: 0, Part: 0] The current role is Follower
I0408 16:54:26.834867    43 RaftPart.cpp:1662] [Port: 9560, Space: 0, Part: 0] Writing log [704050, 704050] to WAL
I0408 16:54:26.834877    43 Part.cpp:368] [Port: 9560, Space: 0, Part: 0] logId 704050, termId 4, clusterId 0
I0408 16:54:26.834895    43 AtomicLogBuffer.h:352] current node firstLogId = 703997, the seeking logId = 704049
I0408 16:54:26.834921    43 Part.cpp:206] [Port: 9560, Space: 0, Part: 0] Skip the heartbeat!
I0408 16:54:26.834964    43 AtomicLogBuffer.h:374] Release ref, readers = 1
I0408 16:54:26.834977    43 RaftPart.cpp:1688] [Port: 9560, Space: 0, Part: 0] Follower succeeded committing log 704049 to 704049
I0408 16:54:26.835209    59 AsyncSocket.cpp:2180] this=0x7fae5e230400, AsyncSocket::handleRead() got 0 bytes
I0408 16:54:26.835228    59 Cpp2Connection.cpp:576] Channel 192.168.201.26:46482 closed: N6apache6thrift9transport19TTransportExceptionE: Channel Closed
I0408 16:54:26.836558    60 AsyncSocket.cpp:2180] this=0x7fae5d42fc00, AsyncSocket::handleRead() got 13 bytes
I0408 16:54:26.836604    60 AsyncSocket.cpp:2180] this=0x7fae5d42fc00, AsyncSocket::handleRead() got 13 bytes
I0408 16:54:26.836619    60 Cpp2Worker.cpp:142] Cpp2Worker: Creating connection for socket 291
I0408 16:54:26.836656    60 Cpp2Worker.cpp:157] Cpp2Worker: created connection for socket 291
I0408 16:54:26.836673    60 AsyncSocket.cpp:2180] this=0x7fae5d42fc00, AsyncSocket::handleRead() got 234 bytes
I0408 16:54:26.836724    60 AsyncSocket.cpp:2180] this=0x7fae5d42fc00, AsyncSocket::handleRead() got -2 bytes
I0408 16:54:26.836736    43 RaftPart.cpp:1717] [Port: 9560, Space: 0, Part: 0] The current role is Follower
I0408 16:54:26.836756    43 RaftPart.cpp:1662] [Port: 9560, Space: 0, Part: 0] Writing log [704051, 704051] to WAL
I0408 16:54:26.836766    43 Part.cpp:368] [Port: 9560, Space: 0, Part: 0] logId 704051, termId 4, clusterId 0
I0408 16:54:26.836779    43 AtomicLogBuffer.h:352] current node firstLogId = 703997, the seeking logId = 704050
I0408 16:54:26.836815    43 AtomicLogBuffer.h:374] Release ref, readers = 1
I0408 16:54:26.836825    43 RaftPart.cpp:1688] [Port: 9560, Space: 0, Part: 0] Follower succeeded committing log 704050 to 704050
I0408 16:54:26.837041    60 AsyncSocket.cpp:2180] this=0x7fae5d42fc00, AsyncSocket::handleRead() got 0 bytes
I0408 16:54:26.837074    60 Cpp2Connection.cpp:576] Channel 192.168.201.26:46486 closed: N6apache6thrift9transport19TTransportExceptionE: Channel Closed
I0408 16:54:26.839453    61 AsyncSocket.cpp:2180] this=0x7fae5c618000, AsyncSocket::handleRead() got 13 bytes
I0408 16:54:26.839496    61 AsyncSocket.cpp:2180] this=0x7fae5c618000, AsyncSocket::handleRead() got 13 bytes
I0408 16:54:26.839507    61 Cpp2Worker.cpp:142] Cpp2Worker: Creating connection for socket 291
I0408 16:54:26.839537    61 Cpp2Worker.cpp:157] Cpp2Worker: created connection for socket 291
I0408 16:54:26.839550    61 AsyncSocket.cpp:2180] this=0x7fae5c618000, AsyncSocket::handleRead() got 234 bytes
I0408 16:54:26.839584    61 AsyncSocket.cpp:2180] this=0x7fae5c618000, AsyncSocket::handleRead() got -2 bytes
I0408 16:54:26.839640    43 RaftPart.cpp:1717] [Port: 9560, Space: 0, Part: 0] The current role is Follower
I0408 16:54:26.839668    43 RaftPart.cpp:1662] [Port: 9560, Space: 0, Part: 0] Writing log [704052, 704052] to WAL
I0408 16:54:26.839679    43 Part.cpp:368] [Port: 9560, Space: 0, Part: 0] logId 704052, termId 4, clusterId 0
I0408 16:54:26.839715    43 AtomicLogBuffer.h:352] current node firstLogId = 703997, the seeking logId = 704051
I0408 16:54:26.839751    43 AtomicLogBuffer.h:374] Release ref, readers = 1
I0408 16:54:26.839763    43 RaftPart.cpp:1688] [Port: 9560, Space: 0, Part: 0] Follower succeeded committing log 704051 to 704051
I0408 16:54:26.839977    61 AsyncSocket.cpp:2180] this=0x7fae5c618000, AsyncSocket::handleRead() got 0 bytes
I0408 16:54:26.839999    61 Cpp2Connection.cpp:576] Channel 192.168.201.26:46490 closed: N6apache6thrift9transport19TTransportExceptionE: Channel Closed
I0408 16:54:26.922730    51 RaftPart.cpp:1321] [Port: 9560, Space: 0, Part: 0] Schedule new task

你看下日志目录下面是那个服务产生的日志比较多,然后将show configs 结果截图下

https://docs.nebula-graph.com.cn/2.0/2.quick-start/0.FAQ/#_4
https://docs.nebula-graph.com.cn/2.0/5.configurations-and-logs/2.log-management/logs/

是helm部署的 镜像是vesoft/nebula-storaged:v2-nightly

# Log level, 0, 1, 2, 3 for INFO, WARNING, ERROR, FATAL respectively -
-minloglevel=3
# Verbose log level, 1, 2, 3, 4, the higher of the level, the more verbose of the logging
–v=1 还是很多日志

一般minloglevel和v都是0足够了

你配置文件没有配置 local_config 为 true 的话,首次部署的时候,就把你部署的配置写到metad了,你后面改配置文件也是无效的,你可以 show configs 看下这两个日志参数,调整让它为 v=0,minloglevel=0