are you on, and does it have ECC memory?
On Thu, Nov 4, 2021 at 7:48 PM Michael Caplan wrote:
Hello,
I have a nothing fancy SQL statement that crashes MariaDB 10.3.31. The
error log reports "mysqld got signal 11" with the below included mini
core dump.
The statement caused no issues wit
Hello,
I have a nothing fancy SQL statement that crashes MariaDB 10.3.31. The
error log reports "mysqld got signal 11" with the below included mini
core dump.
The statement caused no issues with my prior install of 10.2.xx. With
10.3, the statement runs the majority of the time. The vast
in an upgrade is supported. So you
need to upgrade
10.2 to 10.3 to 10.4 to 10.5, with any additional caveats for specific
version upgrades (e.g. InnoDB log format change during 10.2).
On Wed, 25 Aug 2021, 15:00 Michael Caplan, <mailto:mich...@eggplant.ws>> wrote:
Hi there.
Hi there.
I'm going through an upgrade process I have done before with earlier
versions of mariaDB and Mysql, but running into an issue. My goal is to
create a new slave including upgrade process from MariaDB 10.2.22
(serverOld) to 10.5.12 on a new server (serverNew)
(as inspired by the
Hello,
I'm working on a plan to roll out MariaDB per table data at rest
encryption. Reading through the docs
(https://mariadb.com/kb/en/data-at-rest-encryption-overview/), I
understand that "Using encryption has an overhead of roughly 3-5%." I'd
like to know what this 3-4% refers to. I am
some infinite loop
Oh boy!
On 2019-03-08 10:44 p.m., Michael Caplan wrote:
Hi Marko,
Hope it is okay to resurrect this thread. Restart times where great
with 10.2.14, until I recently enabled FTS on thousands of tables.
Shutdown and startup both take over an hour. This, coupled
Hi Marko,
Hope it is okay to resurrect this thread. Restart times where great
with 10.2.14, until I recently enabled FTS on thousands of tables.
Shutdown and startup both take over an hour. This, coupled with MariaDB
eating up far greater sums of allocated memory in my.cnf, I need to
your issue.
Hope that helps
GL
Le mer. 20 juin 2018 à 14:48, Michael Caplan <mailto:mich...@eggplant.ws>> a écrit :
Just a little follow up on this issue.
Reducing my innodb-buffer-pool-size (by 10GB) has reduced the
amount of time before swap gets chomped on. But not e
15 juin 2018 à 16:53, Michael Caplan <mailto:mich...@eggplant.ws>> a écrit :
If I'm reading the output correct mysql is currently using 35.8
%MEM, 67GB VSZ, and 23.6GB RSS
Not sure how virtual memory size is calculated, but that seems big
I'll try dropping my inno
Lefranc wrote:
Rhys.Campbell, 0 means off since kernel version 3.5.
See reference here:
https://community.hortonworks.com/questions/71095/why-not-set-swappiness-to-zero.html
That's why most people use 1 (safe value)
Michael Caplan: please look at the size of your mysqld process in "ps
aux&quo
--Original Message-
From: Maria-discuss
[mailto:maria-discuss-bounces+rhys.campbell=swisscom@lists.launchpad.net]
On Behalf Of Michael Caplan
Sent: 15 June 2018 14:48
To: Maria Discuss
Subject: [Maria-discuss] Chewing Through Swap - Swappiness = 0
Hi,
I'm trying to figure out why my re
Hi,
I'm trying to figure out why my recently put into production MariaDB is
so swap hungry.
I'm running 10.2.14, with roughly 300GB data (1000K +/- tables). 95%
tables are innodb. I have 64GB RAM, with INNODB buffer pool size set to
50GB (full my.cnf below). The OS is Ubuntu 16.04.4. This
he Twitter fork that was
absorbed by the now removed XtraDB.
Thanks,
Mike
On 2018-06-15 08:24 AM, Michael Caplan wrote:
Hi,
I'm trying to figure out why my recently put into production MariaDB
is so swap hungry.
I'm running 10.2.14, with roughly 300GB data (1000K +/- tables). 95%
tables
Hello,
I've just stalled a rollout to production of 10.2.14 because of this
what I think is rather huge SQL break
(https://jira.mariadb.org/browse/MDEV-15765). Anyone else holding
10.2.14 from production? Anyone running 10.2.14 in production?
Trying to get some additional perspective on
Thanks everyone for the feedback. In sum, not worth the risk. :)
Mike
On 2018-04-06 03:54 AM, andrei.el...@pp.inet.fi wrote:
Kristian,
andrei.el...@pp.inet.fi writes:
Mike,
Hello,
I realize that in general replication from a newer master to an older
slave is typically not
Marko,
Thank you again for such a clear explanation of your reasoning! Should
you be able to pass along a defect ID that I can follow, I'll follow
that and wait for the next release to test things out.
Best,
Mike
On 2018-01-16 01:48 PM, Marko Mäkelä wrote:
Hi Mike,
Sorry, I was busy
next steps?
Thanks,
Mike
On 2018-01-12 08:42 PM, Michael Caplan wrote:
Hi Marko,
Not sure how I missed your reply. Sorry for the delayed response.
To give you a complete picture, this fresh install of MariaDB was
populated with data copied from MySQL 5.6. The data was copied via
rsy
nks,
Mike
On 2018-01-12 08:42 PM, Michael Caplan wrote:
Hi Marko,
Not sure how I missed your reply. Sorry for the delayed response.
To give you a complete picture, this fresh install of MariaDB was
populated with data copied from MySQL 5.6. The data was copied via
rsy
quot;mariabackup --prepare" and
"mariabackup --copy-back" in order to apply the redo log before
starting up the server on the copied files. And while you are at it,
you could also use "mariabackup --backup" and skip the file system
snapshot.
Best regards,
Marko
On Tue, Jan
Here you go!
Thanks,
Mike
On 2018-01-08 12:38 PM, Marko Mäkelä wrote:
Hi Michael,
OK, all the interesting functions (InnoDB functions) are displayed as ??.
In the "perf top" it would have helped to drill into the mysqld
executable, and only show its top functions. Apparently a lot of
else running 10.2 with a large number of tables?
Thanks,
Mike
On 2018-01-08 09:06 AM, Michael Caplan wrote:
Hi,
I'm setting up a replication slave based off of MySQL 5.6. There are a
large number of tables (400K). The MySQL 5.6 master takes around 10
minutes to start up, where the new
Hi,
I'm setting up a replication slave based off of MySQL 5.6. There are a
large number of tables (400K). The MySQL 5.6 master takes around 10
minutes to start up, where the new MariaDB 10.2 slave takes close to 30
minutes. What is making the startup take soo long?
In the below mysql
Thanks for the feedback.
With the slave being set up on a new version from the master, do you see
any issue with this?
Best,
Mike
On 2017-12-29 11:51 AM, Reindl Harald wrote:
Am 29.12.2017 um 16:45 schrieb Michael Caplan:
Am hoping to get some feedback on an upgrade strategy to go from
Hi there,
I'm not seeing any concise information in the MariaDB docs about the
recommended upgrade plan from MySQL 5.6 to MariaDB 10.1. Should I
install MariaDB 10.0 and then 10.1? Or can I run right to 10.1?
I'm running an older version of Ubuntu (12.04 Precise). Looking at the
repo, it
24 matches
Mail list logo
