Hi!
On May 25, Steven Roussey wrote:
> We had some servers that were upgraded from 4.0.17/18 to 4.0.20 and had
> several problems thereafter:
>
> 1. Tables with FTS indices became corrupted, with queries on them causing
> segfaults on the servers.
Hmm, I don't see any changes in ft-related files since 4.0.18 that could
cause it (there were bugfixes, but they affect only *searching* - that
is MATCH - and not *updating*).
Can you create a test case ?
> 2. BinLog files were getting created with ownership of root, not mysql. Then
> Mysql complains that it can not read the file and so goes and creates
> another (which is fine and owned by mysql). All slaves to the master then
> die with corruption warnings about the master.
I don't really understand how it can happen - I'll let others comment on it.
> 3. All servers suddenly have a lot of connection errors:
> Aborted connection 109 to db: 'xyz' user: 'aaa' host: `something.i' (Got
> timeout reading communication packets)
I think, this is because --log-warnings was changed to be ON by default.
Disable with --skip-log-warnings
> 4. Thread stack warnings:
> Warning: Asked for 196608 thread stack, but got 126976
Same here.
Regards,
Sergei
--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
