-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-8161] Set externalBlockStoreInitialized to be true, after ExternalBlockStore is initialized #6702
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
|
Good catch. LGTM |
|
Test build #34429 has finished for PR 6702 at commit
|
|
should we add some tests in |
|
@squito |
|
ping.... |
|
@andrewor14 @aarondav |
|
ping ....... |
|
@shimingfei I think people are busy with Spark Summit. |
|
OK, I see. Thanks. |
|
LGTM. I agree we should have a regression test, but we shouldn't block the fix on it. The code before was clearly wrong since we never set the flag to true. |
|
LGMT |
|
Merging into master 1.4 |
…rnalBlockStore is initialized externalBlockStoreInitialized is never set to be true, which causes the blocks stored in ExternalBlockStore can not be removed. Author: Mingfei <[email protected]> Closes #6702 from shimingfei/SetTrue and squashes the following commits: add61d8 [Mingfei] Set externalBlockStoreInitialized to be true, after ExternalBlockStore is initialized (cherry picked from commit 7ad8c5d) Signed-off-by: Andrew Or <[email protected]>
…rnalBlockStore is initialized externalBlockStoreInitialized is never set to be true, which causes the blocks stored in ExternalBlockStore can not be removed. Author: Mingfei <[email protected]> Closes apache#6702 from shimingfei/SetTrue and squashes the following commits: add61d8 [Mingfei] Set externalBlockStoreInitialized to be true, after ExternalBlockStore is initialized
externalBlockStoreInitialized is never set to be true, which causes the blocks stored in ExternalBlockStore can not be removed.