[MXS-1200] config file lines limited to ~1024 chars Created: 2017-03-23  Updated: 2017-04-03  Resolved: 2017-04-03

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.0.5
Fix Version/s: 2.1.3

Type: Bug Priority: Minor
Reporter: Wade Rossmann Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2017-31

 Description   

Because $reasons I've got around 150 pairs [which is only half of the migration] of servers set up for readconnroute services which are then fed to a schemarouter that runs on top of them. I've found that once any line of configuration breaks the 1024-char barrier maxscale can no longer load.

My problem cases are in the readconnroute I attempt to configure a monitor for all 300+ servers which generates a line over 5000 chars. Though I could conceivably live without this, the more urgent concern is that the schemarouter config has now broken this barrier.

In both cases the error is:

* Error: Error: Failed to pre-parse configuration file. Error on line X.

Where line X-1 is any line longer than ~1024 chars, even a comment.

Is there any fix or workaround for this, such as a multiline syntax?



 Comments   
Comment by markus makela [ 2017-03-23 ]

You can split the server list like so:

[RW Split Router]
type=service
router=readwritesplit
servers=server1,
    server2,
    server3,
    server4
user=maxuser
passwd=maxpwd

There is a hard limit of 1024 characters in the configuration files. This could be updated to a higher value.

Comment by Wade Rossmann [ 2017-03-23 ]

Thank you for once again saving my butt.

I was going to say "the multi-line syntax should be more prominent in the docs, because I couldn't find it" but thought I should double-check one more time, and I don't know if it could possibly be any more prominently displayed, given it's section one in the first document I should have looked at: https://mariadb.com/kb/en/mariadb-enterprise/mariadb-maxscale-configuration-usage-scenarios/

Apologies for the spurious bug.

Comment by markus makela [ 2017-03-24 ]

Lowering priority as there is a workaround. The hard limit should still be documented in the limitations document.

Comment by markus makela [ 2017-04-03 ]

Increased the maximum line length to 16384 characters. The limitations document now also mentions this limit.

Generated at Thu Feb 08 04:04:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.