- developers - lists.mariadb.org

[Maria-developers] Not able to run MariaDB after building from source
by Sonali Ellath 05 Jan '16

05 Jan '16

Hi, I am Sonali looking to participate in this years Google Summer of Code. I was hoping to contribute to MariaDb. I tried building MariaDb from source using instructions found here <https://mariadb.com/kb/en/mariadb/generic-build-instructions/>. Configure, make and make install were successful. But I faced problem under section Starting MariaDB for the first time. When I executed the step: > scripts/mysql_install_db --user=mysql > I received an error saying: ... > [Note] InnoDB: The InnoDB memory heap is disabled > [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins > [Note] InnoDB: Memory barrier is not used > [Note] InnoDB: Compressed tables use zlib 1.2.8 > [Note] InnoDB: Using Linux native AIO > [Note] InnoDB: Using SSE crc32 instructions > [Note] InnoDB: Initializing buffer pool, size = 128.0M > [Note] InnoDB: Completed initialization of buffer pool > [ERROR] InnoDB: Data file ./ibdata1 is of a different size 768 pages > (rounded down to MB) than specified in the .cnf file 64000 pages! > [ERROR] InnoDB: Could not open or create the system tablespace. If you > tried to add new data files to the system tablespace, and it failed here, > you should now edit innodb_data_file_path in my.cnf back to what it was, > and remove the new ibdata files InnoDB created in this failed attempt. > InnoDB only wrote those files full of zeros, but did not yet use them in > any way. But be careful: do not remove old data files which contain your > precious data! > [ERROR] Plugin 'InnoDB' init function returned error. > [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. > [ERROR] Unknown/unsupported storage engine: InnoDB > [ERROR] Aborting > > Installation of system tables failed! Examine the logs in > ./data for more information. > The problem could be conflicting information in an external > my.cnf files. You can ignore these by doing: > > shell> ./bin/scripts/mysql_install_db --defaults-file=~/.my.cnf > > You can also try to start the mysqld daemon with: > > shell> ./bin/mysqld --skip-grant --general-log & > > and use the command line tool ./bin/mysql > to connect to the mysql database and look at the grant tables: > > shell> ./bin/mysql -u root mysql > mysql> show tables; > So I tried to run mysqld but that didn't work either. I had MySql installed earlier, but I removed it because it was getting very confusing with that. I also tried to run from source as mentioned here <https://mariadb.com/kb/en/mariadb/running-mariadb-from-the-source-directory/>. But it gives the following error: > ERROR 2002 (HY000): Can't connect to local MySQL server through socket > '/tmp/mysql.sock' (111 "Connection refused") I made sure that I uncommented lines from my.cnf which had sock information under client and server. Thanks in advance Sonali

2 1

[Maria-developers] MariaDB plugin package names (in Debian) scheme: mariadb-plugin-<name>
by Otto Kekäläinen 04 Jan '16

04 Jan '16

Hello! Currenlty we have storage engine packages named mariadb-oqgraph-engine-10.0 mariadb-connect-engine-10.0 Serg suggested in the summer that the version number should be dropped from the engine/plugin package names (it is enough to have it in the package metadata). I was now also thinking that the naming scheme of the base name should change to mariadb-plugin-oqgraph mariadb-plugin-connect The motivation is that plugin is more universal than 'engine' as some plugins are not engines, and by having all plugins prepended with mariadb-plugin-* they list nicer in alphabetical listings. What do you think? I already experimented in the lines of this with http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=97b3c4…

2 3

[Maria-developers] TokuDB QA issues - should we fix them ourself or are any of the upstream devs listening?
by Otto Kekäläinen 04 Jan '16

04 Jan '16

Hello! While working on the Debian packaging I noticed multiple minor QA level issues that stem from problems in TokuDB: - Debian builds are not reproducable due to random embedded build id in the TokuDB plugin, see https://reproducible.debian.net/dbd/unstable/amd64/mariadb-10.0_10.0.23-1.d… (subpage of https://reproducible.debian.net/rb-pkg/unstable/amd64/mariadb-10.0.html) - Lintian complains about missing man page for binary tokuftdump. Also Lintian complains about outdated autotool files in TokuDB sources. For both see https://lintian.debian.org/maintainer/pkg-mysql-maint@lists.alioth.debian.o… I'd like to see these fixed. What is the best process to proceed with these? File an issue at mariadb.org/jira or https://github.com/percona/PerconaFT or what..? Please advice. - Otto MariaDB Foundation

3 2

[Maria-developers] Documentation for new features
by Ian Gilfillan 03 Jan '16

03 Jan '16

Hi I quite often find out about a new feature after release, either by looking through the changelog and commits, or because someone points out it's missing from the documentation. It's time-consuming trying to keep track of every change, and I miss things (especially in non-default plugins etc), so it'd be better if everyone can remember the need for documentation when adding new features/variables or changes in behaviour. Each task of this sort in JIRA could have a related documentation subtask. You can add to the knowledgebase directly (don't worry about bad English, I will fix), email me with details, or at least alert me about an impending change. thanks, ian

4 4

[Maria-developers] Should these files be included in the Debian packages?
by Otto Kekäläinen 02 Jan '16

02 Jan '16

Hello! While working on MDEV-9259 I did some comparisons about what files in general are created by the build but which are missing from the Debian packaging. The list is below. Please advise which should be included and which are OK to leave out. etc/mysql/conf.d/cassandra.cnf etc/mysql/conf.d/dialog.cnf etc/mysql/conf.d/oqgraph.cnf usr/bin/mysql_config usr/bin/mysql_embedded usr/bin/mytop usr/include/mysql/*.h usr/lib/mysql/plugin/dialog.so usr/lib/mysql/plugin/mysql_clear_password.so usr/share/mysql/mroonga/install.sql usr/share/mysql/mroonga/uninstall.sql usr/share/mysql/my-huge.cnf usr/share/mysql/my-innodb-heavy-4G.cnf usr/share/mysql/my-large.cnf usr/share/mysql/my-medium.cnf usr/share/mysql/my-small.cnf usr/share/mysql/mysqld_multi.server usr/share/mysql/mysql-log-rotate usr/share/mysql/mysql.server usr/sql-bench/*

4 6

[Maria-developers] Student looking to contribute to MariaDB
by Rishab Jaju 31 Dec '15

31 Dec '15

Hello everybody, I am a third year student looking to contribute towards MariaDB for the upcoming Google Summer of Code program. I am very proficient in C++, Java, Python and Scheme. I have done some projects in machine learning as well as NLP. My exposure to databases is limited to an undergraduate course on Database systems. What level of knowledge would I need to contribute to the project? What sort of project would be appropriate for my skill set? Thank you, Rishab Jaju.

2 1

Re: [Maria-developers] [Commits] b904ca0: MDEV-9297 - mysql_install_db launches mysqld 3x
by Sergei Golubchik 29 Dec '15

29 Dec '15

Hi, Sergey! On Dec 23, Sergey Vojtovich wrote: > revision-id: b904ca0c2e9e35ffecb314f1082e45bfb42038f3 (mariadb-10.1.8-99-gb904ca0) > parent(s): 29290a3d53a05bd7177bcf7de05e1c8fff6e9cea > committer: Sergey Vojtovich > timestamp: 2015-12-23 15:52:34 +0400 > message: > > MDEV-9297 - mysql_install_db launches mysqld 3x > > Perform database installation in one mysqld run. This makes mysql_install_db > 3x faster. > > diff --git a/scripts/mysql_install_db.sh b/scripts/mysql_install_db.sh > index f8f36bf..9dcd23a 100644 > --- a/scripts/mysql_install_db.sh > +++ b/scripts/mysql_install_db.sh > @@ -427,7 +427,7 @@ mysqld_install_cmd_line() > > # Create the system and help tables by passing them to "mysqld --bootstrap" > s_echo "Installing MariaDB/MySQL system tables in '$ldata' ..." > -if { echo "use mysql;"; cat "$create_system_tables" "$create_system_tables2" "$fill_system_tables"; } | eval "$filter_cmd_line" | mysqld_install_cmd_line > /dev/null > +if { echo "use mysql;"; cat "$create_system_tables" "$create_system_tables2" "$fill_system_tables" "$fill_help_tables" "$maria_add_gis_sp"; } | eval "$filter_cmd_line" | mysqld_install_cmd_line > /dev/null > then > s_echo "OK" > else > @@ -462,26 +462,6 @@ else > exit 1 > fi > > -s_echo "Filling help tables..." > -if { echo "use mysql;"; cat "$fill_help_tables"; } | mysqld_install_cmd_line > /dev/null > -then > - s_echo "OK" > -else > - echo > - echo "WARNING: HELP FILES ARE NOT COMPLETELY INSTALLED!" > - echo "The \"HELP\" command might not work properly." > -fi > - > -s_echo "Creating OpenGIS required SP-s..." > -if { echo "use test;"; cat "$maria_add_gis_sp"; } | mysqld_install_cmd_line > /dev/null > -then > - s_echo "OK" > -else > - echo > - echo "WARNING: OPENGIS REQUIRED SP-S WERE NOT COMPLETELY INSTALLED!" > - echo "GIS extentions might not work properly." > -fi Uhm, I don't know. I believe the point was not to treat fill_help_tables failure as fatal. To keep this logic you can merge maria_add_gis_sp and fill_help_tables in one mysqld_install_cmd_line invocation. But that's all. On the other hand, perhaps it's not important to preserve this logic? Then your patch is fine... Regards, Sergei Chief Architect MariaDB and security(a)mariadb.org -- Vote for my Percona Live 2016 talks: https://www.percona.com/live/data-performance-conference-2016/sessions/mari… https://www.percona.com/live/data-performance-conference-2016/sessions/mari…

2 2

Re: [Maria-developers] [Commits] 05c122b: MDEV-8491 - On shutdown, report the user and the host executed that.
by Sergei Golubchik 28 Dec '15

28 Dec '15

Hi, Sergey! On Dec 24, Sergey Vojtovich wrote: > revision-id: 05c122b3ccd0102a3414a7d59313e6662a1fd5e4 (mariadb-10.1.8-101-g05c122b) > parent(s): 7c533a17523d2d6ef380487ab35151da0208090f > committer: Sergey Vojtovich > timestamp: 2015-12-24 19:53:44 +0400 > message: > > MDEV-8491 - On shutdown, report the user and the host executed that. ok to push Regards, Sergei Chief Architect MariaDB and security(a)mariadb.org -- Vote for my Percona Live 2016 talks: https://www.percona.com/live/data-performance-conference-2016/sessions/mari… https://www.percona.com/live/data-performance-conference-2016/sessions/mari…

1 0

[Maria-developers] Option to _not_ disable semisync on slave timeout?
by Kristian Nielsen 28 Dec '15

28 Dec '15

Hi Jonas (or anyone else who may know), If I understand correctly, semisync replication has a timeout for how long it will wait for a slave to acknowledge transactions. If the timeout is exceeded, semisync is turned off on the master. Do you know if there is a facility to avoid semisync being turned off automatically in this case, maybe instead fail and roll back the master transaction? I was thinking at Google you might already have needed and implemented this (merged or not merged into MariaDB yet), or you may be aware of a patch by someone else for this? Thanks, and merry Christmas! - Kristian.

3 2

Re: [Maria-developers] [Commits] a1ab431: MDEV-7261 - Backport the default autosized value of
by Sergei Golubchik 28 Dec '15

28 Dec '15

Hi, Sergey! On Nov 20, Sergey Vojtovich wrote: > revision-id: a1ab4314d1f88fa954a774c322709822d7b95344 (mariadb-10.1.8-58-ga1ab431) > parent(s): cfc135b645db5fa78b9f63b1959ea3f2be137a26 > committer: Sergey Vojtovich > timestamp: 2015-11-20 17:32:26 +0400 > message: > > MDEV-7261 - Backport the default autosized value of > "table_definition_cache" from MySQL 5.6.8+ > > Fixed table_definition_cache auto-sizing. Note that this patch doesn't > address broken PFS auto-sizing. Do you plan to address it after you've broken it? How? Regards, Sergei

2 9