When optimizing a large MySQL table (e.g., ~300GB), the database server might hang during the final step of swapping the old table with the optimized one. If this hang persists beyond 600 seconds, MySQL intentionally crashes to prevent prolonged instability.
Typical log entries indicating the issue:
---TRANSACTION 60682931334, ACTIVE 11095 sec dropping table
This tutorial explains how to efficiently export selected large tables from a production Percona MySQL 8 database to a local development environment. This approach avoids the significant performance penalty associated with logical backups (mysqldump) when working with large tables (multiple GBs each).
Prerequisites:
Your MySQL (Percona MySQL 8 recommended) server must have the innodb_file_per_table setting enabled. This setting is enabled by default in recent installations.
Install Percona XtraBackup both on your server and local machine. Instructions: Percona XtraBackup Installation
The documentation is very lacking (probably because this is new?) and it took me some extra time to figure out where to get the tokens and how to configure the importer.
When you run this step gh actions-importer configure you need to provide personal access tokens for both github and the platform you're trying to migrate from.
In my case it's Travis CI and that's what I will cover here, however the steps to acquire the personal access token for github are the same.
Tl;dr go here: https://github.com/settings/tokens
| package main | |
| import ( | |
| "sync" | |
| log "github.com/sirupsen/logrus" | |
| ) | |
| func produce[T any](resources []T, jobs chan<- T, wg *sync.WaitGroup) { | |
| defer wg.Done() |
Whether you're looking to save money on egress charges or whether you simply want a local cache of a subset of your S3 bucket, all you need is this docker compose configuration to proxy all your read requests and cache files locally.
version: '3.7'
services:
minio1:
image: minio/minio:latest
Also available on Odysee: https://odysee.com/@nikooo777:5/o_direct:3
I work at LBRY and I'm a DevOps and Infrastructure Engineer there.
One of my tasks is to develop and improve video delivery to our players over at https://odysee.com.
While this seems like a rather easy task, it actually becomes a very complex one as traffic grows and usage spreads across the world.
Given the large data breach uncovered by HIBP (https://www.troyhunt.com/the-773-million-record-collection-1-data-reach/) in which I was listed I wrote a script to check all my passwords. Here are the instructions if you want to check all your passwords against their database in a safe way:
cat passwordlist.txt | sort | uniq > sortedpasswords.txtfor i in $(cat sortedpasswords.txt); do echo $(echo -n $i | sha1sum | awk '{print $1}') "--- $i" >> hashtable.txt; done#!/bin/bash
for i in $(cut -c1-5 hashtable.txt); do
Certbot now supports DNS authentication and you probably already know that!
Official documentation here
While upgrading the infrastructure at LBRY, the company I work for, I had the necessity of changing certbot renewals from HTTP auth to DNS auth.
A quick google search didn't bring any results for my simple question "How to convert a Certbot certificate configuration based on HTTP authentication to DNS based authentication" (hint: that's too long to be used as search key!) so I thought I'd write up this simple guide.
This article will walk you through the simple steps of porting your old certificates from HTTP authentication to DNS authentication.