Bug #19619 | Cluster can not extend NoOfFragmentLogFiles w/o initial the file system | ||
---|---|---|---|
Submitted: | 8 May 2006 16:32 | Modified: | 13 May 2006 2:02 |
Reporter: | Jonathan Miller | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S2 (Serious) |
Version: | 5.1.11 | OS: | Linux (Linux 32 Bit OS) |
Assigned to: | Jon Stephens | CPU Architecture: | Any |
[8 May 2006 16:32]
Jonathan Miller
[9 May 2006 8:58]
Jonas Oreland
Changing the implemented behavior in this area is very time consuming. And my personal idea on how this should be accomplished is to have SQL commands (like alter logfile group add undofile, but instead for redofile), But it should documented that in order to change NoOfFragmentLogFiles one need to restart the node initial. So if one wants to do it for entire cluster, on can do a rolling node restart. Therefor moving this to docs...
[13 May 2006 0:46]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant product(s). Additional info: Updated description of parameter in Manual as suggested.
[13 May 2006 1:05]
Jonathan Miller
emphasis role="bold">Important</emphasis>: This parameter + cannot be changed <quote>on the fly</quote>; you must + restart the node using <option>--initial</option>. If you + iwsh to change this value for a running cluster, you can + do so via a rolling node restart. iwsh should be "wish" Also the commands in the ndb_mgm for restart is "<id> restart" This is where most will go to do rolling restarts. The option there is -i which should be documented. In addtion, there is another option -n that I have not idea of what it does. Moreover, we should have a table of what vaule changes need restart ( I would think all of them) and which need restarts with -i or --initial. Thanks /jeb
[13 May 2006 2:02]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant product(s). Additional info: Fixed typo. Other commentary is not relevant to *this* bug, we'll discuss via other channels, please don't reopen again. Thanks!