You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of storing block files directly in the local destination, we wish to modify the block writers as follows:
Store block files initially in an "unverified" folder, just flat with full file name.
A separate process initiated when a result is published by the verification service will move the file.
When a "verified" result is published this will move the now-verified block (only) to its proper destination
When an "unverified" result is published, this will remove the now-failed block (only).
When other result types are published this sub-service will only react if appropriate.
On startup, the persistence service will remove all unverified files.
This might be accomplished by using a folder on tmpfs, which is managed in-memory by the kernel and would significantly improve reliability and performance.
All other persistence service elements, and all archive services, will operate only on the trie structure folders containing verified block files.
The text was updated successfully, but these errors were encountered:
ata-nas
added
New Feature
A new feature, service, or documentation. Major changes that are not backwards compatible.
P0
An issue impacting production environments or impacting multiple releases or multiple individuals.
Block Node
Issues/PR related to the Block Node.
Alpha-0
Issues related to features designated for the Alpha-0 release
labels
Feb 5, 2025
ata-nas
changed the title
Add unverified marker for persisted block files
feat: add unverified marker for persisted block files
Feb 5, 2025
jsync-swirlds
removed
New Feature
A new feature, service, or documentation. Major changes that are not backwards compatible.
Block Node
Issues/PR related to the Block Node.
Alpha-0
Issues related to features designated for the Alpha-0 release
labels
Feb 5, 2025
Instead of storing block files directly in the local destination, we wish to modify the block writers as follows:
The text was updated successfully, but these errors were encountered: