-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
HDFS-15590. namenode fails to start when ordered snapshot deletion feature is disabled #2326
Conversation
…ature is disabled.
💔 -1 overall
This message was automatically generated. |
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.
How about failing the second user delete request with a "Already marked as deleted" exception instead of changing the edit log loading? It is hard for editlog loading to guess if the command is valid.
Thanks @szetszwo . The problem is just not with user deletes. Let's see a sequence like this:
It will run into the same problem again. We cannot seem to avoid 2 edit log entries for same snapshot delete with Snapshot GC thread running and deleting the snapshot. |
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.
@bshashikant , you are right that failing the second delete won't work. Thanks.
+1 the change looks good.
💔 -1 overall
This message was automatically generated. |
Thanks @szetszwo for the review. I have committed this. |
…ature is disabled (apache#2326)
…ature is disabled (apache#2326) (cherry picked from commit 368f2f6) Change-Id: I78a945efa6747c34e20cf8d2d41d5f89546eebe0
please see https://issues.apache.org/jira/browse/HDFS-15590