-
Notifications
You must be signed in to change notification settings - Fork 232
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
can we have the option to use localCheckpoint instead of checkpoint? #429
Comments
+1 on this, we swapped to GraphX algorithm because we don't want to checkpoint in S3 and Kubernetes Sparks typically runs without an HDFS Not sure about GraphX vs GraphFrames performance, we didn't see impact in mock tests (but our graphs usually dont very long "paths"), would be nice if someone knows about any benchmark. Btw we had to revert to GraphFrames because GraphX is buggy in our system (i.e. wrong results). For those interested, adding a guide on how we added localCheckpoint (maybe we'll push this to this repo, but still under testing and we are not contributors here, so would need time to adapt the test we delete, which should be fairly easy). It passes all other tests. I'm doing testing as of now, but tbh this should be even safer than our default mechanism since S3 has some consistency issues...
PS: If anyone is willing, feel free to push it to the repo (aka create a pullrequest) without asking me |
Hello,
can we have the option to use localCheckpoint instead of checkpoint?
In fact in our project we do not have access to put setCheckpointDir due to access limitation but localCheckpoint is working fine.
It would be good to have this feature available?
The text was updated successfully, but these errors were encountered: