#maria Log v0.1

logs Catalogue

This page loads from the db, refresh as and when. It displays 24 hrs
For older data http://marialog.archivist.info/previous.php, logs go back to 2009-01-18
Some user stats
Table logs
date_time
user
message
2016-09-26 02:56:06
ixor
:)
2016-09-26 04:00:30
kaos01
hi im getting this mariadb-5.5.50-1.el7_2.x86_64 is obsoleted by mysql-community-client-5.6.23-3.el7.x86_64 which is already installed
2016-09-26 04:00:48
kaos01
gussing its due to the versions ?
2016-09-26 11:34:32
karatecode
Hi. I saw that wsrep_sync_wait was introduced in 10.0.13, but I can't find it in 10.1.16. What's wrong?
2016-09-26 11:41:08
serg
it exists in 10.1.16 all right, I've just checked
2016-09-26 11:46:14
karatecode
Ok, thanks. Then it's just something wrong with me then. :) It does not show when I run "show status like "wsrep%"
2016-09-26 11:48:07
karatecode
Oh, and btw. I don't understand why I should choose the glib version over the other.
2016-09-26 11:51:40
serg
some plugins require newer libraries, but we still want users with old glibc to run mariadb even if without some plugins
2016-09-26 11:54:06
karatecode
Ok, so unless I want plugins there's no reason to use the glibc-version?
2016-09-26 11:55:43
serg
unless you want some specific plugins, if I'm not mistaken it's oqgraph and tokudb
2016-09-26 11:56:57
karatecode
Ok, thanks. I'll stick with the non-glibc then.
2016-09-26 11:59:00
karatecode
But it's still the question why I cannot see wsrep_sync_wait. I have installed mariadb over mysql, and I have run service mysql start --wsrep_on=OFF; mysql_upgrade; service mysql stop; service mysql start --wsrep_new_cluster
2016-09-26 12:31:17
karatecode
Now I found that wsrep_casual_reads is depricated by wsrep_sync_wait, but wsrep_causal_reads is what I see when I run show status like "wsrep%"
2016-09-26 12:50:54
karatecode
Sorry for repeating myself, but what's wrong if I find wsrep_casual_reads instead of wsrep_sync_wait? I'm using MariaDB 10.1.16
2016-09-26 12:52:14
jkavalik
karatecode, write "\s" into your console, that will return server info containing both mariadb and wsrep versions
2016-09-26 12:54:18
karatecode
jkavalik: I did now, but I don't understand what I should look for
2016-09-26 12:55:07
karatecode
jkavalik: http://pastebin.com/Kc8rSLZm
2016-09-26 12:57:18
jkavalik
karatecode, hm, our (10.0) server responds with the version of the wsrep in "Server version: 10.0.17-MariaDB-wsrep-log MariaDB Server, wsrep_25.10.r4144" - so I expected 10.1 to show something like that too.. no idea then, sorry
2016-09-26 12:59:16
TvL2386
hi guys, I have 1 server running mariadb-server-5.5 and 2 webservers having mariadb-client-5.5. When I upgrade the database server to mariadb-server-10.0, do I also need to upgrade the 2 webservers?
2016-09-26 12:59:48
TvL2386
the webservers are running a tomcat app and php app with their own database on the database server
2016-09-26 13:00:14
karatecode
jkavalik: Thanks anyway. So I guess that I just have set casual_reads to ON before doing a page switch then.
2016-09-26 13:25:15
nirbhay
karatecode, wsrep_sync_wait is a system variable (not status variable).
2016-09-26 13:28:35
karatecode
nirbhay: Oh, thank you very much.
2016-09-26 13:28:55
grknight
TvL2386: the protocol between versions doesn't change so it is not required, plus if you are using the php mysqlnd driver (recommended) the code is native to PHP and not reliant on outside libraries
2016-09-26 13:29:15
karatecode
nirbhay: So when I want to activate syncronous replication, I change that variable?
2016-09-26 13:32:00
TvL2386
grknight, tyvm!
2016-09-26 13:32:05
nirbhay
karatecode, You will have to configure the mandatory ones - https://mariadb.com/kb/en/mariadb/getting-started-with-mariadb-galera-cluster/#mandatory-settings
2016-09-26 13:35:55
karatecode
nirbhay: Yep, all those are fixed. Does that mean that I when I want to use syncrounus replication I run "set wsrep_sync_wait = 1;"?
2016-09-26 13:36:38
karatecode
nirbhay: My question is: Can I change async to sync replication while the daemon is running?
2016-09-26 13:37:15
nirbhay
karatecode, for synchronous read view, yes.
2016-09-26 13:38:30
karatecode
nirbhay: Thank you. However, I did that on one node, but I did not see that variable change on the other node. Is that normal? (I'm a complete noob on this, but I have googled a lot)
2016-09-26 13:38:33
nirbhay
karatecode, I believe, that will require a server restart.
2016-09-26 13:40:32
nirbhay
karatecode, Yes, variables changes do not replicate to other nodes. You will have to update them on all the nodes.
2016-09-26 13:44:09
karatecode
nirbhay: Ah, so if node1 has sync_wait set, but node0 doesn't, it will run as normal, but node1 will not report ok until node2 is updated, but node2 will not do the same?
2016-09-26 13:48:47
nirbhay
karatecode, sort of, sync_wait does not affect replication. If set, it ensures that that a command from client is not executed until previous commands have been applied on all the node.
2016-09-26 13:48:58
nirbhay
all the nodes, that is.
2016-09-26 13:50:09
karatecode
nirbhay: That's what I meant. Thank you very much. My plan is to use this flag to upgrade the software without downtime.
2016-09-26 15:17:40
karatecode
Strange. I tried to set wsrep_sync_wait to 7. A show variable showed that it indeed had that number. Then I ran a testscript which tests to write to one node and read from another. It failed. When I checked wsrep_sync_wait it was reset to 0.