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

Data is resurrected after a server restart #342

Merged
merged 7 commits into from
Mar 26, 2014
Merged

Conversation

jvshahid
Copy link
Contributor

  • Write data into a database
  • Drop the database
  • Create the database
  • Run query and see if data is still there

@pauldix pauldix added this to the 0.5.0 milestone Mar 14, 2014
@jvshahid jvshahid modified the milestones: 0.5.1, 0.5.0 Mar 24, 2014
Deleting data without creating a wal bookmark will cause the log to
replay some requests that where written before the delete happened,
causing the data to be resurrected. This change makes sure we create a
bookmark right before we delete the data to make sure that any write
before the delete will not be replayed.
jvshahid added a commit that referenced this pull request Mar 26, 2014
Deletes don't seem to actually delete the underlying data
@jvshahid jvshahid merged commit 7654856 into master Mar 26, 2014
@jvshahid jvshahid changed the title Deletes don't seem to actually delete the underlying data Data is resurrected after a server restart Mar 26, 2014
@jvshahid jvshahid deleted the fix-342-delete-bug branch April 1, 2014 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants