is meta_p still supported?

On Tue, Apr 6, 2021 at 3:31 PM John <> wrote:
Will we have a simple way to connect to the databases? One of the key reasons that "enwiki.labsdb" works so well is that from a programming level we dont have to worry about which server/slice a particular database is on. Using the <lang><project>_p at <lang><project>.labsdb created a simple uniform way to connect without having to keep track of what database moved to which slice (when that was added mid size wikis were being moved regularrly

On Tue, Apr 6, 2021 at 3:11 PM Brooke Storm <> wrote:

On Apr 6, 2021, at 11:49 AM, Huji Lee <> wrote:

Pardon my potentially dumb question, but how do the shorter DB names get resolved?

I have python code that looks like this:

conn = mysqldb.connect(host="enwiki.labsdb", db="enwiki_p", read_default_file="~/")

How does enwiki.labsdb get resolved to, I am assuming, and will this stop working on April 28th?

Those names were deprecated years ago and are not maintained (they only work for a certain fraction of databases). They are just CNAMES exactly like the others:
enwiki.labsdb. 871 IN CNAME

I did mass grepping in Toolforge NFS and didn’t find any uses of them. So, I’m surprised they are still used anywhere, but recursive greps can miss things. 

So on those names:
1. Please don’t use them anyway because they will certainly go away at some point and only work for the oldest wikis.
2. Since they point at the old DNS names for the sections, they go wherever they go. If we redirect them to the new cluster, they’ll just keep working like before.

They honestly need to be cleaned up (as part of the overall removal of “labs” names), but that’s a separate task that needs communication and so forth.

—Brooke Storm
Wikimedia Cloud Services mailing list (formerly