[MDEV-10903] Strangeness with binlog_cache_size Settings Created: 2016-09-26 Updated: 2019-04-03 Resolved: 2019-04-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | 5.5, 10.0, 10.1 |
| Fix Version/s: | 10.0.30, 10.1.22 |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Calender (Inactive) | Assignee: | Sujatha Sivakumar (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | upstream-fixed | ||
| Description |
|
I am seeing strage behavior with binlog_cache_size when trying to set it too large in the my.cnf file. The behavior is similar to the bug regarding max_binlog_stmt_cache_size reported here: https://jira.mariadb.org/browse/MDEV-4774 If you attempt to set binlog_cache_size to 18446744073709547520 via the my.cnf file, the max value per the manual, then your instance will not start, even though this can be set dynamically. Set the following:
On Windows, the instance will not start, and nothing is logged. On Linux, it also will not start, but at least you will see an error message similar to the following:
As stated, this variable can be set dynamically:
|
| Comments |
| Comment by Elena Stepanova [ 2016-09-26 ] |
|
Also reproducible with MySQL 5.5, but not 5.6/5.7. |
| Comment by Sujatha Sivakumar (Inactive) [ 2019-04-03 ] |
|
Fix for Method of verification: |