wiki:qclug_meeting_minutes_2-7-2017
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
wiki:qclug_meeting_minutes_2-7-2017 [2017/02/08 01:55] Aaron Johnson |
wiki:qclug_meeting_minutes_2-7-2017 [2017/02/08 02:48] (current) Aaron Johnson |
||
|---|---|---|---|
| Line 28: | Line 28: | ||
| side converstation: | side converstation: | ||
| - tom was reminiscing of when there were internet yellow pages types books | - tom was reminiscing of when there were internet yellow pages types books | ||
| - | - | + | - openstack was brought up (which uses mysql galera and pacemaker as well) and we found that travis's demo cluster was very similar to how openstack works. |
| + | - tom mentioned that there are db2 databases and clients that implement high availability in a similar way but the clients are actually 'smart' and can actually choose another db server when connection issues occur. | ||
| topic presentation notes: | topic presentation notes: | ||
| - the actual galera presentation began at exactly 7:19PM (central) | - the actual galera presentation began at exactly 7:19PM (central) | ||
| Line 47: | Line 48: | ||
| - travis chose to go with mariadb | - travis chose to go with mariadb | ||
| - travis started his live demo at exactly 7:49 | - travis started his live demo at exactly 7:49 | ||
| - | - he decided to run his node-1 setup shell script before sharing the commands in the script, but this backfired because the live presentation god's frowned upon him and made his yum transacation for loading the mariadbs packages slower than dog shit. | + | - he decided to run his node-1 setup shell script before sharing the commands in the script, but this backfired because the live presentation god's frowned upon him and made his yum transaction for loading the mariadbs packages slower than dog shit. |
| - | - | + | - worth noting, galera does not seem to offer a security mechanisim to prevent new galera nodes from joining the cluster (other than a configuration option for setting a unique cluster name) |
| + | - tom wanted to know is galera is a name for a monster, we found that galera means "crowd" in portuguese | ||
| + | - the presentation switched gears and travis started talking about pacemaker/corosync | ||
| + | - corosync supports either multicast or unicast in a configuration called a ring | ||
| + | - it supports resource agents and fencing agents | ||
| + | - fencing agents are available via prepackaged scripts (to hardware kill a misbehaving node) | ||
| + | - however no one knows why anyone would actually use a fencing agent since all of the clusters we've been involved in do not actually use fencing agents... | ||
| + | - the presentation finished at 8:26 (on time) and the cluster was fully functional! | ||
| + | - we tested galera's ability to run as a single cluster node after "ungraceful" shutdown and galera will not run properly without manual intervention so a 3 node cluster or use of the galera arbitrator is recommended for a 2 node cluster. | ||
| </code> | </code> | ||
wiki/qclug_meeting_minutes_2-7-2017.1486518928.txt.gz · Last modified: 2017/02/08 01:55 by Aaron Johnson
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
