-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Anti-Entropy loops endlessly with empty shard #21273
Labels
Comments
davidby-influx
added a commit
that referenced
this issue
Apr 21, 2021
The anti-entropy service will loop trying to copy an empty shard to a data node missing that shard. This fix is one of two changes that correctly create an empty shard on a new node. This fix will set the LastModified date of an empty shard directory to the modificaiton time of that directory, instead of to the Unix epoch. Fixes: #21273
3 tasks
3 tasks
davidby-influx
added a commit
that referenced
this issue
Apr 23, 2021
The anti-entropy service will loop trying to copy an empty shard to a data node missing that shard. This fix is one of two changes that correctly create an empty shard on a new node. This fix will set the LastModified date of an empty shard directory to the modification time of that directory, instead of to the Unix epoch. Fixes: #21273
This was referenced Apr 23, 2021
davidby-influx
added a commit
that referenced
this issue
Apr 23, 2021
The anti-entropy service will loop trying to copy an empty shard to a data node missing that shard. This fix is one of two changes that correctly create an empty shard on a new node. This fix will set the LastModified date of an empty shard directory to the modification time of that directory, instead of to the Unix epoch. Fixes: #21273 (cherry picked from commit 7f300dc)
4 tasks
davidby-influx
added a commit
that referenced
this issue
Apr 26, 2021
The anti-entropy service will loop trying to copy an empty shard to a data node missing that shard. This fix is one of two changes that correctly create an empty shard on a new node. This fix will set the LastModified date of an empty shard directory to the modification time of that directory, instead of to the Unix epoch. Fixes: #21273 (cherry picked from commit 7f300dc)
davidby-influx
added a commit
that referenced
this issue
Apr 27, 2021
The anti-entropy service will loop trying to copy an empty shard to a data node missing that shard. This fix is one of two changes that correctly create an empty shard on a new node. This fix will set the LastModified date of an empty shard directory to the modification time of that directory, instead of to the Unix epoch. Fixes: #21273 (cherry picked from commit 7f300dc)
4 tasks
davidby-influx
added a commit
that referenced
this issue
Apr 28, 2021
The anti-entropy service will loop trying to copy an empty shard to a data node missing that shard. This fix is one of two changes that correctly create an empty shard on a new node. This fix will set the LastModified date of an empty shard directory to the modification time of that directory, instead of to the Unix epoch. Fixes: #21273 (cherry picked from commit 7f300dc) fixes #21287
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a fix for an issue only seen in the Enterprise version of Influx.
In this change, the FileStore.LastModification() for an empty directory with no shard files is set to the modification time of the directory itself, instead of the Unix epoch. This is part of the changes necessary to prevent a bug in the anti-entropy service. The change does not affect any directory which has shard files in it.
The text was updated successfully, but these errors were encountered: