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.

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

Describe well-known X-Headers #118

Merged
merged 1 commit into from
Jan 11, 2021

Conversation

realloc
Copy link

@realloc realloc commented Jan 11, 2021

When object can't be found using current network map, there is a chance to find it using netmap versions from previous epochs.

By default only current netmap is used. Well-known X-Headers can be used to set the specific netmap version and limit how deep into the past the node can go in the search of an object.

Closes #117

// affect system behaviour:
//
// * __NEOFS__NETMAP_EPOCH \
// Netmap epoch to use for object placement calculation. If set to '0' or not
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice to specify format of the string value for both NETMAP_EPOCH and NETMAP_LOOKUP_DEPTH. E.g. add Value represented as decimal number lines.

When object can't be found using current network map, there is a chance to find
it using netmap versions from previous epochs.

By default only current netmap is used. Well-known X-Headers can be used to set
the specific netmap version and limit how deep into the past the node can go in
the search of an object.

Signed-off-by: Stanislav Bogatyrev <stanislav@nspcc.ru>
@realloc realloc merged commit fac353b into nspcc-dev:master Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Describe well-known x-headers for request epoch number
3 participants