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

S3 restore cancellation issue #153

Open
ferhatsb opened this issue Dec 17, 2014 · 0 comments
Open

S3 restore cancellation issue #153

ferhatsb opened this issue Dec 17, 2014 · 0 comments

Comments

@ferhatsb
Copy link

Hi,

Noticed today if you delete an index which is still being restored (offered way to cancel an index restore) BlobContainer still keeps reading incoming stream.

If you have very large index, you can not start another restore operation before waiting it to complete even result will be simply nothing.

I experience this with S3 but probably it is a case for all other restore options.
@ferhatsb ferhatsb changed the title S3 Data transfer after deleting index being restored S3 recovery cancellation issue Dec 17, 2014
@ferhatsb ferhatsb changed the title S3 recovery cancellation issue S3 restore cancellation issue Dec 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ferhatsb