Tue, Oct 12
Currently doing the above command but over an NFS mount to dbbackup1 which is in the US. This will take significantly longer - that is the main thing I am interested in right now.
mydumper -G -E -R -m -v 3 -t 2 -c -x "^(?!([0-9a-z]+wiki.(objectcache|querycache|querycachetwo|recentchanges|searchindex)))" -L "/home/johnflewis/$(date +"%Y%m%d%H%M%S").log" --trx-consistency-only
- Time taken: 103 minutes (1 hour and 43 minutes)
- Size: 30G
John has indicated that this is upstream from Certbot so there's nothing further we can do.
Now on test3
The Community noticeboard thread is live and so far has one support. As for going around the wikis, I will do that later and see what they think about the proposed change and the alternative solution to the affected extension.
I will make a thread on the Community noticeboard to inform users about the proposed change and I will also make sure to go around to the wikis which use the extension to inform them about the pros and cons of enabling database compression and get their input on this/discuss possible alternatives to any affected feature (like ReplaceText).
It should be important to note MassEditRegex has more features than ReplaceText and works with compression.
@Agent_Isai Assigning this task to you as as John has mentioned above, there is the disadvantage of ReplaceText and other minor features (which I don't remember by heart) no longer working as a result of this potential change. Some wikis have already been compressed in the past and I recall some users being unhappy because of the ReplaceText issue.
Hi there, do I email you the generated certificate? I cannot seem to find which email I send it to.
I understand. Thank you.
@RatGirl Here's a CSR for your provider:
Unfortunately we prefer to stay with stable versions. Therefore we won't change it to the unstable development branch at this time. I apologise for the inconvenience
Mon, Oct 11
Trying to optimise the dump by reducing amount of data carried over (because not everything in MediaWiki is irreplaceable!)
According to https://www.mediawiki.org/wiki/Extension:AdvancedSearch it requires CirrusSearch which requires ElasticSearch. I think the extension should be undeployed as not currently supported by our infra. CC @RhinosF1 @Reception123 @Universal_Omega.
I don't know why this became a discussion of Elastic/CirrusSearch. My report was that an extension is broken.
High and Unbreak Now! are reserved for issues that affect Miraheze globally. Since this is a database name change, I will recategorize this as Normal.
All but schema changes are done.