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

receiver-based connection undefined behavior #58

Closed
CodingCat opened this issue Apr 10, 2017 · 1 comment
Closed

receiver-based connection undefined behavior #58

CodingCat opened this issue Apr 10, 2017 · 1 comment
Assignees
@CodingCat

Comments

@CodingCat
Copy link
Contributor

In the implementation of receiver-based connection, there is a race condition when the receiver is restarted.

The current implementation restart a new receiver in a new thread (within Spark Streaming internal) and in the original MessageHandler thread, it will close the FileSystem

This is an undefined behavior according to the API doc of HDFS

https://hadoop.apache.org/docs/current/api/org/apache/hadoop/fs/FileSystem.html#close--

Urgent fixes are needed
@CodingCat CodingCat self-assigned this Apr 10, 2017
@CodingCat
Copy link
Contributor Author

#59

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

@CodingCat CodingCat

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CodingCat