New issue
Advanced search Search tips

Issue 910732 link

Starred by 1 user
Status: Fixed
Owner:
zamorzaev@chromium.org
Closed: Dec 5
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 910728



Sign in to add a comment

Stop replicating native mysql databases

Project Member Reported by pprabhu@chromium.org, Nov 30 
This is a follow up of go/chops-pm-102 (crbug/902158)

The replication failures happened because replication of some of the mysql native tables (performance_schema related) conflicted with mysql upgrade on the master DB.

We should only replicate our own databases (chromeos_autotest_db and server_database) and leave other databases untouched.

PM follow up => default P1

Comment 1 by pprabhu@chromium.org, Nov 30

Labels: Chase
Owner: zamorzaev@chromium.org
Status: Assigned (was: Untriaged)

Comment 2 by pprabhu@chromium.org, Nov 30

Blocking: 910728

Comment 3 by akes...@chromium.org, Dec 3 

Mysql config is in puppet. my.conf or similar.
Project Member

Comment 4 by bugdroid1@chromium.org, Dec 4 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/422eafbe3f15a7a1a2e818591a71f436463bcfcf

commit 422eafbe3f15a7a1a2e818591a71f436463bcfcf
Author: Alex Zamorzaev <zamorzaev@chromium.org>
Date: Tue Dec 04 19:24:19 2018

Comment 5 by zamorzaev@chromium.org, Dec 5

Status: Fixed (was: Assigned)
►

Sign in to add a comment