-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-18342] Make rename failures fatal in HDFSBackedStateStore #15804
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
Conversation
|
cc @tdas |
|
Test build #68317 has finished for PR 15804 at commit
|
| val deltaFiles = allFiles.filter { file => | ||
| file.version > snapshotFile.version && file.version <= version | ||
| } | ||
| }.toList |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the line returns a Stream which is a Scala Iterator like class, therefore the logging below doesn't work
|
Test build #68346 has finished for PR 15804 at commit
|
|
|
||
| /** Fake FileSystem to test whether the method `fs.exists` is called during | ||
| * `DataSource.resolveRelation`. | ||
| */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wrong docs.
| } | ||
| } | ||
|
|
||
| test("commit fails when rename fails") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you add the jira number here.
|
looks good. to minor comments. |
|
@tdas Addressed |
|
Test build #68356 has finished for PR 15804 at commit
|
|
LGTM. |
|
Test build #68358 has finished for PR 15804 at commit
|
|
Merge this to master, 2.1 and 2.0 |
## What changes were proposed in this pull request? If the rename operation in the state store fails (`fs.rename` returns `false`), the StateStore should throw an exception and have the task retry. Currently if renames fail, nothing happens during execution immediately. However, you will observe that snapshot operations will fail, and then any attempt at recovery (executor failure / checkpoint recovery) also fails. ## How was this patch tested? Unit test Author: Burak Yavuz <brkyvz@gmail.com> Closes #15804 from brkyvz/rename-state. (cherry picked from commit 6f7ecb0) Signed-off-by: Tathagata Das <tathagata.das1565@gmail.com>
## What changes were proposed in this pull request? If the rename operation in the state store fails (`fs.rename` returns `false`), the StateStore should throw an exception and have the task retry. Currently if renames fail, nothing happens during execution immediately. However, you will observe that snapshot operations will fail, and then any attempt at recovery (executor failure / checkpoint recovery) also fails. ## How was this patch tested? Unit test Author: Burak Yavuz <brkyvz@gmail.com> Closes #15804 from brkyvz/rename-state. (cherry picked from commit 6f7ecb0) Signed-off-by: Tathagata Das <tathagata.das1565@gmail.com>
## What changes were proposed in this pull request? If the rename operation in the state store fails (`fs.rename` returns `false`), the StateStore should throw an exception and have the task retry. Currently if renames fail, nothing happens during execution immediately. However, you will observe that snapshot operations will fail, and then any attempt at recovery (executor failure / checkpoint recovery) also fails. ## How was this patch tested? Unit test Author: Burak Yavuz <brkyvz@gmail.com> Closes apache#15804 from brkyvz/rename-state.
What changes were proposed in this pull request?
If the rename operation in the state store fails (
fs.renamereturnsfalse), the StateStore should throw an exception and have the task retry. Currently if renames fail, nothing happens during execution immediately. However, you will observe that snapshot operations will fail, and then any attempt at recovery (executor failure / checkpoint recovery) also fails.How was this patch tested?
Unit test