Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[venus] venus节点运行badger超过2T且metadata大于400M，可能会影响到节点同步 #6085

Open
1 of 7 tasks
cloudxin opened this issue Aug 2, 2023 · 0 comments
Open
1 of 7 tasks

[venus] venus节点运行badger超过2T且metadata大于400M，可能会影响到节点同步 #6085

cloudxin opened this issue Aug 2, 2023 · 0 comments
Labels
C-bug Category: This is a bug CU-force-community Category: from force community P1 High - we should be working on this now or in the immediate future

Comments

@cloudxin
Copy link

cloudxin commented Aug 2, 2023

Sophon Service / 智子服务

  • venus
  • sophon-messager
  • sophon-miner
  • sophon-auth
  • sophon-gateway
  • sophon-co
  • 文档 / docs

Version / 版本

{
	"Version": "1.12.0+git.60ff3060"
}

Describe the Bug / 描述

节点磁盘充足的情况下，venus的repo目录下badger在增长到2T以上时，且metadata在增长到400M时，重启后节点无法同步。需要清空metadata目录后，重启节点可以恢复正常同步。

Logging Information / 日志

-

Repo Steps / 重现步骤

No response
@cloudxin cloudxin added the C-bug Category: This is a bug label Aug 2, 2023
@Fatman13 Fatman13 added the CU-force-community Category: from force community label Aug 9, 2023
@elvin-du elvin-du added the P1 High - we should be working on this now or in the immediate future label Aug 11, 2023
@Fatman13 Fatman13 changed the title [venus] venus节点运行badger超过2T且metadata大于400M，可能会影响到节点同步 [venus] venus节点运行badger超过2T且metadata大于400M，可能会影响到节点同步 Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-bug Category: This is a bug CU-force-community Category: from force community P1 High - we should be working on this now or in the immediate future
Projects
Venus Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Fatman13 @elvin-du @cloudxin