You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
Help:Toolforge/Database
Tool and Tools users are granted access to replicas of the production databases. Private user data has been redacted from these replicas (some rows are elided and/or some columns are made NULL depending on the table). For most practical purposes this is identical to the production databases and sharded into clusters in much the same way.
Database credentials are generated on account creation and placed in a replica.my.cnf file in the home directory of both a Tool and a Tools user account. This file cannot be modified or removed by users.
Symlinking the access file can be practical:
ln -s $HOME/replica.my.cnf $HOME/my.cnf
Connecting to the database replicas
You can connect to the database replicas (and/or the cluster where a database replica is hosted) by specifying your access credentials and the alias of the cluster and replicated database. For example:
To connect to the English Wikipedia replica, specify the alias of the hosting cluster (enwiki.analytics.db.svc.eqiad.wmflabs) and the alias of the database replica (enwiki_p) :
mysql --defaults-file=$HOME/replica.my.cnf -h enwiki.analytics.db.svc.eqiad.wmflabs enwiki_p
To connect to the Wikidata cluster:
mysql --defaults-file=$HOME/replica.my.cnf -h wikidatawiki.analytics.db.svc.eqiad.wmflabs
To connect to Commons cluster:
mysql --defaults-file=$HOME/replica.my.cnf -h commonswiki.analytics.db.svc.eqiad.wmflabs
There is also a shortcut for connecting to the replicas: sql <dbname>[_p] The _p is optional, but implicit (i.e. the sql tool will add it if absent).
To connect to the English Wikipedia database replica using the shortcut, simply type:
sql enwiki
To connect to ToolsDB where you can create and write to tables, type:
sql local
This sets server to "tools.db.svc.eqiad.wmflabs" and db to "". It's equivalent to typing-
mysql --defaults-file=$HOME/replica.my.cnf -h tools.db.svc.eqiad.wmflabs
Naming conventions
As a convenience, each mediawiki project database (enwiki, bgwiki, etc) has an alias to the cluster it is hosted on. The alias has the form:
- ${PROJECT}.{analytics,web}.db.svc.eqiad.wmflabs
where ${PROJECT} is the internal database name of a hosted Wikimedia project. The choice of "analytics" or "web" is up to you. The analytics service name connects to Wiki Replica servers where SQL queries will be allowed to run for a longer duration, but at the cost of all queries being potentially slower. Use of the web service name should be reserved for webservices which are running queries that display to users.
Wikipedia project database names generally follow the format ${LANGUAGE_CODE}${PROJECT_FAMILY}. ${LANGUAGE_CODE} is the ISO 639 two-letter code for the primary content language (e.g. en for English, es for Spanish, bg for Bulgarian, ...). ${PROJECT_FAMILY} is an internal label for the wiki's project family (e.g. wiki for Wikipedia, wiktionary for Wiktionary, ...). Some wikis such as Meta-Wiki have database names that do not follow this pattern (metawiki).
 | A full list of projects is available via Quarry. |
The replica database names themselves consist of the Wikimedia project name, suffixed with _p (an underscore, and a p), for example:
enwiki_pfor the English Wikipedia replica
In addition each cluster can be accessed by the name of its Wikimedia production shard which follows the format s${SHARD_NUMBER}.{analytics,web}.db.svc.eqiad.wmflabs (for example, s1.analytics.db.svc.eqiad.wmflabs hosts the enwiki_p database). The shard where a particular database is located can change over time. You should only use the shard name for opening a database connection if your application requires it for specific performance reasons such as for heavily crosswiki tools which would otherwise open hundreds of database connections.
Connection handling policy
Usage of connection pools (maintaining open connections without them being in use), persistent connections, or any kind of connection pattern that maintains several connections open even if they are unused is not permitted on shared MySQL instances (Wiki Replicas and ToolsDB).
The memory and processing power available to the database servers is a finite resource. Each open connection to a database, even if inactive, consumes some of these resources. Given the number of potential users for the Wiki Replicas and ToolsDB, if even a relatively small percentage of users held open idle connections, the server would quickly run out of resources to allow new connections. Please close your connections as soon as you stop using them. Note that connecting interactively and being idle for a few minutes is not an issue—opening dozens of connections and maintaining them automatically open is.
Idle connections can and will be killed by database and system administrators when discovered. If you (for example, by connector configuration or application policy) then reopen those connections automatically and keep them idle, you will be warned to stop.
Connecting to the database replicas from other Labs instances
The *.{analytics,web}.db.svc.eqiad.wmflabs servers should be directly accessible from other Labs instances as well (these are provided in DNS), but there is no automatic creation of database credential files. Please create a task in the Labs project to have one created for you.
Connecting to the database replicas from your own computer
You can access the database replicas from your own computer by setting up an SSH tunnel. If you use MySQL Workbench, you can find a detailed description for that application below.
Tunneling is a built-in capability of ssh. It allows creating a listening TCP port on your local computer that will transparently forward all connections to a given host and port on the remote side of the ssh connection. The destination host and port do not need to be the host that you are connecting to with your ssh session, but they do need to be reachable from the remote host.
In the general case, need to add a port forwarding in your ssh tool. In Windows, you can use the tool PuTTY by add in Connection → SSH → Tunnels the following settings.
In Linux, you can add the option -L $LOCAL_PORT:$REMOTE_HOST:$REMOTE_PORT to your ssh call, e. g.:
$ ssh -L 4711:enwiki.analytics.db.svc.eqiad.wmflabs:3306 tools-login.wmflabs.org
This will set up a tunnel so that connections to port 4711 on your own computer will be relayed to the enwiki.analytics.db.svc.eqiad.wmflabs database replica's MySQL server on port 3306. This tunnel will continue to work as long as the SSH session is open.
The mysql command line to connect using the tunnel from the example above would look something like:
$ mysql --user=$USER_FROM_REPLICA.MY.CNF --host=127.0.0.1 --port=4711 --password enwiki_p
The user and password values needed can be found in the $HOME/replica.my.cnf credentials file for your Toolforge user account or a tool that you have access to.
Note that you need to explicitly use the 127.0.0.1 IP address; using localhost instead will give an "Access denied" error.
SSH tunneling for local testing which makes use of Wiki Replica databases
- Setup SSH tunnels:
ssh -N yourusername@tools-dev.wmflabs.org -L 3306:enwiki.analytics.db.svc.eqiad.wmflabs:3306-Nprevents ssh from opening an interactive shell. This connection will only be useful for port forwarding.- The first port is the listening port on your machine and the second one is on the remote server. 3306 is the default port for MySQL.
- For multiple database connections, add additional
-L $LOCAL_PORT:$REMOTE_HOST:$REMOTE_PORTsections to the same command or open additional ssh connections. - If you need to connect to more than one Labs database server each database will need a different listening port on your machine (e.g. 3307, 3308, 3309, ...). Change the associated php/python connect command to send requests to that port instead of the default 3306.
- (optional) Edit your
/etc/hostsfile to add something like127.0.0.1 enwiki.analytics.db.svc.eqiad.wmflabsfor each of the databases you're connecting to. - You might need to copy over the replica.my.cnf file to your local machine for this to work.
TLS connection failures
Some client libraries may attempt to enable TLS encryption when connecting to the Wiki Replica or ToolsDB databases. Depending on the backing server's configuration, this may either fail silently because TLS is not supported at all, or it may fail with authentication or decryption errors because TLS is partially enabled. In this second case, the problem is caused by MariaDB servers which do support TLS encryption but are using self-signed certificates which are not available to the client and do not match the service names used for connections from Cloud Services hosts.
The "fix" for these failures is to configure your client to avoid TLS encryption. How to do this will vary based on the client libraries in use, but should be something that you can find an answer for by searching the Internet/Stack Overflow/library documentation.
Databases
Replica database schema (tables and indexes)
The database replicas for the various Wikimedia projects follow the standard MediaWiki database schema described on mediawiki.org and in the MediaWiki git repository.
Many of the indexes on these tables are actually compound indexes designed to optimize the runtime performance of the MediaWiki software rather than to be convenient for ad hoc queries. For example, a naive query by page_title such at SELECT * FROM page WHERE page_title = 'NOFX'; will be slow because the index which includes page_title is a compound index with page_namespace. Adding page_namespace to the WHERE clause will improve the query speed dramatically: SELECT * FROM page WHERE page_namespace = 0 AND page_title = 'NOFX';
Stability of the mediawiki database schema
maintenance/tables.sql shows the HEAD of the mediawiki changes. Extra tables may be available due to additional extensions setup in production. Also some tables may have been redacted or filtered for containing private data such as the user passwords or private ip addresses. Aside from that, while we try to synchronize production with develoment HEAD, changes to the database structure may be applied in advance (or more commonly) lag behin its publication. The reason for this is that schema changes are being continuously applied to production databases, and due to the amout of data, it may take a few hours to a few months (in the case of more complex cases) to be finalized.
Core tables, such as revision, page, user, recentchanges rarely change, but cloud maintainers cannot guarantee they will never change, as they have to follow the production changes. While we are happy for people to setup scripts and tools on top of the database copies (wikireplicas) expect the schema to change every now and then. If you cannot do small tweaks from time to time to adapt to the latest schema changes, using the API instead of the database internals is suggested, as API changes have more guarantees of stability and a proper lifecycle and deprecation policy. That is not true for mediawiki database internals, although compatibility views can sometimes be setup to require only minimal changes.
Tables for revision or logging queries involving user names and IDs
The revision and logging tables do not have indexes on user columns. In an email, one of the system administrators pointed out that this is because "those values are conditionally nulled when supressed" (see also phab:T68786 for some more detail). One has to instead use the corresponding revision_userindex or logging_userindex for these types of queries. On those views, rows where the column would have otherwise been nulled are elided; this allows the indexes to be usable.
Example query that will use the appropriate index (in this case on the rev_user_text column, the rev_user column works the same way for user IDs):
SELECT rev_id, rev_timestamp FROM revision_userindex WHERE rev_user_text="Foo"
Example query that fails to use an index because the table doesn't have them:
SELECT rev_id, rev_timestamp FROM revision WHERE rev_user_text="Foo"
You should use the indexes so queries will go faster (performance).
Redacted tables
language, skin, timecorrection, and variant properties have been deemed sensitive and are removed from user_properties table of Labs DB replicas.
Unused tables
Some of the standard MediaWiki tables that are in use on Wikimedia wikis, are not available. The following tables are missing or empty:
interwiki(T103589)texttable (mw:Manual:MediaWiki architecture#Database and text storage): Users can use the API, or dumps to access page contents.
Metadata database
There is a table with automatically maintained meta information about the replicated databases: meta_p.wiki. See Quarry #4031 for an up-to-date version.
MariaDB [meta_p]> DESCRIBE wiki;
+------------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +------------------+--------------+------+-----+---------+-------+ | dbname | varchar(32) | NO | PRI | NULL | | | lang | varchar(12) | NO | | en | | | name | text | YES | | NULL | | | family | text | YES | | NULL | | | url | text | YES | | NULL | | | size | decimal(1,0) | NO | | 1 | | | slice | text | NO | | NULL | | | is_closed | decimal(1,0) | NO | | 0 | | | has_echo | decimal(1,0) | NO | | 0 | | | has_flaggedrevs | decimal(1,0) | NO | | 0 | | | has_visualeditor | decimal(1,0) | NO | | 0 | | | has_wikidata | decimal(1,0) | NO | | 0 | | | is_sensitive | decimal(1,0) | NO | | 0 | | +------------------+--------------+------+-----+---------+-------+
Example data:
MariaDB [nlwiki_p]> select * from meta_p.wiki limit 1 \G
*************************** 1. row ***************************
dbname: aawiki
lang: aa
name: Wikipedia
family: wikipedia
url: http://aa.wikipedia.org
size: 1
slice: s3.labsdb
is_closed: 1
has_echo: 1
has_flaggedrevs: 0
has_visualeditor: 1
has_wikidata: 1
is_sensitive: 0
Identifying lag
If there is a network/labs db infrastructure problem, production problem, maintenance (scheduled or unscheduled), excessive load or production or user's queries blocking the replication process, labs replicas can get behind the production databases "lag".
To identify lag, see https://tools.wmflabs.org/replag/ or execute yourself on the database host you are connected to:
(u3518@enwiki.analytics.db.svc.eqiad.wmflabs) [heartbeat_p]> SELECT * FROM heartbeat; +-------+----------------------------+--------+ | shard | last_updated | lag | +-------+----------------------------+--------+ | s1 | 2018-01-09T22:47:05.001180 | 0.0000 | | s2 | 2018-01-09T22:47:05.001190 | 0.0000 | | s3 | 2018-01-09T22:47:05.001290 | 0.0000 | | s4 | 2018-01-09T22:47:05.000570 | 0.0000 | | s5 | 2018-01-09T22:47:05.000670 | 0.0000 | | s6 | 2018-01-09T22:47:05.000760 | 0.0000 | | s7 | 2018-01-09T22:47:05.000690 | 0.0000 | | s8 | 2018-01-09T22:47:05.000600 | 0.0000 | +-------+----------------------------+--------+ 8 rows in set (0.00 sec)
This table is based on the tool pt-heartbeat, not on SHOW MASTER STATUS, producing very accurate results, even if replication is broken, and directly comparing it to the original master, and not the replicas's direct master.
- shard: s1-8. Each of the production masters. The wiki distribution can be seen at: https://noc.wikimedia.org/db.php
- last_updated: Every 1 second, a row in the master is written with the date local to the master. Here you have its value, once replicated. As it is updated every 1 second, it has a measuring error of [0, 1+] seconds.
- lag: The difference between the current date and the last_updated column (
timestampdiff(MICROSECOND,`heartbeat`.`heartbeat`.`ts`,utc_timestamp())/1000000.0). Again note that updates to this table only happen every second (it can vary on production), so most decimals are meaningless.
To directly query the replication lag for a particular wiki, use requests like:
MariaDB [fawiki_p]> SELECT lag FROM heartbeat_p.heartbeat JOIN meta_p.wiki ON shard = SUBSTRING_INDEX(slice, ".", 1) WHERE dbname = 'fawiki'; +------+ | lag | +------+ | 0 | +------+ 1 row in set (0.09 sec)
Please note that some seconds or a few minutes of lag is considered normal, due to the filtering process and the hops done before reaching the public hosts.
Replica drift
- This is a brief summary of the /Replica drift documentation page.
| This page is historical and documents a problem which has been addressed. |
Overview
This page documents an issue known as Replica drift.
This problem was solved for wikireplicas by introducing Row-based replication starting on production, so most issues, if not all, should have already disappeared (only anecdotal cases could reappear).
If you detect what you think is a drift- report a ticket on Wikimedia's Phabricator (https://phabricator.wikimedia.org) with an SQL query, expected results and obtained results, with the tags #data-services and #dba.
History
Replica drift was a recurring problem for the Wiki Replicas prior to the introduction of row-based replication (RBR) between the sanitarium server(s) and their upstream sources. The RBR replication used to populate the *.{analytics,web}.db.svc.eqiad1.wikimedia.cloud servers will not allow arbitrary differences in data to be synchronized. If there is a replication failure it will halt all replication with the master server which will in turn raise an alert that will be noticed and corrected.
User databases
User-created databases can be created on a shared server: tools.db.svc.eqiad.wmflabs. Database names must start with the name of the credential user followed by two underscores and then the name of the database: <credentialUser>__<DBName> (e.g. "s51234__mydb").
The credential user is not your user name. It can be found in your ~/replica.my.cnf file. The name of the credential user looks something like 'u1234' for a user and 's51234' for a service group. You can also find the name of the credential user using a live database connection:
SELECT SUBSTRING_INDEX(CURRENT_USER(), '@', 1);
Privileges on the database
Users have all privileges and have access to all grant options on their databases. Database names ending with _p are granted read access for everyone. Please create a ticket if you need more fine-grained permissions, like sharing a database only between 2 users, or other special permissions.
Steps to create a user database on tools.db.svc.eqiad.wmflabs
To create a database on tools.db.svc.eqiad.wmflabs:
- Become your tool account.
maintainer@tools-login:~$ become toolaccount
- Connect to tools.db.svc.eqiad.wmflabs with the replica.my.cnf credentials:
mysql --defaults-file=$HOME/replica.my.cnf -h tools.db.svc.eqiad.wmflabs
You could also just type:sql tools
- In the mysql console, create a new database (where CREDENTIALUSER is your credentials user, which can be found in your ~/replica.my.cnf file, and DBNAME the name you want to give to your database. Note that there are 2 underscores between CREDENTIALUSER and DBNAME):
MariaDB [(none)]> CREATE DATABASE CREDENTIALUSER__DBNAME;
You can then connect to your database using:
mysql --defaults-file=$HOME/replica.my.cnf -h tools.db.svc.eqiad.wmflabs CREDENTIALUSER__DBNAME
Example
Assuming that your tool account is called "mytool", this is what it would look like:
maintainer@tools-login:~$ become mytool tools.mytool@tools-login:~$ mysql --defaults-file=$HOME/replica.my.cnf -h tools.db.svc.eqiad.wmflabs MariaDB [(none)]> select substring_index(current_user(), '@', 1) as uname; +---------------+ | uname | +---------------+ | u123something | +---------------+ 1 row in set (0.00 sec) MariaDB [(none)]> create database u123something__wiki;
 Caution: | The DNS alias tools-db is deprecated. |
ToolsDB Backups and Replication
We maintain two copies of the user and tool databases in ToolsDB, with a MySQL master-slave replication setup. However, we don't do offline backups of any of the databases in ToolsDB. ToolsDB users can backup their data using mysqldump if necessary. Note that we don't recommend storing backups permanently on NFS (/data/project, /home, or /data/scratch on Toolforge) or on any other Cloud VPS hosted drive. True backups should be kept offsite.
There are some ToolsDB databases which are not replicated for various reasons including size and access patterns:
- s51412__data
- s51071__templatetiger_p
- s52721__pagecount_stats_p
- s51290__dpl_p
Users were warned about this particularity and details can be seen at task T127164.
Query Limits
This information is directed towards the new wikireplica services.
Since MariaDB 10.1 (the version used on tools and the new wikireplicas), one can use max_statement_time (unit is seconds, it allows decimals) :
SET max_statement_time = 300;
And all subsequent queries on the same connection will be killed if they run for longer than the given time.
For example:
mariadb[(none)]> SET max_statement_time = 10; Query OK, 0 rows affected (0.00 sec) mariadb[(none)]> SELECT sleep(20); +-----------+ | sleep(20) | +-----------+ | 1 | +-----------+ 1 row in set (10.00 sec)
It works on Quarry, too!
You can also set limits with a single SQL query. For example:
SET STATEMENT max_statement_time = 300 FOR
SELECT COUNT(rev_id) FROM revision_userindex
WHERE rev_user_text = 'Jimbo Wales'
Example queries
See Help:MySQL queries. Add yours!
Connecting with...
Python
Use User:Legoktm/toolforge library.
MySQL Workbench
You can connect to databases on Toolforge with MySQL Workbench (or similar client applications) via an SSH tunnel.
Instructions for connecting via MySQL Workbench are as follows:
- Launch MySQL Workbench on your local machine.
- Click the plus icon next to "MySQL Connections" in the Workbench window (or choose "Manage Connections..." from the Database menu and click the "new" button).
- Set Connection Method to "Standard TCP/IP over SSH"
- Set the following connection parameters:
- SSH Hostname: tools-login.wmflabs.org
- SSH Username: <your Toolforge shell username>
- SSH Key File: <your Toolforge SSH private key file>
- SSH Password: password/passphrase of your private key (if set) - not your wiki login password.
- MySQL Hostname: enwiki.analytics.db.svc.eqiad.wmflabs (or whatever server your database lives on)
- MySQL Server Port: 3306
- Username: <your Toolforge MySQL user name (from $HOME/replica.my.cnf)>
- Password: <your Toolforge MySQL password (from $HOME/replica.my.cnf)>
- Default Schema: <name of your Toolforge MySQL database, e.g. enwiki_p>
- Click "OK"
Replica-db hostnames can be found in /etc/hosts. Bear in mind to add the _p suffix if setting a default schema for replica databases. e.g: enwiki_p.
If you are using SSH keys generated with PuTTYgen (Windows users), you need to convert your private key to the 'OpenSSH' format. Load your private key in PuTTYgen, then click Conversions » Export OpenSSH key. Use this file as SSH Key File above.
If you are getting errors with SSL, you can try disabling it. From the menu bar: Database -> select your connection -> SSL -> Change "Use SSL" to "No".
PGAdmin (for OpenStreetMap databases)
This guide assumes you already know what PGAdmin is and how to use it.
| Extended instructions |
|
You need a version that support SSH Tunneling. Version 1.18 does.
The application will autoconnect to the server. There will be a warning about server encoding, ignore it for now. The tables can be found in the following hierarchy Databases->gis->Schemas->public->Tables
|
Connecting to OSM via the official CLI PostgreSQL
- SSH to tools-login.wmflabs.org or tools-dev.wmflabs.org
- psql -h osmdb.eqiad.wmnet -U osm gis
- Start querying
Connecting from a Servlet in Tomcat
- create directory "lib" in directory "public_tomcat"
- copy "mysql-connector-java-bin.jar" to "public_tomcat/lib"
import org.apache.tomcat.jdbc.pool.DataSource; import org.apache.tomcat.jdbc.pool.PoolProperties; String DBURL = "jdbc:mysql://tools.db.svc.eqiad.wmflabs:3306/"; String DBDRIVER = "com.mysql.jdbc.Driver"; String DATABASE = DBUSER + "__" + PROJECT; PoolProperties p = new PoolProperties(); p.setUrl (DBURL + DATABASE); p.setDriverClassName(DBDRIVER ); p.setUsername (DBUSER ); p.setPassword (DBPASSWORD ); p.setJdbcInterceptors( "org.apache.tomcat.jdbc.pool.interceptor.ConnectionState;" + "org.apache.tomcat.jdbc.pool.interceptor.StatementFinalizer"); DataSource datasource = new DataSource(); datasource.setPoolProperties(p); Connection connection = datasource.getConnection (); Statement statement = connection.createStatement();
javac -classpath javax.servlet.jar:tomcat-jdbc.jar myhttpservlet.java
Code samples for common languages
- Copied with edits from mw:Toolserver:Database access#Program access (not all tested, use with cation!)
In most programming languages, it will be sufficient to tell MySQL to use the database credentials found in $HOME/.my.cnf assuming that you have created a symlink from $HOME/.my.cnf to $HOME/replica.my.cnf.
Below are various examples in a few common programming languages.
Bash
-- 2> /dev/null; date; echo '
/* Bash/SQL compatible test structure
*
* Run time: ? <SLOW_OK>
*/
SELECT 1
;-- ' | mysql -ch tools.db.svc.eqiad.wmflabs enwiki_p > ~/query_results-enwiki; date;
C
#include <my_global.h>
#include <mysql.h>
...
char *host = "tools.db.svc.eqiad.wmflabs";
MYSQL *conn = mysql_init(NULL);
mysql_options(conn, MYSQL_READ_DEFAULT_GROUP, "client");
if (mysql_real_connect(conn, host, NULL, NULL, NULL, 0, NULL, 0) == NULL) {
printf("Error %u: %s\n", mysql_errno(conn), mysql_error(conn));
...
}
Perl
use User::pwent;
use DBI;
my $database = "enwiki_p";
my $host = "tools.db.svc.eqiad.wmflabs";
my $dbh = DBI->connect(
"DBI:mysql:database=$database;host=$host;"
. "mysql_read_default_file=" . getpwuid($<)->dir . "/replica.my.cnf",
undef, undef) or die "Error: $DBI::err, $DBI::errstr";
Python
- Using User:Legoktm/toolforge library is probably the best way (which supports Python 3).
Using oursql (uses less memory):
import os, oursql
db = oursql.connect(db='tools.db.svc.eqiad.wmflabs',
host="localhost",
read_default_file=os.path.expanduser("~/replica.my.cnf"),
charset=None,
use_unicode=False
)
Extra flags are required for oursql to force binary mode since VARCHAR fields on sql-s2 are mislabeled with latin-1. Manual decoding is required even after upgrading since the fields will be VARBINARY instead. Note: oursql is only installed on solaris, see jira:TS-760 and jira:TS-1452 for more information.
PHP (using PDO)
<?php
$ts_pw = posix_getpwuid(posix_getuid());
$ts_mycnf = parse_ini_file($ts_pw['dir'] . "/replica.my.cnf");
$db = new PDO("mysql:host=enwiki.analytics.db.svc.eqiad.wmflabs;dbname=enwiki_p", $ts_mycnf['user'], $ts_mycnf['password']);
unset($ts_mycnf, $ts_pw);
$q = $db->prepare('select * from page where page_id = :id');
$q->execute(array(':id' => 843020));
print_r($q->fetchAll());
?>
PHP (using MySQLi)
<?php
$ts_pw = posix_getpwuid(posix_getuid());
$ts_mycnf = parse_ini_file($ts_pw['dir'] . "/replica.my.cnf");
$mysqli = new mysqli('enwiki.analytics.db.svc.eqiad.wmflabs', $ts_mycnf['user'], $ts_mycnf['password'], 'enwiki_p');
// YOUR REQUEST HERE
?>
Java
Class.forName("com.mysql.jdbc.Driver").newInstance();
Properties mycnf = new Properties();
mycnf.load(new FileInputStream(System.getProperty("user.home")+"/replica.my.cnf"));
String password = mycnf.getProperty("password");
password=password.substring((password.startsWith("\""))?1:0, password.length()-((password.startsWith("\""))?1:0));
mycnf.put("password", password);
mycnf.put("useOldUTF8Behavior", "true");
mycnf.put("useUnicode", "true");
mycnf.put("characterEncoding", "UTF-8");
mycnf.put("connectionCollation", "utf8_general_ci");
String url = "jdbc:mysql://tools.db.svc.eqiad.wmflabs:3306/enwiki_p";
Connection conn = DriverManager.getConnection(url, mycnf);
See also
- "New Wiki Replica servers ready for use"(announcement post, September 25, 2017)