[MXS-813] binlogrouter, mariadb10.0, signal 11, crash Created: 2016-07-28 Updated: 2016-07-29 Resolved: 2016-07-29 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | 1.4.3 |
| Fix Version/s: | 2.0.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | sava | Assignee: | Massimiliano Pinto (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
master: maxscale: |
||
| Description |
|
My /etc/maxscale.cnf is below [maxscale] [MaxAdmin Service] [Replication] [MaxAdmin Listener] [Replication Listener] My operation is below: sudo systemctl start maxscale.service mysql -h 127.0.0.1 -u maxscale -P 5308 --protocol=tcp -p MariaDB [(none)]> CHANGE MASTER TO MASTER_HOST='xxxxxxxxxxx.ap-northeast-1.rds.amazonaws.com', MASTER_PORT=3306, MASTER_USER='repl', MASTER_PASSWORD='xxxxxxxxxxx', MASTER_LOG_FILE='mysql-bin-changelog.001521', MASTER_LOG_POS=4; My logfile is below: 2016-07-28 09:46:30 [3] info : Execute statement from the slave 'show slave status' |
| Comments |
| Comment by sava [ 2016-07-28 ] |
|
RDS MySQL 5.6.29 is also bad. |
| Comment by Massimiliano Pinto (Inactive) [ 2016-07-28 ] |
|
There is a bug in the routine that reports the hostname in SHOW SLAVE STATUS Max size is 41 bytes for all columns: this is being fixed with forthcoming maxScale release. Would you mind testing again MySQL 5.6 and MariaDB 10.0 using shorter names or IP if possible? |
| Comment by sava [ 2016-07-29 ] |
|
Hello Massimiliano Pinto, I've tested IP address instead of long FQDN like xxxxxxxxxxxxx.ap-northeast-1.rds.amazonaws.com. |
| Comment by Massimiliano Pinto (Inactive) [ 2016-07-29 ] |
|
Hi, It will be available in the next release. For now, as you successfully tested, the only way to get rid of the issue is to use a 41 bytes long hostname. Massimiliano |