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

changefeedccl: test that the initial scan only emits the latest value #28174

Merged
merged 1 commit into from
Aug 3, 2018

Conversation

danhhz
Copy link
Contributor

@danhhz danhhz commented Aug 1, 2018

Release note: None

@danhhz danhhz requested review from nvanbenschoten and a team August 1, 2018 21:37
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Member

@nvanbenschoten nvanbenschoten left a comment

Choose a reason for hiding this comment

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

:lgtm: but is this the desired behavior or an artifact of the ExportRequest method?

Reviewed 1 of 1 files at r1.
Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (and 1 stale)

@danhhz
Copy link
Contributor Author

danhhz commented Aug 3, 2018

This is the desired behavior. When the changefeed is started without the cursor option, it select a timestamp and emits the current values at that timestamp. This is checking that it doesn't also emit obsolete versions of a row from before that timestamp

(flake is TestHelpURLs in lint, rerunning)

@danhhz
Copy link
Contributor Author

danhhz commented Aug 3, 2018

bors r=nvanbenschoten

craig bot pushed a commit that referenced this pull request Aug 3, 2018
28174: changefeedccl: test that the initial scan only emits the latest value r=nvanbenschoten a=danhhz

Release note: None

28223: internal/client: Make the lease manager thread-safe r=a-robinson a=a-robinson

This race was exceptionally rare due to how the lease manager is
typically used by the sqlmigrations package, but it is indeed a race.

Holding a mutex while making a remote RPC is usually a terrible idea,
but in the context of how it's used it's actually more dangerous to let
ExtendLease and ReleaseLease interleave, since if ReleaseLease's CPut
fails then the sqlmigrations package will log.Fatal, and the only
potential for lock contention is between one goroutine using ExtendLease
and one running ReleaseLseas. Perhaps this is tuning the package too
tightly to the needs of its client, but as of now it's its only client.

Fixes #28222

Release note: None

Co-authored-by: Daniel Harrison <[email protected]>
Co-authored-by: Alex Robinson <[email protected]>
@craig
Copy link
Contributor

craig bot commented Aug 3, 2018

Build succeeded

@craig craig bot merged commit c4ffb83 into cockroachdb:master Aug 3, 2018
@danhhz danhhz deleted the cdc_initialscan branch August 3, 2018 18:45
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.

3 participants