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

Race condition from client thinking block is complete before namenode #81

Closed
pelmers opened this issue Nov 17, 2016 · 2 comments
Closed

Race condition from client thinking block is complete before namenode #81

pelmers opened this issue Nov 17, 2016 · 2 comments
Assignees
@pelmers @Vegetable26

Comments

@pelmers
Copy link
Contributor

pelmers commented Nov 17, 2016

The data transfer server may complete its final acknowledge before blockReceived returns because acknowledgements are returned on a separate thread.

Then the client thinks its data is complete so it will complete on the namenode, but there is a chance the namenode did not process blockReceived in time and will fail.
@pelmers
Copy link
Contributor Author

pelmers commented Nov 17, 2016

just noticed #80, maybe these could be related?

@Vegetable26
Copy link
Contributor

This issue is actually an issue with LeaseManager. See #87

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pelmers pelmers

@Vegetable26 Vegetable26

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pelmers @Vegetable26