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.

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

Does Cuju guarantee consistency between checkpoints and shared persistent storage? #54

Open
mingnus opened this issue Dec 13, 2019 · 1 comment
Labels

Comments

@mingnus
Copy link

mingnus commented Dec 13, 2019

Hi,

I'm new to VM fault tolerance. I'm not sure if Cuju guarantees the shared storage state or not. Some fault-tolerance solutions use either storage snapshot, or a private storage for the secondary VM, to preserve the storage state while checkpointing. How does Cuju handle this issue? Alternatively, is there any best practice for using shared storage? Thanks.

@PJTPJT
Copy link
Collaborator

PJTPJT commented Jan 21, 2020

Actually, we use shared storage for primary and secondary VM and only primary VM can write the storage. And we buffered disk write operations when the memory state was not fully backed up to the secondary side.
In other words, when backed up finished, we release the buffered disk write operations to the shared storage. So it can make the shared storage state consistent with backed up state

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants