- discuss - lists.mariadb.org

[Maria-discuss] Bundle more relevant cnf files in MariaDB package
by Haidong Ji 04 Apr '11

04 Apr '11

Hi, I alluded to this in IRC maybe a couple of weeks back. That is, it is really to have intelligent default for MariaDB servers. In particular, the bundled sample my.cnf files, under /usr/local/mysql/support-files, such as my-small.cnf, my-medium.cnf, my-large.cnf, and my-huge.cnf, are laughable in today's world. In the my-huge.cnf, it talks about memory between 1G and 2G as huge. It will be good that MariaDB can bundle a different set, like what has been mentioned here: http://datastrangler.com/windpipe/2011/02/24/custom-mysql-config-files-to-e… I think the sample cnf files in the above blog post is a good starting point. Thanks, Haidong "Alex" Ji PS: I modified http://kb.askmonty.org/v/installing-mariadb-binary-tarballs with the addition of modifying $PATH so a casual user will be able to use various MariaDB clients after the install.

6 14

[Maria-discuss] The Plugins & Storage Engines Summit for MySQL/MariaDB/Drizzle 2011
by Colin Charles 01 Apr '11

01 Apr '11

Hi! Are you a developers who is writing a storage engines or plugins, knowing the plugin architecture of either MySQL, the extensions in MariaDB as well as the differences in Drizzle? Or are you writing User defined functions (UDF)? Or are you interested in developing something related to the MariaDB ecosystem? Then you should be at the summit on April 15 2011 Find out more at: http://kb.askmonty.org/v/storage-engine-summit-2011 -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/

2 1

[Maria-discuss] Segfaulting with signal 6
by Lance Albertson 30 Mar '11

30 Mar '11

I've run into another weird problem where MariaDB is segfaulting and dieing on Gentoo Hardened Linux. I can't figure out if its a weird situation with my Gentoo environment on the machine or something with MariaDB itself. I don't have this problem on the other machine running MariaDB. It seems to happen under load about once or twice a day. I have a nearly identical machine that doesn't have any of these problems. I'm running mariadb-5.1.50 under Hardened Gentoo. The compiled flags are: --- Configuration summary for MariaDB Server version 5.1.50-MariaDB * Installation prefix: /usr * System type: pc-linux-gnu * Host CPU: x86_64 * C Compiler: x86_64-pc-linux-gnu-gcc (Gentoo Hardened 4.4.4-r2 p1.2, pie-0.4.5) 4.4.4 * C++ Compiler: x86_64-pc-linux-gnu-g++ (Gentoo Hardened 4.4.4-r2 p1.2, pie-0.4.5) 4.4.4 * Debug enabled: no * Community Features: yes --- $ ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libexecdir=/usr/sbin --sysconfdir=/etc/mysql --localstatedir=/var/lib/mysql --sharedstatedir=/usr/share/mysql --libdir=/usr/lib64/mysql --includedir=/usr/include/mysql --with-low-memory --with-client-ldflags=-lstdc++ --enable-thread-safe-client --with-comment=Gentoo Linux mariadb-5.1.50 --without-docs --without-big-tables --enable-local-infile --with-extra-charsets=all --with-mysqld-user=mysql --with-server --with-unix-socket-path=/var/run/mysqld/mysqld.sock --without-libwrap --enable-shared --enable-static --without-debug --with-charset=utf8 --with-collation=utf8_general_ci --without-embedded-privilege-control --without-embedded-server --with-ssl=/usr --enable-assembler --with-geometry --with-readline --with-zlib-dir=/usr/ --without-pstack --with-plugindir=/usr/lib64/mysql/plugin --enable-community-features --disable-profiling --with-maria-tmp-tables --with-libevent --with-plugins=csv,myisam,myisammrg,heap,archive,blackhole,maria,xtradb --without-plugin-example --without-plugin-ibmdb2i --without-plugin-partition --without-plugin-federated --without-plugin-ndbcluster --without-plugin-pbxt I haven't opened a bug with Gentoo yet (I'm actually developer myself). I figured I'd ask here first. Any help would be great. Thanks! Here's the output I have from the log file: mysqld: malloc.c:5153: malloc_consolidate: Assertion `nextchunk->fd_nextsize->bk_nextsize == nextchunk' failed. 110329 13:11:25 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=134217728 read_buffer_size=262144 max_used_connections=376 max_threads=401 threads_connected=80 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 445322 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x3518dccbaa0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x3519ebd3ea0 thread_stack 0x3c000 /usr/lib64/mysql/libmysys.so.0(my_print_stacktrace+0x3c) [0x3547393ab0c] /usr/sbin/mysqld(handle_segfault+0x3cc) [0x7d0ebd1c1c] /lib/libpthread.so.0(+0xf010) [0x35473f86010] /lib/libc.so.6(gsignal+0x35) [0x35472264135] /lib/libc.so.6(abort+0x180) [0x35472265550] /lib/libc.so.6(+0x72c6a) [0x354722a4c6a] /lib/libc.so.6(+0x72f2d) [0x354722a4f2d] /lib/libc.so.6(+0x751e4) [0x354722a71e4] /lib/libc.so.6(__libc_malloc+0x70) [0x354722a9900] /usr/sbin/mysqld(+0x5ad9cf) [0x7d0ee529cf] /usr/sbin/mysqld(+0x5f3bfb) [0x7d0ee98bfb] /usr/sbin/mysqld(+0x5ed71b) [0x7d0ee9271b] /usr/sbin/mysqld(+0x588aa3) [0x7d0ee2daa3] /usr/sbin/mysqld(rr_sequential(READ_RECORD*)+0x29) [0x7d0ecc4b69] /usr/sbin/mysqld(sub_select(JOIN*, st_join_table*, bool)+0x99) [0x7d0ec430b9] /usr/sbin/mysqld(+0x39e524) [0x7d0ec43524] /usr/sbin/mysqld(JOIN::exec()+0xbd7) [0x7d0ec53b47] /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st _order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x1b2) [0x7d0ec551a 2] /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x19c) [0x7d0ec55c5c] /usr/sbin/mysqld(+0x33955a) [0x7d0ebde55a] /usr/sbin/mysqld(mysql_execute_command(THD*)+0x405) [0x7d0ebe07f5] /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2f3) [0x7d0ebe5cf3] /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x53a) [0x7d0ebe6b2a] /usr/sbin/mysqld(libevent_thread_proc+0x182) [0x7d0ebda682] /lib/libpthread.so.0(+0x68c4) [0x35473f7d8c4] /lib/libc.so.6(clone+0x6d) [0x35472302b4d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x3518424f018 is an invalid pointer thd->thread_id=14399 thd->killed=NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. -- Lance Albertson Systems Administrator / Architect Open Source Lab Network Services Oregon State University

3 3

Re: [Maria-discuss] client library shared library version changed in 5.5.10
by Sergei Golubchik 28 Mar '11

28 Mar '11

Hi, Monty! On Mar 18, Michael Widenius wrote: > >>>>> "MARK" == MARK CALLAGHAN <mdcallag(a)gmail.com> writes: > > > I think there was discussion about how client library shared library > > versions during the Lisbon meeting. > > >> From http://dev.mysql.com/doc/refman/5.5/en/news-5-5-10.html > >>>> > > Incompatible Change: The shared library version of the client library > > was increased to 18 to reflect ABI changes, and avoid compatibility > > problems with the client library in MySQL 5.1. Note that this is an > > incompatible change between 5.5.10 and earlier 5.5 versions, so client > > programs that use the 5.5 client library should be recompiled against > > the 5.5.10 client library. > > Serg, as you have now probably have full insight into the MariaDB 5.5 > code, is it possible to keep the API compatible with MariaDB 5.1 / > MySQL 5.1 to not force all applications to have to be recompiled when > upgrading to 5.5 ? The API incompatibility was caused by migration to CMake. If you want to keep libraries compatible, if's something that Wlad may need to look into. Regards, Sergei

4 6

[Maria-discuss] Suggested sample my.cnf for MariaDB package
by Haidong Ji 25 Mar '11

25 Mar '11

All, I proposed updating the packaged my.cnf sample files before. After some thinking and deliberation, here are my thoughts on the sample my.cnf: 1. There are so many factors that affect settings in my.cnf so it is impossible to please everybody. There is a lot of debates on this. 2. There are values in having just ONE sample my.cnf to get beginners started 3. It should be short 4. It should incorporate best practices, to the extent that best practices can be agreed 5. It should benefit as many people as possible My proposal is pasted below. Comments welcome. At the same time, constant back-and-forth bickering won't benefit much either, in my opinion. Thanks, Haidong "Alex" Ji # MariaDB/Percona/Oracle MySQL programs look for option files in a set of # locations which depend on the deployment platform. # You can copy this option file to one of those # locations. For information about these locations, see: # http://dev.mysql.com/doc/mysql/en/option-files.html # # For detailed definition of settings, see URL below: # http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html # Please do your own research, consult various resources # and experts for optimal settings for your own needs. # Some basic ones are provided below to get you started. # The following options will be passed to all MySQL clients [client] port = 3306 socket = /var/lib/mysql/mysql.sock # The MySQL server [mysqld] port = 3306 socket = /var/lib/mysql/mysql.sock user=mysql log-bin = mysql-bin log-slow-queries sync_binlog = 1 expire_logs_days= 10 wait_timeout = 30 #server-id = last octet of IP address #character-set-server = utf8 [mysqldump] quick

4 6

Re: [Maria-discuss] Suggested sample my.cnf for MariaDB package
by Haidong Ji 20 Mar '11

20 Mar '11

Hi Monty, > The problem is that a too simple my.cnf will please very few (mainly > desktop users) and leave the a bit more advanced user to search on > the net and get 'anything' that looks remotely right. > I respectfully disagree. I think the sample my.cnf is targeted for desktop users, medium-sized company users, and small business owners whose expertise is low and frustration level can run high. A generic, simple, and short my.cnf file serves that constituents well, gains their confidence, and is conducive in building up their comfort and skill level gradually, that they would seek information themselves on the web and/or ask expert for help as the need for performance/scalability rises. But that is AFTER they are comfortable enough with the ease, power, and simplicity of MariaDB. In other words, my view is that its target audience is not big size social network sites, Facebook, Google, and other money-rich financial companies. Those guys probably don't need the built-in sample anyway. Personally, I feel a minimalistic file works the best. This is not a debate of enterprise-worthiness of MariaDB/Percona/MySQL. It is. It's just that I think the sample's target is small scale users, relatively speaking. > I prefer the other approach taken by most unix programs (like postfix) > have taken where you have most important options in the config file, > but the not common ones are commented, with a good explanation of when > to enable the option. This is makes it much faster to get good > options without having to go trough a lot of manuals and web sites... This will make it long, which tends to cause confusion. A typical user/developer will be overwhelmed by the slew of jargons, which is a turn-off, IMHO. Given the importance of key_buffer_cache, however, perhaps that should be mentioned as a comment. > I also personally like the original approach with small, medium, large and > huge default config files, but now with many storage engines these are > also not as valid as they originally where. (And I agree with Arjen > that many of the values needs to be updates). I actually went ahead with that assumption as well initially, but after some thinking, I feel that contradict with the simplicity rule, so I stopped. But the idea is still good, in my mind. So perhaps we can put my-1gb.cnf, my-4gb.cnf, my-32gb.cnf on the knowledgebase? > > What should (at least) be done is to create new sections to the my.cnf > files that one can easily enable if one uses different storage > engines. I would also like to see more options and better comments in > the defaults file. > I agree, but I think we should NOT put in samples for every storage engine under the sun. Once again, simplicity rules in my mind, so we need only cover 2: MyISAM (Aria when Aria is mature enough to phase out MyISAM) and InnoDB. I do realize that in the sample I sent out, I didn't put any for InnoDB, which is probably not a good idea. > I have this week actually added to MariaDB 5.2 some new startup > options and groups to be able to make the option files smaller. > > For example, now in 5.2 both the server and clients are reading the > 'client-server' group, so one doesn't have to specify the socket and > port twice. > > I also added and --log-basedir so that one can specify the name for > all log files with one command (instead of having to use 8+ different > options) and new groups [mariadb] and [client-mariadb] so that one can > use the same config file for MySQL and MariaDB running on the same > computer. > That's fantastic! In summary, it appears that we disagree quite a bit on this. And the main point of contention, I think, is who is the target audience. There is definitely a need to replace/update the current ones, though. What about we package a minimalist sample my.cnf, and put a line in it pointing to a web page on KnowledgeBase that has more samples available with better explanation. Better yet, it is a wiki so the knowledge can be crowd-sourced. Haidong

1 0

[Maria-discuss] client library shared library version changed in 5.5.10
by MARK CALLAGHAN 18 Mar '11

18 Mar '11

I think there was discussion about how client library shared library versions during the Lisbon meeting. >From http://dev.mysql.com/doc/refman/5.5/en/news-5-5-10.html >>> Incompatible Change: The shared library version of the client library was increased to 18 to reflect ABI changes, and avoid compatibility problems with the client library in MySQL 5.1. Note that this is an incompatible change between 5.5.10 and earlier 5.5 versions, so client programs that use the 5.5 client library should be recompiled against the 5.5.10 client library. >>> -- Mark Callaghan mdcallag(a)gmail.com

1 0

[Maria-discuss] Installation problems of 5.2 in debian squueze
by Πρεκατές Αλέξανδρος 13 Mar '11

13 Mar '11

Hi. in debian squeeze trying to install mariaDB5.2 i get a conflict with mysql- core used by aconandi. what should i do? Thanks. aprekates

2 4

[Maria-discuss] askmonty.org vs kb.askmonty.org
by MARK CALLAGHAN 13 Mar '11

13 Mar '11

Why must I have separate logins for askmonty.org and kb.askmonty.org. I was confused by this and assume others will be confused by it. This isn't efficient. After logging into kb.askmonty.org and going to my profile page, there is no option to change my password. I am "Mdcallag" on both kb.askmonty.org and askmonty.org After logging into kb.askmonty.org I get "403 ERROR: Access denied" on everything including: http://kb.askmonty.org/v/plans-for-56 http://kb.askmonty.org/v/legal http://kb.askmonty.org/v/about -- Mark Callaghan mdcallag(a)gmail.com

1 0

Re: [Maria-discuss] Bundle more relevant cnf files in MariaDB package
by Haidong Ji 12 Mar '11

12 Mar '11

cool, Kurt von Finck, I will do it. I couldn't find a good enough translation in English of the “遣将不如激将” phrase, but I like your message. I will dig around the source code base in Launchpad, and get this damn thing started. I bet those config files are old relic from 10 years ago, or even more. 可八方，好，“遣将不如激将”，我会按你的建议去做！ On Fri, Mar 11, 2011 at 5:23 PM, Kurt von Finck <kurt(a)montyprogram.com> wrote: > On Fri, Mar 11, 2011 at 2:56 PM, Haidong Ji <haidong.ji(a)gmail.com> wrote: >> Hi, >> >> I alluded to this in IRC maybe a couple of weeks back. That is, it is >> really to have intelligent default for MariaDB servers. >> >> In particular, the bundled sample my.cnf files, under >> /usr/local/mysql/support-files, such as my-small.cnf, my-medium.cnf, >> my-large.cnf, and my-huge.cnf, are laughable in today's world. In the >> my-huge.cnf, it talks about memory between 1G and 2G as huge. It will >> be good that MariaDB can bundle a different set, like what has been >> mentioned here: >> >> http://datastrangler.com/windpipe/2011/02/24/custom-mysql-config-files-to-e… >> >> I think the sample cnf files in the above blog post is a good starting point. >> >> Thanks, >> Haidong "Alex" Ji >> >> PS: I modified http://kb.askmonty.org/v/installing-mariadb-binary-tarballs >> with the addition of modifying $PATH so a casual user will be able to >> use various MariaDB clients after the install. > > Not to sound snarky, but MariaDB is an open project. I would encourage > you to create sample my.cnf files, and submit them with bzr for review > and approval by a maria-captain. > > The real beauty of an open project is the ability to DIY for the > improvements and changes you think are important. Just Do It. :) > > -- > ./k > > Kurt von Finck > Chief Community And Communications Officer > Monty Program > http://montyprogram.com >

1 0