-
Notifications
You must be signed in to change notification settings - Fork 455
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
Fix (almost) infinite loop in Fileset writer when previous fileset encountered an error writing out index files #2058
Merged
Merged
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
// Copyright (c) 2019 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 fs | ||
|
||
import ( | ||
"os" | ||
"path/filepath" | ||
"testing" | ||
"time" | ||
|
||
"github.com/m3db/m3/src/dbnode/persist" | ||
"github.com/m3db/m3/src/x/ident" | ||
"github.com/stretchr/testify/require" | ||
) | ||
|
||
// TestWriteReuseAfterError was added as a regression test after it was | ||
// discovered that reusing a fileset writer after a called to Close() had | ||
// returned an error could make the fileset writer end up in a near infinite | ||
// loop when it was reused to write out a completely indepedent set of files. | ||
// | ||
// This test verifies that the fix works as expected and prevents regressions | ||
// of the issue. | ||
func TestWriteReuseAfterError(t *testing.T) { | ||
dir := createTempDir(t) | ||
filePathPrefix := filepath.Join(dir, "") | ||
defer os.RemoveAll(dir) | ||
|
||
seriesID := ident.StringID("series1") | ||
w := newTestWriter(t, filePathPrefix) | ||
writerOpts := DataWriterOpenOptions{ | ||
Identifier: FileSetFileIdentifier{ | ||
Namespace: testNs1ID, | ||
Shard: 0, | ||
BlockStart: time.Now().Truncate(time.Hour), | ||
VolumeIndex: 0, | ||
}, | ||
BlockSize: time.Hour, | ||
FileSetType: persist.FileSetFlushType, | ||
} | ||
data := checkedBytes([]byte{1, 2, 3}) | ||
|
||
require.NoError(t, w.Open(writerOpts)) | ||
require.NoError(t, w.Write(seriesID, ident.Tags{}, data, 0)) | ||
require.NoError(t, w.Write(seriesID, ident.Tags{}, data, 0)) | ||
require.Error(t, w.Close()) | ||
|
||
require.NoError(t, w.Open(writerOpts)) | ||
require.NoError(t, w.Close()) | ||
} |
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.
mind grouping the reseting code into a new
func (w *writer) reset()
fnThere 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.
tangentially - should
indexEntries
be bounded/randomly re-allocated if it exceeds certain size to reduce memory usage? not for this PR, just curious myself.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.
@prateek sure
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.
@vdarulis Theoretically yeah it probably should. In practice we only keep one of these around per node (for the most part) and the size of this slice will never exceed the number of series for a given block/shard combination so in practice its usually in the 10s of thousands tops and each item in the slice is not that big so I think its really unlikely it would become an issue. There are definitely other things like this in the code-base though where we're more paranoid because they could become an issue if left unchecked