gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Filer Metadata Events (markdown)

Chris Lu 2022-03-29 02:03:19 -07:00
parent 28f2ba2edf
commit 5c3d197127
1 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
Filer-Metadata-Events.md

@ -81,10 +81,11 @@ The `SubscribeMetadataResponse` contains `EventNotification`, which contains `ol
* Update Event: `old_entry` is not null, and `new_entry` is not null. * Update Event: `old_entry` is not null, and `new_entry` is not null.
* Rename Event: similar to Update Event, but also need `SubscribeMetadataResponse.directory` and `EventNotification.new_parent_path`. * Rename Event: similar to Update Event, but also need `SubscribeMetadataResponse.directory` and `EventNotification.new_parent_path`.
## Purging Metadata ## Purging Metadata Logs
It is safe to delete the metadata files for now. However, future development will rely on these metadata events to implement new features, such as: It is ok to delete the metadata logs. However, many features rely on these metadata events, such as:
* Async filer replication (to replace existing dependency on other message queue, e.g., Kafka) * Async filer replication
* Recover deleted files * Sync metadata with `weed mount`
* Snapshot * Async filer metadata backup
* Filer backup
The metadata should not take too much space. Just leave it there. So better not to mess with the metadata logs, which should not take too much space. Just leave them there.