[Maria-discuss] Newbie Question - Multi-Master vs Cluster
Hi all, Up until now we have only directly managed stand alone MySQL instances. For clusters (MySQL) we have used a contractor to build and administrate the clusters. Our current product development requirements and good business practice (high availability of critical databases) now dictate that we move to a multi-server setup. Our goal is to setup at least two servers which will have the same data at all times and which are at separate sites so if the link between the sites goes down, the cell of servers at that site can keep operating. Our database stores text fields and blobs of audio recordings. We read data (SELECT with a WHERE) for 90-95% of our queries, some tables can be populated with hundreds of thousand of rows but normally far fewer. The software we are running which interacts with the database is smart enough to figure out if one of the database servers it is trying to reach is not responding and will hunt through a list of IP's until it successfully connects. I have a couple of questions as this will be our first cluster. (I don't think multi-master will meet our requirements based on the examples available online so I have chosen MariaDB 10 with Galera.) How often is complex management (manual intervention) required such as adding a node back into the cluster after communications between the nodes fails and then is restored? Is it normal, say 90% of the time, for syncing to re-establish automatically? What type of monitoring tools are advised? (Or is it as simple as automatically parsing logs to find errors?) The documented recommendation is 3 servers; we don't have the hardware at the moment so is it ok to start with 2 and add an additional database server at a later time? Alternatively, we could use 2 dedicated servers and 1 virtual server but the documentation states that the cluster only works as quickly as the slowest node. Is that only if you are running queries against the slowest node? Or if you are writing to the slowest node? I am assuming we can run the arbiter (garbd) on one of the existing data nodes. I am assuming we can use the SSL options in the configuration file to secure communication between the servers so if it was sniffed it would not be possible to decode the data. Does anyone have any comments on if this affects reliability? Thank you for any input you have on these questions. Please feel free to ask if you want clarification on anything. ___ 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] The relay-log is not fluashed after the slave-relay-log.999999 showed
Gmail next1...@gmail.com writes: And, as I mentioned at the title of this question, the relay-log is not flushed after the slave-relay-log.99 showed when using Salve_parallel_threads:10 setting. like showed blow. - binlog_format: ROW - Slave_parallel_threads:10 Everything are working fine except the slave-relay-log.** files continue to exist at the disk which will finally cause the disk full. If I change the value of Slave_parallel_threads setting from 10 to 0, the log will be flushed. Howevery PK duplicate warning error logs come next. Ok, thanks for reporting this. It's probably a bug that parallel replication behaves differently from non-parallel. I'll try to look into it when I have time. I could imagine that there are more bugs lurking when the log counter overflows... I'm not sure this is well tested. I wonder what the correct behaviour is? Should it just continue with slave-relay-log.100 ? Thanks, - Kristian. ___ 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] The relay-log is not fluashed after the slave-relay-log.999999 showed
Hello, dear users. I am using MariaDB 10.0.14 at CentOS 6.5. And, as I mentioned at the title of this question, the relay-log is not flushed after the slave-relay-log.99 showed when using Salve_parallel_threads:10 setting. like showed blow. - binlog_format: ROW - Slave_parallel_threads:10 Everything are working fine except the slave-relay-log.** files continue to exist at the disk which will finally cause the disk full. If I change the value of Slave_parallel_threads setting from 10 to 0, the log will be flushed. Howevery PK duplicate warning error logs come next. Is there any setting should be used with Slave_parallel_threads setting? Any help will be great. Best regareds, - Jasung ___ 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] R: Oracle sets 'tone' and standard/level of discussion
Am 05.01.2015 um 07:52 schrieb Stewart Smith: Quanah Gibson-Mount qua...@zimbra.com writes: --On Thursday, December 04, 2014 11:11 PM + Federico Razzoli federico_...@yahoo.it wrote: And I wrote: In other words, distros that prefer MariaDB are unstable and not mature? This post is offensive. Shame on this kind of marketing. But I don't think that these guys accept criticism. It's against their religion. People still use mysql? ;) From Debian popcon: mysql-server-core-5.5 43643 mysql-server-core-5.1 10584 mysql-server-5.19617 mysql-server-5.04001 mariadb-server 1115 mariadb-server-core-10.0 644 mariadb-server-10.0 636 mariadb-server-5.5 588 drizzle 106 the world is not Debian/Ubuntu nor has free software spy-functions on by default and sou you have no real conuts If we go by http://mariadb.org/feedback_plugin/stats/server_count_by_month/ then we see that Maria is hedging towards 6,000 installs reporting back. RHEL//CentOS7/Fedora are using MariaDB as *default* MySQL replacement and likely exceed that 6000 installs, i personally count 15 and they are not reporting back - why should they? ALthough some of the other stats give different totals, so I'm really not sure what to make of that. signature.asc Description: OpenPGP digital signature ___ 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
