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

Lost object handling in meta #3140

Open
roman-khimov opened this issue Feb 16, 2025 · 0 comments
Open

Lost object handling in meta #3140

roman-khimov opened this issue Feb 16, 2025 · 0 comments
Labels
enhancement Improving existing functionality I4 No visible changes neofs-storage Storage node application issues S4 Routine U3 Regular

Comments

@roman-khimov
Copy link
Member

Objects can be lost. Three machines going down with REP 3 is exactly that case. This fact should be reflected in the contract, signed by all current container machines. Then the object entry can be dropped from the metabase.
@roman-khimov roman-khimov added enhancement Improving existing functionality I4 No visible changes neofs-storage Storage node application issues S4 Routine U3 Regular labels Feb 16, 2025
@roman-khimov roman-khimov mentioned this issue Feb 16, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Improving existing functionality I4 No visible changes neofs-storage Storage node application issues S4 Routine U3 Regular
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@roman-khimov