-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
wal dir is not used in meta server #893
Comments
Just as you said, wal and data is in the same dir (see NebulaStore::newPart). We may clean outdated wal in background. Default wal_ttl is 86400s. |
@critical27 did you mean that outdated wal will first move to data/meta/nebula/0/wal ? |
In fact, when metad is a cluster, the wal will be used. :) |
yixinglu
pushed a commit
to yixinglu/nebula
that referenced
this issue
Jan 31, 2023
* Refactor to one part one rocksdb (vesoft-inc#896) * increment backup and restore (vesoft-inc#893) * increment backup * fix UT * restore process return parthost info * support drop multi snapshot * fix spaceId is empty * drop empty checkpoint directory * optimize * address pengweisong's comments * address critical27's comments confirm with Sophie * support clusterId in backupmeta (vesoft-inc#972) Co-authored-by: panda-sheep <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
according to rocksdb log, wal and data is in the same dir.
by there still have a wal dir . maybe the setting is wrong, wal should move to wal dir.
The text was updated successfully, but these errors were encountered: