Closed
Bug 665867
Opened 13 years ago
Closed 13 years ago
enable mysql access from autoland-staging{01,02}.build
Categories
(Data & BI Services Team :: DB: MySQL, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lsblakk, Assigned: mpressman)
References
Details
+++ This bug was initially created as a clone of Bug #663017 +++
+++ This bug was initially created as a clone of Bug #657764 +++
Probably need both mysql ACLs and firewall access granted.
Comment 1•13 years ago
|
||
Just for the staging databases, right?
Reporter | ||
Comment 2•13 years ago
|
||
no, i need to be able to read the real production data (try pushes and other branches) for testing - read only so if there's a user account set up for read-only than that will work for this.
Assignee | ||
Comment 3•13 years ago
|
||
which database[s] do you need read-only access to?
Assignee: server-ops-database → mpressman
Reporter | ||
Comment 4•13 years ago
|
||
read-only access for user buildbot_reader to tm-b01-slave01.mozilla.org/buildbot_schedulers
Comment 5•13 years ago
|
||
The MySQL slave has a noticeable delay (seconds) from the master - is that going to lead to timing problems where the autoland code expects rows in the database that may not have arrived yet? If not, woo for finding a use for the r/o slave!
Assignee | ||
Comment 6•13 years ago
|
||
The replication delay from the slave is most likely due to locked tables where the insert thread has to wait for a table, most likely a MyISAM table that is in use. This certainly can lead to timing problems. There are some tuning options that can give a higher priority to the writing thread of the master that will help to prevent that delay, however, the drawback is that read queries may yield longer.
Reporter | ||
Comment 7•13 years ago
|
||
(In reply to comment #5)
> The MySQL slave has a noticeable delay (seconds) from the master - is that
> going to lead to timing problems where the autoland code expects rows in the
> database that may not have arrived yet? If not, woo for finding a use for
> the r/o slave!
seconds of delay will not be a problem for this use case.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 9•13 years ago
|
||
Getting permission error:
sqlalchemy.exc.OperationalError: (OperationalError) (1130, "Host '10.12.51.250' is not allowed to connect to this MySQL server") None None
connecting to url:
mysql://buildbot_reader:PASSWORD@tm-b01-slave01.mozilla.org/buildbot_schedulers
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•13 years ago
|
||
Is it possible to get this done asap? My last day here and it would be nice to get some full staging runs done before the end of the day.
Reporter | ||
Comment 11•13 years ago
|
||
Thanks to Matt Pressman who added the autoland-staging01 host address to the allowed list of connections for buildbot_reader we are now able to connect.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Comment 12•13 years ago
|
||
tm-b01-slave01.mozilla.org is unreachable from autoland-staging02.
Accessing through mysql://buildbot_reader:PASSWORD@tm-b01-slave01.mozilla.org/buildbot_schedulers
Looking at the history of this bug, access was only ever added for autoland-staging01.
This is blocking us moving forward with staging of Autoland.
Thanks.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 13•13 years ago
|
||
mysql> GRANT SELECT, CREATE TEMPORARY TABLES ON `buildbot_schedulers`.* TO 'buildbot_reader'@'10.12.51.251' IDENTIFIED BY PASSWORD 'ELIDED';
(note: the password *was* elided....the password is not the word ELIDED). Same pass as buildbot_reader@10.12.51.250.
Comment 14•13 years ago
|
||
Netflow has been opened, can successfully connect.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Data & BI Services Team
You need to log in
before you can comment on or make changes to this bug.
Description
•