Re: [Maria-discuss] Broken MariaDB client ARGGG!!!
Thanks for the heads up about Deb9. I hadn't seen that yet. Moving to
Devuan myself.
But all this talk about PHP is off topic. Its just one example. I guess
I'll take these comments to mean that the official stance on binary
backwards compatibility is that there is less then 0 concern. So I should
expect that all compiled software will need to be patched and recompiled
potentially with each point release. This is a surprise.
Bummer.
- Jon
On 07/04/2017 03:13 AM, Guillaume Lefranc wrote:
Hi Jon,
This is 2017, and you should use mysqlnd. libmysqlclient is not needed
for PHP mysql extensions anymore, hence the error.
apt-get php5-mysqlnd should fix the issue.
And btw, Deb9 is out :)
Best
-GL
Le lun. 3 juil. 2017 à 22:51, Jon Foster <j...@jfpossibilities.com
<mailto:j...@jfpossibilities.com>> a écrit :
I'm constantly astounded at the extreme cavalier attitude that
MySQL/MariaDB has had towards backwards compatibility for the nearly two
decades I've worked with it. Its like you hate the developers that
use your
stuff. What's up with this?!?!
I decided I better install the latest updates to my Deb7 64bit MariaDB
install. WTF! Now all of my PHP apps are griping about:
symbol client_errors, version libmysqlclient_18 not defined in file
libmysqlclient.so.18 ...
And it was working so well ten minutes ago. 10.2 even did away with the
previous gripes from v10.1. :-/ But with the update to
10.2.6+maria~wheezy
of the client libraries from your Debian repositories my clients'
sites are
down.
Please fix. I'll find someway to install older functional code again.
- Jon
--
Sent from my Debian Linux workstation --
http://www.debian.org/intro/about
Jon Foster
JF Possibilities, Inc.
j...@jfpossibilities.com <mailto:j...@jfpossibilities.com>
541-410-2760 <tel:%28541%29%20410-2760>
Making computers work for you!
___
Mailing list: https://launchpad.net/~maria-discuss
<https://launchpad.net/%7Emaria-discuss>
Post to : maria-discuss@lists.launchpad.net
<mailto:maria-discuss@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~maria-discuss
<https://launchpad.net/%7Emaria-discuss>
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp
--
Sent from my Debian Linux workstation -- http://www.debian.org/intro/about
Jon Foster
JF Possibilities, Inc.
j...@jfpossibilities.com
541-410-2760
Making computers work for you!
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp
[Maria-discuss] Broken MariaDB client ARGGG!!!
I'm constantly astounded at the extreme cavalier attitude that MySQL/MariaDB has had towards backwards compatibility for the nearly two decades I've worked with it. Its like you hate the developers that use your stuff. What's up with this?!?! I decided I better install the latest updates to my Deb7 64bit MariaDB install. WTF! Now all of my PHP apps are griping about: symbol client_errors, version libmysqlclient_18 not defined in file libmysqlclient.so.18 ... And it was working so well ten minutes ago. 10.2 even did away with the previous gripes from v10.1. :-/ But with the update to 10.2.6+maria~wheezy of the client libraries from your Debian repositories my clients' sites are down. Please fix. I'll find someway to install older functional code again. - Jon -- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about Jon Foster JF Possibilities, Inc. j...@jfpossibilities.com 541-410-2760 Making computers work for you! ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Re: [Maria-discuss] Best way to scale writes
Clint Byrum wrote: Excerpts from Jon Foster's message of 2016-10-14 09:33:59 -0700: I have a DB scenario that is very write intensive. Essentially its a large scale hit counter of sorts. Currently we're running on a single 12core server with 6 SSDs in a RAID6 array. But we're looking for a way to scale out write volume by adding more servers [...] Anyhow some pointers would be appreciated. If you're overwhelming one server (you haven't even begun to scale up btw) you will have to shard. However, before you do that.. consider how cheap 24 core servers with 10x FusionIO or similar SSDs would be versus the cost in complexity of sharding. Maybe take a look at Vitess, which helps shard things but keeps all the good stuff you like about MariaDB/MySQL: http://vitess.io/ ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp Thanks, Clint, we are moving towards the 24core option too. Just looking to the future. :-) In fact we're moving the DB onto another box just to determine if the "semaphore freezes" we're experiencing are hardware. The newer box is a dual processor box! I'll look at Vitess. THX - Jon -- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about Jon Foster JF Possibilities, Inc. j...@jfpossibilities.com 541-410-2760 Making computers work for you! ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
[Maria-discuss] Best way to scale writes
I have a DB scenario that is very write intensive. Essentially its a large scale hit counter of sorts. Currently we're running on a single 12core server with 6 SSDs in a RAID6 array. But we're looking for a way to scale out write volume by adding more servers, hopefully as conveniently as I might add Apache servers to a website. We see two servers laboring so we add a third to the mix and so on. I'm still looking at the various technologies available to me and was wondering if someone out there had some suggestions on this front. Although Galera Cluster says it scales for write loads too it also says that all servers write the same data and make sure its committed by the time the transaction is completed. So it seems like write performance would never scale because all servers are doing the same write. Maybe I'm missing something. Anyhow some pointers would be appreciated. TIA - Jon -- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about Jon Foster JF Possibilities, Inc. j...@jfpossibilities.com 541-410-2760 Making computers work for you! ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
[Maria-discuss] Long semaphore waits killing server
We're running MariaDB 10.1.16 on Debian 7 (wheezy). We were running v5.5.51 but we started having occasional unrecoverable semaphore waits once or twice a month. We'd have to shutdown all Apache processes running PHP code and then shutdown and restart MariaDB. Lastly we'd restart the Apache servers. That got us by until one day we had the same thing happen every 5 minutes after we started everything back up. It was nearly exactly 5 minutes from the time the Apache services would start that we'd see the beginning symptoms (connection counts surging, CPU hitting the roof) and then within two minutes from there the log would start filling with semaphore wait messages. So I performed an emergency upgrade to 10.1. Its been about a month and I thought this had solved the problem until last Monday... when it happened again. The usual restart process fixed it and I haven't seen any more of those messages logged. There is a ton of information I could give but I'm not sure what will be helpful. So I'll start with the basics: hardware/os: 12 core Intel Xeon @ 1.8GHz 64GB of RAM. 6x Samsung 850 SSDs in software RAID6 array. Debian 7 64bit Linux General MariaDB info: v10.1.16 installed from MariaDB repos. 12,000 connection limit <1,000 typically used. Using XtraDB on all DBs other than "mysql". InnoDB pool size 15GB Total DB file size ~3GB Adaptive hash index turned off Individual InnoDB files Workload has heavy writes, lots of subqueries and temp tables. I counted up the various wait messages and grouped them by source file and line # and came up with this: lock0lock.cc:05075: 16 lock0lock.cc:06671: 2 lock0lock.cc:06822: 18602 lock0lock.cc:07078: 2 lock0lock.cc:07159: 2492 lock0lock.cc:07631: 16 lock0lock.cc:07721: 6 lock0wait.cc:00079: 34301 lock0wait.cc:00097: 9 lock0wait.cc:00247: 22996 lock0wait.cc:00291: 2 lock0wait.cc:00358: 22 lock0wait.cc:00485: 11 lock0wait.cc:00543: 14 row0ins.cc:01846: 60 row0mysql.cc:01772: 172 row0undo.cc:00298: 619 srv0srv.cc:02874: 349 srv0srv.cc:03573: 2 trx0rec.cc:01458: 97 This was from the period of time covering from when I noticed a problem up to the time I shutdown MariaDB. I'm sure there are plenty of dupes in there. But thought that it might give someone an idea of where to look next. I'm not sure where to start looking so I was hoping to get pointed in the right direction. I have config files, log output and probably anything else someone might want. Thanks in advance for any help! THX - Jon -- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about Jon Foster JF Possibilities, Inc. j...@jfpossibilities.com 541-410-2760 Making computers work for you! ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
