Skip to content
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

rocksdb: correctly handle FS that does not support hard links #40875

Merged
merged 1 commit into from
Sep 18, 2019

Conversation

darinpp
Copy link
Contributor

@darinpp darinpp commented Sep 18, 2019

Ingesting a file from a file system that doesn't
support hard links or from a network location, returns
an error that wasn't handled correctly and the result was
IO error instead of Not Supported status.

Fixes #38789

Release justification: Category 2: Bug fixes and low-risk updates to new functionality.

Release note (bug fix): Fixes an issue with creating table indexes
when the server is running on Windows and the store is on a FS
that does not support hard links (ex FAT32 or network share)

@darinpp darinpp requested a review from ajkr September 18, 2019 16:36
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Collaborator

@petermattis petermattis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, though our docs on how to do RocksDB changes are out of date. Please open a PR on cockroachdb/rocksdb with a target branch of crl-release-6.2.1. We'll review the RocksDB change there, then get to rubber stamp this PR.

PS You'll need a Release justification stanza as well.

@ajkr
Copy link
Contributor

ajkr commented Sep 18, 2019

@petermattis I talked to @darinpp and we couldn't think of a problem with following the procedure in the out-of-date README.md. My guess is the drawback is we can't comment on individual lines of code, but in cases where the change is small and we don't need to do that, can following either procedure be ok?

@petermattis
Copy link
Collaborator

@petermattis I talked to @darinpp and we couldn't think of a problem with following the procedure in the out-of-date README.md. My guess is the drawback is we can't comment on individual lines of code, but in cases where the change is small and we don't need to do that, can following either procedure be ok?

Well, the big thing is that we want is for crl-release-6.2.1 to be in sync with the submodule pointer. AFAICT right now it is out of sync. I'm fine with omitting the PR step on cockroachdb/rocksdb, but please push to the crl-release-6.2.1 branch.

Copy link
Contributor

@ajkr ajkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right that is step 7, after we LGTM here. OK then, I'll accept.

Ingesting a file from a file system that doesn't
support hard links or from a network location, returns
an error that wasn't handled correctly and the result was
IO error instead of Not Supported status.

Fixes cockroachdb#38789

Release justification: Category 2: Bug fixes and low-risk updates to new functionality.

Release note (bug fix): Fixes an issue with creating table indexes
when the server is running on Windows and the store is on a FS
that does not support hard links (ex FAT32 or network share)
Copy link
Contributor

@ajkr ajkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM again, the commit matches head of crl-release-6.2.1 now.

@darinpp
Copy link
Contributor Author

darinpp commented Sep 18, 2019

bors r+

craig bot pushed a commit that referenced this pull request Sep 18, 2019
40875: rocksdb: correctly handle FS that does not support hard links r=darinpp a=darinpp

Ingesting a file from a file system that doesn't
support hard links or from a network location, returns
an error that wasn't handled correctly and the result was
IO error instead of Not Supported status.

Fixes #38789

Release justification: Category 2: Bug fixes and low-risk updates to new functionality.

Release note (bug fix): Fixes an issue with creating table indexes
when the server is running on Windows and the store is on a FS
that does not support hard links (ex FAT32 or network share)

Co-authored-by: Darin <darinp@gmail.com>
@kenliu
Copy link

kenliu commented Sep 18, 2019

thx for your help with this @darinpp

@craig
Copy link
Contributor

craig bot commented Sep 18, 2019

Build succeeded

@craig craig bot merged commit 876c5e7 into cockroachdb:master Sep 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

storage: "Failed to link" error creating index on windows
5 participants