{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":65550850,"defaultBranch":"10.1","name":"server","ownerLogin":"knielsen","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2016-08-12T12:15:08.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/79553?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1712073275.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"994c3625a1d21fcb2b26b60189024349c209b660","ref":"refs/heads/implement_slave_parallel_threads_active","pushedAt":"2024-04-02T15:54:35.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"knielsen","name":"Kristian Nielsen","path":"/knielsen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79553?s=80&v=4"},"commit":{"message":"Implement option --slave-parallel-threads-active\n\nThis option implements a way to limit the number of actively used threads\nin parallel replication without requiring to stop the slave threads.\n\nWhen set non-zero, following transactions will be queued against at most\n@@slave_parallel_threads_active threads in each domain, even if\n@@slave_parallel_threads or @@slave_domain_parallel_threads are set higher.\n\nSigned-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>","shortMessageHtmlLink":"Implement option --slave-parallel-threads-active"}},{"before":null,"after":"d6c51805fba49b911532d844e79823e7587aaeb4","ref":"refs/heads/snow_rpl_deadlock_logging","pushedAt":"2024-03-06T13:12:38.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"knielsen","name":"Kristian Nielsen","path":"/knielsen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79553?s=80&v=4"},"commit":{"message":"Add extra logging around parallel replication transaction conflict and retry\n\nA warning is logged to the error log when:\n\n - A lock wait timeout occurs.\n - A transaction needs to retry more than once.\n\nAdditionally, an informational/note is logged to the error log whenever a\ntransaction is rolled back and retried due to a conflict with an earlier\ntransaction; this is raised to a warning if the rolled-back transaction\nalready had to retry once.\n\nSigned-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>","shortMessageHtmlLink":"Add extra logging around parallel replication transaction conflict an…"}},{"before":null,"after":"b5ff911ed70cfab0b7ed9931f9a9574bec29bb80","ref":"refs/heads/knielsen_alt_domain_wait","pushedAt":"2023-12-19T11:07:20.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"knielsen","name":"Kristian Nielsen","path":"/knielsen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79553?s=80&v=4"},"commit":{"message":"Incomplete prototype of out-of-order alternate domain running always behind the default domain\n\nSigned-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>","shortMessageHtmlLink":"Incomplete prototype of out-of-order alternate domain running always …"}},{"before":"134dfddc278cb941e56cf83977ad3b4b3ac3deb6","after":"024b8791ac1c01b22807085c5e24930816d68f0f","ref":"refs/heads/bugfix_mariabackup_nolock","pushedAt":"2023-09-22T11:15:54.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"knielsen","name":"Kristian Nielsen","path":"/knielsen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79553?s=80&v=4"},"commit":{"message":"Fix mariabackup InnoDB recovered binlog position on server upgrade\n\nBefore MariaDB 10.3.5, the binlog position was stored in the TRX_SYS page,\nwhile after it is stored in rollback segments. There is code to read the\nlegacy position from TRX_SYS to handle upgrades. The problem was if the\nlegacy position happens to compare larger than the position found in\nrollback segments; in this case, the old TRX_SYS position would incorrectly\nbe preferred over the newer position from rollback segments.\n\nFixed by always preferring a position from rollback segments over a legacy\nposition.\n\nSigned-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>","shortMessageHtmlLink":"Fix mariabackup InnoDB recovered binlog position on server upgrade"}},{"before":null,"after":"134dfddc278cb941e56cf83977ad3b4b3ac3deb6","ref":"refs/heads/bugfix_mariabackup_nolock","pushedAt":"2023-08-15T10:34:10.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"knielsen","name":"Kristian Nielsen","path":"/knielsen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79553?s=80&v=4"},"commit":{"message":"Revert: MDEV-22351 InnoDB may recover wrong information after RESET MASTER\n\nThis commit can cause the wrong (old) binlog position to be recovered by\nmariabackup --prepare. It implements that the value of the FIL_PAGE_LSN is\ncompared to determine which binlog position is the last one and should be\nrecoved. However, it some cases it is seen that the FIL_PAGE_LSN order does\nnot match the binlog position commit order, as is assumed by the code.\n\nIn one example, the recovery first encountered this in trx_rseg_mem_restore():\n\n  lsn=27282754  binlog position (./master-bin.000001, 472908)\n\nand then later:\n\n  lsn=27282699  binlog position (./master-bin.000001, 477164)\n\nThe last one 477164 is the correct position. However, because the LSN\nencountered for the first one is higher, that position is recovered instead.\nThis results in too old binlog position, and a newly provisioned slave will\nstart replicating too early and get duplicate key error or similar.\n\nSigned-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>","shortMessageHtmlLink":"Revert: MDEV-22351 InnoDB may recover wrong information after RESET M…"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEJbomhgA","startCursor":null,"endCursor":null}},"title":"Activity · knielsen/server"}