Handle mispredictions cleanly #22
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the real world, we might mess up when naming a partition. This should be rare if partitionmanager is running often, since it'll rename partitions to match reality, but when it's running only rarely, things get out of date. This change avoids attempting to calculate rates-of-change using partitions that don't make sense - e.g., today is July 1, and our active partition says it starts in a week. That is plainly wrong, but we can still use our current rate-of-change. This expands on PR #12 by changing what the start-datetime is for new partitions after we mispredicted - without this change, if we had partitions through to December, but it's only August and we need more, the new partitions would be named for January instead of reflecting reality that they need to be named for Right Now. This also catches a bug where we could get timestamp name collisions. This is a lot less of an issue when I implement Tim's suggestion in #19, but for now this just increases dates by a day to avoid a collision, and that works well.
tgeoghegan
approved these changes
Sep 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the real world, we might mess up when naming a partition. This should be
rare if partitionmanager is running often, since it'll rename partitions
to match reality, but when it's running only rarely, things get out of date.
This change avoids attempting to calculate rates-of-change using partitions
that don't make sense - e.g., today is July 1, and our active partition
says it starts in a week. That is plainly wrong, but we can still use our
current rate-of-change.
This expands on PR #12 by changing what the start-datetime is for new
partitions after we mispredicted - without this change, if we had partitions
through to December, but it's only August and we need more, the new partitions
would be named for January instead of reflecting reality that they need to
be named for Right Now.
This also catches a bug where we could get timestamp name collisions. This is
a lot less of an issue when I implement Tim's suggestion in #19, but for now
this just increases dates by a day to avoid a collision, and that works well.