-
Notifications
You must be signed in to change notification settings - Fork 453
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
[dbnode] Add reason tag to bootstrap retries metric #3317
Merged
Merged
Changes from 12 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
fcd2646
[dbnode] Add reason tag to bootstrap retries metric
vpranckaitis 26dd3e0
Merge branch 'master' into vilius/retry_metric_reason
vpranckaitis 778aed4
increase obsolete-ranges metric when appropriate
vpranckaitis 8d0c2c1
validate metric value in tests
vpranckaitis 00328cf
reorder imports
vpranckaitis e41c8b7
add unit tests
vpranckaitis 5f49665
use xerrors.Is()
vpranckaitis 05131b5
PR comments
vpranckaitis 5afa0b4
additional asserts for metrics
vpranckaitis 4181359
advance clock during bootstrapper run
vpranckaitis e205fbc
update comment
vpranckaitis 61967a8
refactor some variables
vpranckaitis 88f45ee
Merge branch 'master' into vilius/retry_metric_reason
vpranckaitis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,90 @@ | ||
// Copyright (c) 2021 Uber Technologies, Inc. | ||
// | ||
// Permission is hereby granted, free of charge, to any person obtaining a copy | ||
// of this software and associated documentation files (the "Software"), to deal | ||
// in the Software without restriction, including without limitation the rights | ||
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
// copies of the Software, and to permit persons to whom the Software is | ||
// furnished to do so, subject to the following conditions: | ||
// | ||
// The above copyright notice and this permission notice shall be included in | ||
// all copies or substantial portions of the Software. | ||
// | ||
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
// THE SOFTWARE. | ||
|
||
package storage | ||
|
||
import ( | ||
"errors" | ||
"strings" | ||
"testing" | ||
|
||
"github.com/stretchr/testify/assert" | ||
"github.com/uber-go/tally" | ||
|
||
"github.com/m3db/m3/src/dbnode/storage/bootstrap" | ||
xerrors "github.com/m3db/m3/src/x/errors" | ||
) | ||
|
||
func TestBootstrapRetryMetricReason(t *testing.T) { | ||
tests := []struct { | ||
name string | ||
err error | ||
expectedReason string | ||
}{ | ||
{ | ||
name: "any error", | ||
err: xerrors.NewInvalidParamsError(errors.New("some error")), | ||
expectedReason: "other", | ||
}, | ||
{ | ||
name: "obsolete ranges error", | ||
err: xerrors.NewInvalidParamsError(bootstrap.ErrFileSetSnapshotTypeRangeAdvanced), | ||
expectedReason: "obsolete-ranges", | ||
}, | ||
} | ||
|
||
for _, tt := range tests { | ||
t.Run(tt.name, func(t *testing.T) { | ||
testScope := tally.NewTestScope("testScope", map[string]string{}) | ||
options := NewOptions() | ||
options = options.SetInstrumentOptions(options.InstrumentOptions().SetMetricsScope(testScope)) | ||
instr := newBootstrapInstrumentation(options) | ||
|
||
instr.bootstrapFailed(1, tt.err) | ||
|
||
retryMetrics := getBootstrapRetryMetrics(testScope) | ||
assert.NotEmpty(t, retryMetrics) | ||
assert.Equal(t, 1, retryMetrics[tt.expectedReason], "metric with reason:%v should be set to 1") | ||
for reason, value := range retryMetrics { | ||
if reason != tt.expectedReason { | ||
assert.Equal(t, 0, value, "metric with reason:%v should stay 0") | ||
} | ||
} | ||
}) | ||
} | ||
} | ||
|
||
func getBootstrapRetryMetrics(testScope tally.TestScope) map[string]int { | ||
const ( | ||
metricName = "bootstrap-retries" | ||
reasonTag = "reason" | ||
) | ||
valuesByReason := make(map[string]int) | ||
for _, counter := range testScope.Snapshot().Counters() { | ||
if strings.Contains(counter.Name(), metricName) { | ||
reason := "" | ||
if r, ok := counter.Tags()[reasonTag]; ok { | ||
reason = r | ||
} | ||
valuesByReason[reason] = int(counter.Value()) | ||
} | ||
} | ||
return valuesByReason | ||
} |
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.
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.
Shouldn't signal come after assert to avoid timing issues?
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.
All these
IsBootstrapped()
asserts are in between first and lastsignalCh
writes, which should guarantee that all of them are called during bootstrap.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.
After you send a signal, the code that was waiting for the signal starts executing, but you cannot know whether it will take one nanosecond, or 10 seconds to complete, so depending on that timing, your assert would be checking
IsBootstrapped
value either before, or after the first bootstrap iteration. Not really sure it this is desirable here.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.
I do not think it matters much if the assert is done during first bootstrapper pass, just before second pass or in between of them. As long as DB is not marked bootstrapped while bootstrapping is in progress (which should match the time period in between first and last
signalCh
writes, plus some variable amount of time before and after that), and as long as it's marked bootstrapped once bootstrapping is done, it should be fine.I guess I could make it so two signals are needed for bootstrapper to unblock. That way I could squeeze the assert in between them and that would guarantee exact execution on n-th bootstraper pass. Though I'm not sure if we would gain anything from this.
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.
But aren't you concerned that you could be advancing the clock at some unpredictable moment? Perhaps even before the first bootstrap pass has calculated the ranges to bootstrap?
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.
My bad, I was assuming the ranges are calculated within
bs.Bootstrap(ctx, namespaces, cache)
and not before invoking the anonymous fn.Just make sure to rename
noopNone
tonoopAll
in places where it getsNewNoOpAllBootstrapperProvider
assigned.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.
Added double signal for more exact control when clock is advanced 4181359
Refactored
noopNone
61967a8