- discuss - lists.mariadb.org

[Maria-discuss] Idea of monitoring tool of Mariadb
by Seung Hoon Yoo 12 Feb '15

12 Feb '15

Hello, i think about monitoring gui tool ( sure, monyog Nagius support mariadb) Mysql Enterprise Monitor is cool, but commercial ver and that is oracle haha Anyway my idea first Performance schema info, that is store info in memory structure in source, so if during every 1 sec memcopy from performance schema to user-define structure and that information transfer out of mariadb by udp port etc.. So, until world in mysql / maria, their tool using proxy method or sql script thas will be some performance issue happen. so Direct Mariadb memory Access Method is useful.. So.. mariadb.com has any plan GUI Monitoring tool? and how about my idea about gathering performance schema ( + information_schema etc) info in mysqld thread info( memory structure) ?? Thanks for reading! p.s i am not used to english. ;) LG CNS post architecture Team

1 0

[Maria-discuss] New Question: Migrating MySQL 5.5 Windows to MariaDB 10.x on new Windows server
by AskMonty KB 11 Feb '15

11 Feb '15

Hello, A new question has been asked in "Moving to MariaDB" by davidgonsalves. Please answer it at http://mariadb.com/kb/en/migrating-mysql-55-windows-to-mariadb-10x-on-new-w… as the person asking the question may not be subscribed to the mailing list. -------------------------------- My company is contemplating moving from MySQL 5.5 to MariaDB 10.x. We don't want to do an in place upgrade because the existing server is an older machine running Win 2003 x64. We have a new server that we're going to build out (don't know complete specs yet), and would like to know how we can best migrate the existing MySQL instance to a new instance of MariaDB on the new server. Is it as simple as doing a mysqldump from the existing server and piping it into the new? I've read how to do it here: http://dba.stackexchange.com/questions/174/how-can-i-move-a-database-from-o… are these answers adequate? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/migrating-mysql-55-windows-to-mariadb-10x-on-new-w…

1 0

[Maria-discuss] New Question: XtraDB + query_cache_size MariaDB 10
by AskMonty KB 11 Feb '15

11 Feb '15

Hello, A new question has been asked in "MariaDB Community" by chrismatthews. Please answer it at http://mariadb.com/kb/en/xtradb-query_cache_size-mariadb-10/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi, I have read that if your using MySQL InnoDB then you should not use query_cache_size. Does this also apply to MariaDB 10 with XtraDB ? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/xtradb-query_cache_size-mariadb-10/

1 0

[Maria-discuss] New Question: Warning: mysqli::mysqli(): Headers and client library minor version mismatch.
by AskMonty KB 11 Feb '15

11 Feb '15

Hello, A new question has been asked in "MariaDB FAQ" by ariez_ahito_g. Please answer it at http://mariadb.com/kb/en/warning-mysqlimysqli-headers-and-client-library-mi… as the person asking the question may not be subscribed to the mailing list. -------------------------------- i am having error with phpipam installation in my centos box.. i got this error Warning: mysqli::mysqli(): Headers and client library minor version mismatch. Headers:50173 Library:50312 -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/warning-mysqlimysqli-headers-and-client-library-mi…

3 2

[Maria-discuss] New Question: Get the error log of Mariadb
by AskMonty KB 09 Feb '15

09 Feb '15

Hello, A new question has been asked in "MariaDB Community" by nunocarapito. Please answer it at http://mariadb.com/kb/en/get-the-error-log-of-mariadb/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi there. First of all sorry if I shouldn't be asking this. I have a big database with MariaDB running on CentOS 7, and recently it has been crashing about a time a day. I'm affraid to try anything and crush all database, making it offline for some time. I can't see what is the problem of it, because I cant find the error log of it. How can I enable it or start it? Thanks -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/get-the-error-log-of-mariadb/

1 0

[Maria-discuss] doubt... show table status
by Roberto Spadim 07 Feb '15

07 Feb '15

guys, i'm creating a table with: CREATE TABLE xxx SELECT * FROM yyyy this one take a long time (more than 1 hour) to end... my problem is... i'm using HeidiSQL sometimes to check tables and etc... when i open database it execute a SHOW TABLE STATUS FROM `database` but is blocked while create table don't end, could we implement a non block show table? or a timeout? -- Roberto Spadim SPAEmpresarial Eng. Automação e Controle

2 2

[Maria-discuss] Restated: JSON cannot represent binary data
by Tom Worster 06 Feb '15

06 Feb '15

I think we're getting lost in the detail. Beyond dispute are two facts: 1. BINARY is a valid datatype in dynamic columns. 2. JSON cannot represent binary data. It follows that: COLUMN_JSON() cannot (correctly) represent all dynamic column values. So I ask the question is: What *should* COLUMN_JSON() do when a dynamic column contains BINARY values? When I file a bug report, I like to give an expected result. I don't know what it is in this case. Every other decent JSON encoder errors on such input. Is that what Maria should do?

6 18

[Maria-discuss] direct send data to app client
by Roberto Spadim 04 Feb '15

04 Feb '15

... i was thinking about big table results, internall network use, and optimization ... should be interesting, if we have a database-side way to export data directly to app-client i'm thinking about a configuration like... client app ----(conect)---> app server, app mysql client ----(connect)---> mysql server client app send a post/get/or any other rpc/ipc method app server, execute some functions ask to mysql database and return data sometimes data is too big, and we transfer data from mysql to app, and from app to client, my idea is transfer mysql to client app this idea have some security problems, but let's think about the solution... at app server we send queries to server and report to server save it, server send a ticket, with a ttl or something like it, app them send this ticket to app client app client connect to mysql/mariadb server with a daemon plugin and 'download' this data i didn't google about this yet, but, should this be possible? in this case, i think the json/bson should be interesting since we need to translate the mysql rows/columns to a standard encode (probably json, bson, xml, html table, csv or something like it), i'm thinking about http/https (or any other network file system / file share protocol) protocol at mysql side or... i didn't think if that's possible without some patch... could the mysql server save the result to a file? like a mysqldump but using only SQL interface? maybe a create table with connect engine? ideas are wellcome -- Roberto Spadim

2 1

[Maria-discuss] MariaDB 10.0.16 now available
by Daniel Bartholomew 04 Feb '15

04 Feb '15

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.0.16 This is a Stable (GA) release. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.0.16 - Release Notes: https://mariadb.com/kb/en/mariadb-10016-release-notes - Changelog: https://mariadb.com/kb/en/mariadb-10016-changelog - Downloads: https://downloads.mariadb.org/mariadb/10.0.16 About MariaDB 10.0: - https://mariadb.com/kb/en/what-is-mariadb-100/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "feedback=ON" to your my.cnf or my.ini file! See http://mariadb.com/kb/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: - http://mariadb.org/jira - - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - - If you would like to contribute to the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/en/donate/ - http://www.cafepress.com/mariadb We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

7 16

[Maria-discuss] Sudden communication failure on MariaDB Galera Cluster
by Raina Masand 03 Feb '15

03 Feb '15

Hello, Recently, we experienced a sudden failure on a 3-node MariaDB Galera cluster (version 10.0.13), and can't find any documentation or discussion of these particular logs. Prior to the crash, our cluster seemed to be experiencing connectivity issues, and this particular node was partitioned from both its peers. It was in a non-primary state when the following occurred: 150126 6:26:16 [Note] WSREP: evs::proto(fee139da-a4dc-11e4-896b-13e5de7439e0, GATHER, view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,4)) suspecting node: b3156374-a4dc-11e4-90ef-7745fb12a381 150126 6:26:17 [Warning] WSREP: subsequent views have same members, prev view view(view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,4) memb { fee139da-a4dc-11e4-896b-13e5de7439e0,0 } joined { } left { } partitioned { }) current view view(view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5) memb { fee139da-a4dc-11e4-896b-13e5de7439e0,0 } joined { } left { } partitioned { }) 150126 6:26:17 [Note] WSREP: view(view_id(NON_PRIM,fee139da-a4dc-11e4-896b-13e5de7439e0,5) memb { fee139da-a4dc-11e4-896b-13e5de7439e0,0 } joined { } left { } partitioned { 7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,0 b3156374-a4dc-11e4-90ef-7745fb12a381,0 }) 150126 6:26:17 [Note] WSREP: New COMPONENT: primary = no, bootstrap = no, my_idx = 0, memb_num = 1 150126 6:26:17 [Note] WSREP: Flow-control interval: [16, 16] 150126 6:26:17 [Note] WSREP: Received NON-PRIMARY. 150126 6:26:17 [Note] WSREP: New cluster view: global state: 7ef7ed24-a4dc-11e4-be97-6ee0620c8266:43, view# -1: non-Primary, number of nodes: 1, my index: 0, protocol version 3 150126 6:26:17 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification. 150126 6:26:20 [Note] WSREP: (fee139da-a4dc-11e4-896b-13e5de7439e0, 'tcp:// 0.0.0.0:4567') reconnecting to 7ef72f2a-a4dc-11e4-8f5b-bb400fba8578 (tcp:// 10.85.49.128:4567), attempt 0 150126 6:26:28 [Note] WSREP: (fee139da-a4dc-11e4-896b-13e5de7439e0, 'tcp:// 0.0.0.0:4567') address 'tcp://10.85.49.130:4567' pointing to uuid fee139da-a4dc-11e4-896b-13e5de7439e0 is blacklisted, skipping 150126 6:26:28 [Note] WSREP: (fee139da-a4dc-11e4-896b-13e5de7439e0, 'tcp:// 0.0.0.0:4567') address 'tcp://10.85.49.130:4567' pointing to uuid fee139da-a4dc-11e4-896b-13e5de7439e0 is blacklisted, skipping 150126 6:26:28 [Note] WSREP: (fee139da-a4dc-11e4-896b-13e5de7439e0, 'tcp:// 0.0.0.0:4567') address 'tcp://10.85.49.130:4567' pointing to uuid fee139da-a4dc-11e4-896b-13e5de7439e0 is blacklisted, skipping 150126 6:26:28 [Note] WSREP: (fee139da-a4dc-11e4-896b-13e5de7439e0, 'tcp:// 0.0.0.0:4567') address 'tcp://10.85.49.130:4567' pointing to uuid fee139da-a4dc-11e4-896b-13e5de7439e0 is blacklisted, skipping 150126 6:26:28 [Note] WSREP: (fee139da-a4dc-11e4-896b-13e5de7439e0, 'tcp:// 0.0.0.0:4567') turning message relay requesting off 150126 6:26:28 [Warning] WSREP: evs::proto(fee139da-a4dc-11e4-896b-13e5de7439e0, INSTALL, view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5)) dropping foreign message from b3156374-a4dc-11e4-90ef-7745fb12a381 in install state 150126 6:26:28 [Warning] WSREP: evs::proto(fee139da-a4dc-11e4-896b-13e5de7439e0, INSTALL, view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5)) dropping foreign message from b3156374-a4dc-11e4-90ef-7745fb12a381 in install state 150126 6:26:28 [Warning] WSREP: evs::proto(fee139da-a4dc-11e4-896b-13e5de7439e0, INSTALL, view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5)) dropping foreign message from b3156374-a4dc-11e4-90ef-7745fb12a381 in install state 150126 6:26:28 [Warning] WSREP: evs::proto(fee139da-a4dc-11e4-896b-13e5de7439e0, INSTALL, view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5)) dropping foreign message from b3156374-a4dc-11e4-90ef-7745fb12a381 in install state 150126 6:26:28 [Warning] WSREP: evs::proto(fee139da-a4dc-11e4-896b-13e5de7439e0, INSTALL, view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5)) dropping foreign message from b3156374-a4dc-11e4-90ef-7745fb12a381 in install state 150126 6:26:28 [Warning] WSREP: evs::proto(fee139da-a4dc-11e4-896b-13e5de7439e0, INSTALL, view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5)) dropping foreign message from b3156374-a4dc-11e4-90ef-7745fb12a381 in install state 150126 6:26:28 [ERROR] WSREP: exception caused by message: evs::msg{version=0,type=3,user_type=255,order=1,seq=-1,seq_range=-1,aru_seq=-1,flags=4,source=7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,source_view_id=view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,6),range_uuid=00000000-0000-0000-0000-000000000000,range=[-1,-1],fifo_seq=176868,node_list=() } state after handling message: evs::proto(evs::proto(fee139da-a4dc-11e4-896b-13e5de7439e0, INSTALL, view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,6)), INSTALL) { current_view=view(view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,6) memb { 7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,0 } joined { } left { } partitioned { }), input_map=evs::input_map: {aru_seq=-1,safe_seq=-1,node_index=}, fifo_seq=176418, last_sent=11, known={ 7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,evs::node{operational=1,suspected=0,installed=1,fifo_seq=176868,join_message= evs::msg{version=0,type=4,user_type=255,order=1,seq=4,seq_range=-1,aru_seq=4,flags=4,source=7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,source_view_id=view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,5),range_uuid=00000000-0000-0000-0000-000000000000,range=[-1,-1],fifo_seq=176864,node_list=( 7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,node: {operational=1,suspected=0,leave_seq=-1,view_id=view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,5),safe_seq=4,im_range=[10,9],} b3156374-a4dc-11e4-90ef-7745fb12a381,node: {operational=0,suspected=1,leave_seq=-1,view_id=view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,5),safe_seq=4,im_range=[5,4],} fee139da-a4dc-11e4-896b-13e5de7439e0,node: {operational=1,suspected=0,leave_seq=-1,view_id=view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,4),safe_seq=0,im_range=[1,0],} ) }, } fee139da-a4dc-11e4-896b-13e5de7439e0,evs::node{operational=1,suspected=0,installed=1,fifo_seq=-1,join_message= evs::msg{version=0,type=4,user_type=255,order=1,seq=11,seq_range=-1,aru_seq=11,flags=0,source=fee139da-a4dc-11e4-896b-13e5de7439e0,source_view_id=view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5),range_uuid=00000000-0000-0000-0000-000000000000,range=[-1,-1],fifo_seq=176416,node_list=( 7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,node: {operational=1,suspected=0,leave_seq=-1,view_id=view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,5),safe_seq=4,im_range=[10,9],} fee139da-a4dc-11e4-896b-13e5de7439e0,node: {operational=1,suspected=0,leave_seq=-1,view_id=view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5),safe_seq=11,im_range=[12,11],} ) }, } } install msg=evs::msg{version=0,type=5,user_type=255,order=1,seq=4,seq_range=-1,aru_seq=4,flags=4,source=7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,source_view_id=view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,5),range_uuid=00000000-0000-0000-0000-000000000000,range=[-1,-1],fifo_seq=176866,node_list=( 7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,node: {operational=1,suspected=0,leave_seq=-1,view_id=view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,5),safe_seq=4,im_range=[10,9],} b3156374-a4dc-11e4-90ef-7745fb12a381,node: {operational=0,suspected=1,leave_seq=-1,view_id=view_id(REG,7ef72f2a-a4dc-11e4-8f5b-bb400fba8578,5),safe_seq=4,im_range=[5,4],} fee139da-a4dc-11e4-896b-13e5de7439e0,node: {operational=1,suspected=0,leave_seq=-1,view_id=view_id(REG,fee139da-a4dc-11e4-896b-13e5de7439e0,5),safe_seq=11,im_range=[12,11],} ) } } 150126 6:26:28 [ERROR] WSREP: exception from gcomm, backend must be restarted: nmi != known_.end(): node b3156374-a4dc-11e4-90ef-7745fb12a381 not found from known map (FATAL) at gcomm/src/evs_proto.cpp:shift_to():2363 150126 6:26:28 [Note] WSREP: Received self-leave message. 150126 6:26:28 [Note] WSREP: Flow-control interval: [0, 0] 150126 6:26:28 [Note] WSREP: Received SELF-LEAVE. Closing connection. 150126 6:26:28 [Note] WSREP: Shifting OPEN -> CLOSED (TO: 43) 150126 6:26:28 [Note] WSREP: RECV thread exiting 0: Success 150126 6:28:16 [Note] WSREP: New cluster view: global state: 7ef7ed24-a4dc-11e4-be97-6ee0620c8266:43, view# -1: non-Primary, number of nodes: 0, my index: -1, protocol version 3 150126 6:28:16 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification. 150126 6:28:16 [Note] WSREP: applier thread exiting (code:0) At this point, the mysqld process was still running but no further logging occurred. We know that we can repair this cluster by bootstrapping a single node, but would like to understand what may have happened to cause this crash. We've highlighted some specific log messages that seemed more significant. The logs of the node in question, b3156374-a4dc-11e4-90ef-7745fb12a381, show that the node continued to function (attempting to find cluster members) for quite some time after this crash. It was unable to connect to fee139da-a4dc-11e4-896b-13e5de7439e0and is still running, still trying to connect at the moment. Any insight into what's going on here, or has anyone seen similar behavior? Looking to see whether this is an effect of the connectivity issues we've seen, or something else entirely. We've also cross-posted this on the Galera/Codership forums. Thanks, Raina and Lyle Cloud Foundry Services Team

1 0