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

sql: use schema change lease only for long running schema changes #31530

Open
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
2 participants
@vivekmenezes
Contributor

vivekmenezes commented Oct 17, 2018

Schema changes like RENAME TABLE that only change the schema
and run no data backfills need not need to hold the schema change
lease. The schema change post processing normally happens on
the gateway node. If the gateway fails, the post processing will
be picked up by another node. If more than one node picks it up,
they can all execute the post processing because it is idempotent.

fixes #18983

Release note: None

@vivekmenezes vivekmenezes requested a review from dt Oct 17, 2018

@vivekmenezes vivekmenezes requested a review from cockroachdb/sql-async-prs as a code owner Oct 17, 2018

@cockroach-teamcity

This comment has been minimized.

Show comment
Hide comment
@cockroach-teamcity

cockroach-teamcity Oct 17, 2018

Member

This change is Reviewable

Member

cockroach-teamcity commented Oct 17, 2018

This change is Reviewable

sql: use schema change lease only for long running schema changes
Schema changes like RENAME TABLE that only change the schema
and run no data backfills need not need to hold the schema change
lease. The schema change post processing normally happens on
the gateway node. If the gateway fails, the post processing will
be picked up by another node. If more than one node picks it up,
they can all execute the post processing because it is idempotent.

fixes #18983

Release note: None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment