Description:
It would be great if we could have some nicer message when downgrading or upgrading to/from a version is not possible. Right now the data nodes just 'crash' with a random, scary (sic) error message.
How to repeat:
If you go from MySQL Cluster 7.0 to 6.2 (which does not work of course), you get following:
Message: Error OS signal received (Internal error, programming error or missing error message, please report a bug)
Error: 6000
Error data: Signal 6 received; Aborted
But another report from 6.3.33 to 6.2.15 for example:
Status: Ndbd file system error, restart node initial
Message: Invalid LCP (Ndbd file system inconsistency error, please report a bug)
Suggested fix:
Wouldn't it be great if a data node, connecting to the management node, checks what version the filesystem is in, what the mgm node's version is, and then decides to 'gracefully' exit saying that versions are incompatible?
The information should already be available in code I think.
