-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
WAL not cleaned up on failed creation #10688
Comments
joshcc3
pushed a commit
to joshcc3/etcd
that referenced
this issue
Apr 28, 2019
delete <data-dir>/member/wal if any operation after the rename in wal.Create fails to avoid reading an inconsistent WAL on restart. Fixes etcd-io#10688
joshcc3
pushed a commit
to joshcc3/etcd
that referenced
this issue
Apr 29, 2019
delete <data-dir>/member/wal if any operation after the rename in wal.Create fails to avoid reading an inconsistent WAL on restart. Fixes etcd-io#10688
joshcc3
pushed a commit
to joshcc3/etcd
that referenced
this issue
Apr 30, 2019
delete <data-dir>/member/wal if any operation after the rename in wal.Create fails to avoid reading an inconsistent WAL on restart. Fixes etcd-io#10688
joshcc3
pushed a commit
to joshcc3/etcd
that referenced
this issue
May 4, 2019
delete <data-dir>/member/wal if any operation after the rename in wal.Create fails to avoid reading an inconsistent WAL on restart. Fixes etcd-io#10688
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran etcd (default config) with the data-dir located in a bind mounted directory in a container running on windows. This Fsync is not supported and on the first run it Panics without cleaning up the WAL dir. As a consequence, on the subsequent run the node enters 'restart' mode however since the peers haven't been added it isn't able to make 'progress' and choose a leader and times out trying to publish its information into the cluster.
While I dont think etcd needs to support this type of storage, I do think that getting to this stage is a bug. I'm interested in contributing to etcd and would be interested in tackling this issue.
On the first run (fails to fsync)
Initial entries to bootstrap peers have not been added to the log but it still exists
Subsequent run where it times out trying to publish info:
I think (one of?) 2 things could be done:
Let me know your thoughts?
I'm not too familiar with the code base yet but I think that's the cause?
The text was updated successfully, but these errors were encountered: