Skip to content
This repository was archived by the owner on Dec 16, 2022. It is now read-only.

Slack sync 2019 01 30#125

Merged
rafael merged 179 commits intomasterfrom
slack-sync-2019-01-30
Jan 31, 2019
Merged

Slack sync 2019 01 30#125
rafael merged 179 commits intomasterfrom
slack-sync-2019-01-30

Conversation

@rafael
Copy link
Copy Markdown

@rafael rafael commented Jan 30, 2019

tl;dr: most of the changes look good, I'm worry about: vitessio#4463

Slack changes

Non-Slack changes

Doc changes

Docker changes

deepthi and others added 30 commits December 4, 2018 15:08
…d of keyspace.shard

Signed-off-by: deepthi <deepthi@planetscale.com>
Signed-off-by: Leo Xuzhang Lin <llin@hubspot.com>
Signed-off-by: Leo Xuzhang Lin <llin@hubspot.com>
Signed-off-by: David Weitzman <dweitzman@pinterest.com>
This completes yuananf's work from vitessio#3683
which was split into several diffs and never fully landed.

One large benefit of multi-statement support is that the "rewriteBatchedStatements"
option in Java's connector-j driver doesn't work without it. There's a bug where
connector-j fails to check the server capabilities and assumes multi-statement support.

Signed-off-by: David Weitzman <dweitzman@pinterest.com>
Signed-off-by: Jitendra Vaidya <jitendra.vaidya@gmail.com>
See also PR 4470 and commit dba155b
which introduced a dependency on golang 1.10+.
Some docs refer to 1.11+ so I made bootstrap.sh require that.

Signed-off-by: Scott Lanning <scott.lanning@booking.com>
Added the ability to build without tests
Signed-off-by: Jitendra Vaidya <jitendra.vaidya@gmail.com>
Fix docs. Make sure that env.sh does not set VTTOP if already set.
There were a few regressions that got introduced due to
recent changes:
* MYSQL_FLAVOR got dropped from Dockerfile.mariadb.
* New build.env did not get included in the docker builds.
* CapabilityClientDeprecateEOF behaves differently for MySQL 5.7
  vs older versions: MySQL 5.6 and MariaDB. For 5.7, the capability
  always comes back true, but it comes back as true or false
  for other versions. So, I just removed the check.

Also removed column length check in one of the tests because
they are not consistent across flavors.

Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Derek Perkins <derek@derekperkins.com>
Signed-off-by: Derek Perkins <derek@derekperkins.com>
Signed-off-by: Derek Perkins <derek@derekperkins.com>
helm: handle Orchestrator during preStop shutdown hook
build: fix broken build for other flavors
Signed-off-by: Derek Perkins <derek@derekperkins.com>
Signed-off-by: Derek Perkins <derek@derekperkins.com>
The error from bootstrap.sh was:
"./dev.env: line 23: source: build.env: file not found".

I think it broke in commit 157ebf5 .
Not sure if this is the right fix, but it worked for me
(bootstrap.sh does `source ./build.env`, so it's probably ok).

Signed-off-by: Scott Lanning <scott.lanning@booking.com>
Signed-off-by: Rafael Chacon <rafael@slack-corp.com>
…ated-files

Regenerates protobuf files using protoc 3.6.1
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
sougou and others added 25 commits January 29, 2019 09:00
Signed-off-by: xichengliudui <liuduidui@beyondcent.com>
Signed-off-by: xichengliudui <liuduidui@beyondcent.com>
Signed-off-by: xichengliudui <liuduidui@beyondcent.com>
Signed-off-by: xichengliudui <liuduidui@beyondcent.com>
Signed-off-by: xichengliudui <liuduidui@beyondcent.com>
Signed-off-by: xichengliudui <liuduidui@beyondcent.com>
See vitessio#4551

Signed-off-by: David Weitzman <dweitzman@pinterest.com>
Signed-off-by: xichengliudui <liuduidui@beyondcent.com>
Don't panic in binlogplayer if the vreplication table omits key range
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
…d instead of keyspace.shard"

This reverts commit 8ea39c3.

Signed-off-by: deepthi <deepthi@planetscale.com>
Signed-off-by: deepthi <deepthi@planetscale.com>
Someone who accidentally made a huge transaction asked what this error meant:
"vttablet: rpc error: code = Aborted desc = transaction 1548379105148705713: in use: for rollback"

It's less clear than the typical transaction killed error because the transaction was so large that
rolling it back probably took some time. This diff changes the in use reason to "for tx killer rollback"
which will hopefully be more clear.

Signed-off-by: David Weitzman <dweitzman@pinterest.com>
Revert "change ClusterAlias in _vt.local_metadata ...
Use a more specific "in use" message for the tx killer's rollback
Copy link
Copy Markdown

@setassociative setassociative left a comment

Choose a reason for hiding this comment

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

🚢

@rafael rafael merged commit a2550c5 into master Jan 31, 2019
@rafael rafael deleted the slack-sync-2019-01-30 branch January 31, 2019 17:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.