Home

MySQL™ Cluster Manager 1.1.6 User Manual

1. 6 rows in set 0 03 sec In the case of list processes each row in the result contains the ID and type of a node in the MySQL Cluster named mycluster together with the name of the host on which the process is running For more information about this command see Section 3 8 5 The list processes Command An empty result set This can occur with one of the 1ist commands when there is nothing to report such as when 1ist sites is used before any sites have been created mcm list sites Empty set 0 72 sec Each command must be entered separately it is not possible to combine multiple commands on a single line Common options The following three options are common to most MySQL Cluster Manager client commands 1 help short form Common to all client commands Provides help output specific to the given command See Section 3 1 Online Help for MySQL Cluster Manager Commands for more information about this option 2 force short form Causes any safety checks to be bypassed when excuting the command For example delete cluster mycluster normally fails if any of the MySQL Cluster processes in the MySQL Cluster named myciuster are running however delete cluster force mycluster forces the shutdown of mycluster followed by the deletion of mycluster from MySQL Cluster Manager s inventory The force option is supported for al
2. Name Type Units Default Min Value Max Value Restart Type Id string IS Table C 6 TCP Configuration Parameters Name Type Units Default Min Value Max Value Restart Type Checksum false N Group unsigned 55 200 N Nodeld1 N Nodeld2 N NodeldServer N OverloadLimit bytes 4G N PortNumber unsigned 64K N Proxy N ReceiveBufferMemorybytes 64K 16K 4G N SendBufferMemory unsigned 256K 64K 4G N SendSignalld false debug N builds true TCP MAXSEG SIZE unsigned 2G N TCP ROV BUF SIZEunsigned 70080 1 2G N TCP SND BUF SlZEunsigned 71540 1 2G N TcpBind INADDR ANY false N Table C 7 SHM Configuration Parameters Name Type Units Default Min Value Max Value Restart Type Checksum true N Group unsigned 35 200 N Nodeld1 N Nodeld2 N NodeldServer N OverloadLimit bytes 4G N PortNumber unsigned 64K N SendSignalld false N ShmKey unsigned 4G N ShmSize bytes 1M 64K 4G N Signum unsigned 4G N Table C 8 SCI Configuration Parameters Name Type Units Default Min Value Max Value Restart Type Checksum false N Group unsigned 15 200 N 134 Name Type Units Default Min Value Max Value Restart Type Host1ScildO unsigned 4G N Host1Scild1 unsigned 4G N Host2Scild0 unsigned 4G N Host2Scild1 unsigned 4G N Nodeld1 N Nodeld2 N NodeldServer N OverloadLimit bytes 4G N PortNumber unsigned 64K N SendLimit unsigned 8K 128 32K N SendSignalld true
3. 4 3 rows in set 1 07 sec In the example just shown yourpackage uses the MySQL Cluster binaries installed at C cluster ndb host 10 on host tonfisk and at C cluster ndb host 20 on flundra mypackage uses MySQL Cluster binaries installed at C Xmy sal on both hosts The output contains three columns these are described in the following list Package The name of the package This can sometimes be empty when a package includes MySQL Cluster installations that are in different locations on different hosts see next example Path The path to the MySQL Cluster installation directory base directory on the indicated host or hosts This is the same as the value given for the basedir option in the add package command that was used to create or augment the package On Windows paths shown in this column have any backslash characters converted to forward slashes just as must be done for the basedir option see the earlier example in this section Hosts The host or hosts where the MySQL Cluster installation or installations are located You can filter the results so that information relating to only a single package is displayed by supplying the package name before the site name as shown here mcm list packages yourpackage mysite 4 dr 4 Package Pant Hosts 4 4
4. Cluster created successfully 1 row in set 7 71 sec As defined by the command just shown mycluster consists of four nodes a management node on host flundra two data nodes one on each of the hosts tonfisk and grindval and one SQL node also on host flundra Using the verbose option causes the command to print output similar to that produced by the list processes command as shown here mcm create cluster verbose package mypackage gt processhosts ndb_mgmd flundra ndbd tonfisk ndbd grindval mysqld flundra mycluster 4 4 4 NodeId Name ose 4 4 4 49 ndb mgmd flundra i ndbd tonfisk 2 ndbd grindval 50 mysqld iENwusebse 4 4 4 4 rows in set 0 32 sec You can also create this cluster in such a way that the mysqld process is permitted to connect to the cluster from any host able to reach the other cluster hosts over the network as shown here mcm create cluster package mypackage gt processhosts ndb_mgmd flundra ndbd tonfisk ndbd grindval mysqld mycluster 4 Command result 4 Cluster created successfully 4 1 row in set 7 71 sec Cluster Manager software installed on the host where the ndbapi process is
5. Name Cmd Line Option file System Var Status Var Var Scope Dynamic Ndb number of data nodes Yes Global No ndb optimization delay Yes Global Yes ndb optimized nogdYeselection Yes ndb pruned scan count Yes Global No Ndb pushed queries defined Yes Global No Ndb pushed queries dropped Yes Global No Ndb pushed queries executed Yes Global No ndb pushed reads Yes Global No ndb_report_thresh Wasog epoch Bs ndb report thresh WF80g mem U ege ndb scan count Yes Global No ndb table no logging Yes Session Yes ndb table temporary Yes Session Yes ndb transid Yes mysql connection map ndb use copying jalter table Yes Both No ndb use exact count Yes Both Yes ndb use transactioMes Yes Yes Both Yes ndb wait Yes Yes Yes Global No connected ndb wait setup Yes Yes Yes Global No ndbcluster Yes Yes Variable have ndbcluster ndbinfo database Yes Global No ndbinfo max bytesYes Yes Both Yes ndbinfo max rows Yes Yes Both Yes ndbinfo show hidd es Yes Both Yes ndbinfo table prelYes Yes Both Yes ndbinfo version Yes Global No server id bits Yes Yes Global No Variable Yes Global No server id bits skip ndbcluster Yes Yes transaction allow batching Yes Session Yes Table C 5 COMPUTER Configuration Parameters Name Type Units Default Min Value Max Value Restart Type HostName name or IP address S 133
6. Name Cmd Line Option file System Var Status Var Var Scope Dynamic Ndb conflict trans row conflict count Yes Global No Ndb conflict trans row reject count Yes Global No ndb connectstring Yes Yes ndb deferred Yes Yes Both Yes constraints Variable Yes Both Yes ndb deferred constraints ndb deferred consYamts Yes Yes Both Yes ndb distribution Yes Yes Yes Both Yes ndb distribution Yes Yes Both Yes Variable Yes Both Yes ndb distribution ndb execute count Yes Global No ndb extra logging Yes Yes Yes Global Yes ndb force send Yes Yes Yes Both Yes ndb index stat caches entries Yes ndb index stat enatse Yes ndb index stat upd te freq Yes ndb join pushdowh Yes Global No ndb log apply Yes Yes Global No status Variable Yes Global No ndb log apply status ndb log bin Yes Yes Both Yes ndb log binlog indes Yes Global Yes ndb log empty ep Gise Yes Yes Global Yes ndb log empty Yes Yes Yes Global Yes epochs ndb log orig Yes Yes Global No Variable Yes Global No ndb log orig ndb log Yes Yes Global No transaction id Variable Yes Global No ndb log transactian id ndb log transactian id Yes Global No ndb log update Yes Yes Yes Global Yes as write ndb log updated 0fis Yes Yes Global Yes ndb mgmd host Yes Yes ndb nodeid Yes Yes Yes Global No 132
7. 4 4 4 4 4 1 row in set 0 22 sec However if you try to use backslashes in the path when issuing the set command the command fails mcm set tmpdir mysqld 4 c temp 4 mycluster Outfile disabled ERROR Unknown command 4 ERROR 6014 00MGR Path name for parameter tmpdir must be absolute The value c mp4 is illegal Setting TCP Connection Attributes For a few attributes that apply only when using TCP connections such as the SendBufferMemory and ReceiveBufferMemoryattributes it is necessary to use a modified syntax for attribute value assignments In this case the attribute assignment contains two process specifications one for each process type or instance to which the setting applies joined with 85 The sec Command a plus sign For the following example consider the cluster named mycluster2 consisting of the processes shown here mcm list processes mycluster2 4 4 4 Tel Name Host 4 p 4 49 ndb mgmd grindval A ndbd tonfisk 2 ndbd flundra 50 mysqid haj Bal mysqld torsk 4 4p 5 rows in set 0 16 sec See Section 3 8 5 The list processes Command for more information about this command TCP connection attributes are not shown in the output from the get command unless they have be
8. sese 105 In this chapter we discuss limitations of and known issues in MySQL Cluster Manager version 1 1 6 4 1 MySQL Cluster Manager Usage and Design Limitations The limitations discussed in this section occur by intention or design in MySQL Cluster Manager 1 1 6 Some of these items may become obsolete in future versions we will update this section accordingly if and as those changes come about change process command Currently the change process command can be used only to exchange an ndbd process for an ndbmtd process or the reverse That is in effect it can be used only to switch a data node between a single threaded process and a multi threaded process It cannot be used for changing a cluster node s type for example you cannot change a data node to an SQL node management node or NDB API application node Because of this restriction and due to the fact that multi threaded data nodes are not supported in MySQL Cluster NDB 6 3 and earlier the change process command is useful only with clusters running MySQL Cluster NDB 7 0 or newer License keys and operating platforms License keys were required to use MySQL Cluster Manager 1 0 however no license key is necessary for MySQL Cluster Manager 1 1 0 or later including MySQL Cluster Manager 1 1 6 Concurrent client sessions unsupported Currently there is no negotation or arbitration between multiple mcm clients While it is possible to use the client from multipl
9. 4 4 2 rows in set 0 50 sec MySQL Cluster Manager you must reference these hosts using IPv4 addresses or as localhost if this is applicable Otherwise MySQL Cluster Manager will be unable to connect to the agent processes on those hosts See Section 4 1 MySQL Note R When IPv6 enabled Windows systems are used as MySQL Cluster hosts under Cluster Manager Usage and Design Limitations 3 3 2 The delete package Command delete package hosts h host list package name host MTSE lose lloses This command is used to unregister a package More specifically it removes any references to MySQL Cluster software installations added to the agent s repository when the package was created delete 60 The list packages Command package does not remove any MySQL Cluster installations the command removes only references to the installations Once a package has been unregistered it can no longer be used for a create cluster command see Section 3 4 1 The create cluster Command The MySQL Cluster binaries remain but cannot be used in a MySQL Cluster administered using the MySQL Cluster Manager unless and until the base directory containing them has been registered with another package It is possible to register a base directory with multiple packages see Section 3 3 1 The add package Command for more information and an example If the hosts opti
10. Readonly HostName tonfisk ndbd 2 Readonly 4 4 4 4 4 4 4 4 2 rows in set 0 12 sec 77 The get Command To retrieve the value of a given attribute for a particular instance of a process you can use a filter that takes the form attribute name process type process id For example you can use the following command to obtain the hostname for the process having 2 as its process ID mcm get HostName ndbd 2 mycluster 4 qp 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4 HostName tonfisk ndbd 2 Readonly q 4 4 4 4 4 4 1 row in set 1 67 sec When filtering for a given attribute on the instance level you must include the process type Failure to do so fails with an error as shown here mcm get HostName 3 mycluster ERROR 7002 00MGR Illegal process type 3 for cluster mycluster You can obtain information about multiple attributes within a single get command by specifying a list of filters separated by commas Each filter in the list must be a complete valid filter The command shown here retrieves the HostName and DataDir for all processes in mycluster
11. SendBufferMemory 8M ndbd 2 mysqld 99 SendBufferMemory 4M ndbd 2 mysqld Sal Process SendBufferMemory 4M ndbd 3 mysqld 50 Process SendBufferMemory 4M ndbd 3 mysqld SU Process 4 4 4 4 4 rows in set 0 24 sec You cannot set a connection attribute on the process level in one part of the process specification that is for one end of the connection and on the instance level in the other Attempting to do so fails with an error as shown here mcm set SendBufferMemory ndbd mysgld 4 2M mycluster2 ERROR 3 00MGR Illegal syntax mcm set SendBufferMemory ndbd 2 mysgld 2M mycluster2 ERROR 3 00MGR Illegal syntax Setup for mysqld connection pooling Enabling connection pooling for mysald can be done by by setting the ndb cluster connection pool attribute to the desired number of connections but also requires an extra step in creating the cluster Because the mysqld process attempts to make multiple connections to the cluster when connection pooling is enabled the cluster must be configured with spare or empty connections You can do this by adding otherwise unused ndbapi entries in the process host list used in the create cluster command as shown here mcm create cluster P mypackage gt R ndb_mgmd 10 100 10 97 nd
12. 4 4R 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 R 4 DataDir opt c2data ndbd 2 HostName Elundea ndbd 2 Read only NodeId 2 ndbd 2 Read only 79 The get Command 4 qp 4 4 4 4 rows in set 0 32 sec As mentioned previously you must specify the process type as well as the process ID If you specify an invalid combination of process type and process ID the get command fails with an error as shown here mcm get ndbd 4 mycluster ERROR 7004 00MGR Illegal process type ndbd for id 4 If you try to obtain values for an attribute which you know is supported by your MySQL Cluster version but the result is empty this almost certainly means that it is a default attribute which either has not been changed since the cluster was created or has been reset In order to view default attributes using get you must execute the command using the include defaults option short form a For example suppose you want to see how much Dat aMemory is configured for the n aba processes in the cluster named mycluster and you execute
13. 4 est Stare Version 4 4 4 co ns Available 1 1 6 4 qp 4 flundra Available 1 1 6 4 4 2 rows in set 0 16 sec If you omit the site name argument the command fails with an error as shown here mcm list hosts ERROR 6 00MGR Illegal number of operands 3 3 MySQL Cluster Manager Package Commands This section contains information about MySQL Cluster Manager client commands used to register extend unregister and obtain information about the software packages making up instances of MySQL Cluster that are to be managed using the MySQL Cluster Manager 3 3 1 The add package Command add package basedir b path hosts h host list package name host MMSE host PROSE reo edd I This command creates a new package or if the package named package name already exists this command extends the package definition The basedi r option short form b which indicates the location of the MySQL Cluster installation directory on the listed hosts is required This must be the path to the top level directory where the MySQL Cluster software is located for example usr 1ocal mysql and should not include the MySQL Cluster bin 1ibexec or other subdirectory within the installation directory 58 The add package Command Hosts may be specified as a comma separated list
14. sesssseeeme 103 4 1 MySQL Cluster Manager Usage and Design Limitations seeeeeeeeee 103 4 2 MySQL Cluster Manager 1 1 6 Limitations Relating to the MySQL Server 103 4 3 MySQL Cluster Manager Limitations Relating to MySQL Cluster 104 4 4 Syntax and Related Issues in MySQL Cluster Manager eee een 105 A Changes in MySQL Cluster Manager 22 000 ee eee 000 ee ee nennen nennen nnn nens nh nn 107 B Licenses for Third Party Components Used in MySQL Cluster Manager 1 1 6 109 B 1 GLib License for MySQL Cluster Manager 4 eeeeeeeeee eee eee e een nene n nn 109 B 2 GNU Lesser General Public License Version 2 1 February 1999 110 B 3 tibevent LIGONS s ae st ictu einn dateni ces HERR nh Re IN an Ri E UE KI EM KR DIES 118 B4 VibimeT LIGONS T 120 B 5 EPew Library ICONS 5 oorr treo E dekolt EUR 120 B 6 Eua liblua LICENSE icone oet ted des ne eed d bx de tune ERR 121 B 7 LuaFileSystem Library License ee ee eee ener cece eee nenene Ken KaK nnn 121 B 8 md5 Message Digest Algorithm 5 License eee eee eee nene 122 B 9 PGRE LICerse oder hber a Fa oka a Sa oo Be A ot E his ato Slon Ae 122 B 10 SHA T iIN C LICENSE cm 123 C Attribute Summary Tables ieri retten ana aa aaa aa 125 INDOX P AE AE k aaa P DE bad ana ae E A A E E 137 Preface and Legal Notices simply MySQL that incorpo
15. 4 qp 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 DataMemory 500M ndbd i Process DataMemory 500M ndbd 4 Process 4 4 4 4 4 2 rows in set 1 46 sec You can see that not only has the Value column in the get command output been updated to the new value but the Level column has also been updated from Default to Process This means that you no longer need the include defaults option to view this attribute as shown here mcm get DataMemory ndbd mycluster DataMemory 500M ndbd 80 The sec Command DataMemory 500M ndbd m2 Process qp 4 4 4 4 2 rows in set 0 63 sec However if you reset Dat aMemory also on the process level this is no longer the case Then DataMemory once again assumes its default value after which you must use the include defaults option to retrieve it as shown in this example mcm reset DataMemory ndbd mycluster Command result qp Cluster reconfigured successfully MERO sete 7 65 sec mcm get DataMemory ndbd myc
16. eee eee eee en 22 2 5 1 Starting and Stopping the Agent on Linux 2 2 eeee ee eee eee nene eee enter nn 22 2 5 2 Starting and Stopping the MySQL Cluster Manager Agent on Windows 24 2 5 3 Installing the MySQL Cluster Manager Agent as a Windows Service 26 2 6 Starting the MySQL Cluster Manager Client 2 2 tees ae ee 0000 eee eee mener 32 2 7 Setting Up MySQL Clusters with MySQL Cluster Manager eee een 35 2 7 1 Creating a MySQL Cluster with MySQL Cluster Manager eee een 35 2 7 2 Migrating a MySQL Cluster to MySQL Cluster Manager eee 37 This chapter discusses basic installation and configuration of the MySQL Cluster Manager Management Agent connecting to the agent with the MySQL Cluster Manager client and the basics of creating or importing a cluster using MySQL Cluster Manager 2 1 Obtaining MySQL Cluster Manager MySQL Cluster Manager is available only through commercial license To learn more about licensing terms and to obtain information about where and how to download MySQL Cluster Manager visit http www mysql com products cluster mcm Or contact your Oracle representative 2 2 Operating Platform and MySQL Cluster Version Compatibility MySQL Cluster Manager 1 1 6 is currently available for and supported on the following operating systems Recent versions of Red Hat Enterprise Linux Recent versions of Novell SUSE Enterprise Linu
17. 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4 at me ou 200 mysqld 50 4 4 4 4 4 1 row in set 0 50 sec Attributes which are marked Read only cannot be set Attempting to do so fails with an error as shown here mcm get ndbd mycluster 4 4 4 4 Name Value Process Idi Precess2 Ice Level Comment 4 4 4 4 4 4 4 DataDir opt c2data ndbd i HostName tonfisk ndbd Al Read only 82 The sec Command NodelId 2 ndbd A Read only DataDir oet c3aata mb 2 HostName grindval ndbd 2 Read only NodeId 13 ndbd 2 Read only qp qp q4 4 qp 4 qp qp 6 rows in set 1 42 sec mcm set HostName ndbd 1 lax mycluster ERROR 6008 00MGR Config attribute HostName is read only and cannot be changed However you can set mandatory attributes such as in the example shown previously in this section where the DataDir configura
18. Default IndexMemory 18874368 ndbd 3 Default 4 4 4 4 4 4 4 Now apply both a process level change and an instance level change to this attribute You can do this with a single set command as shown here mcm set IndexMemory ndbd 500M IndexMemory ndbd 3 750M mycluster 4 Command result 4 Cluster reconfigured successfully 1 row in set 7 29 sec Because the process level change was specified first it is overridden for the ndbd process by the instance level change specified second The output from the following get command confirms that this is the case mcm gt get IndexMemory mycluster 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 q4 4 4 4 IndexMemory 500M ndbd 2 Process IndexMemory 750M ndbd 3 4 4 4 4 4 4 4 2 rows in set 0 85 sec If the instance level IndexMemory setting for the ndbd process with process ID 3 is reset the process level setting still applies as shown here 90 The
19. 4 4 4 4 2 rows in set 0 21 sec It is also possible to obtain a list of attributes and their values for a given process type or instance of a process For a given process type use a filter having the form process name For example to retrieve all non default attributes applying to ndbd processes in a cluster named mycluster you can use the filter ndbd as shown here mcm get ndbd mycluster qp 4 4 4 4p 4 qp 4 Name Value Processl Idl Process2 Ta Level Comment 4 4 4p 4 4 4 4 qp DataDir opt c2data ndbd il HostName tonfisk ndbd 1 Read only NodeId l ndbd il Read only DataDir opt c3data ndbd 2 HostName flundra ndbd 2 Read only NodeId 2 ndbd 2 Read only qp 4 4 4 4 4 4 4 6 rows in set 0 77 sec The example just shown assumes that no attributes are set to non default values To get a list of all non default attributes for a single instance of a process use a filter having the form process_name process_id as shown in this example which retrieves all non default attributes for the ndbd process having 2 as its process ID mcm get ndbd 2 mycluster 4
20. auto BinPath C Program Files ath MySQL MySQL Cluster Manage bin mend suc exe defaults file C Program Files x86 MySQL MySQL C1 nager 1 1 4ketekmemd init 56 CreateService SUCCESS C Windows systems gt In addition you should keep in mind that the spaces after the equals signs following the DisplayName Start and BinPath arguments are required 28 Installing the MySQL Cluster Manager Agent as a Windows Service After installing the service d you can start and stop the service manually if the need arises with the NET START and NET STOP commands as shown here Microsoft Windows Version 6 1 7601 Copyright c 2009 Microsoft Corporation All rights reserved C2 Windows systemi NET START HCH The MySQL Cluster Hanager 1 1 4 Service 15 starting Ihe MySQL Cluster Hanager 1 1 4 service was started successfully C Windows system32 gt HET STOP MECH The MySQL Cluster Hanager 1 1 4 service 15 stopping The MySQL Cluster Hanager 1 1 4 service was stopped successfully C Windows system32 gt Once the service is installed the MySQL Cluster Manager agent starts automatically whenever Windows is started You can verify that the service is running with the Windows Task Manager Open the Task Manager and switch to the Services tab if it is not already P i If the MySQL Cluster acad agent is running d can find it in the list of services under MCM in the Name column and MySOL Cluste Manager
21. yourpackage usr local ndb host 10 tonfisk usr local ndb host 20 flundra 4 dr nn 2 rows in set 0 55 sec See Section 3 3 1 The add package Command for the add package commands that were used to create yourpackage When a package contains MySQL Cluster installations using different base directories on different hosts each unique combination of path and host is shown in its own row However the name of the package is displayed in the first row only all rows that immediately follow this row and that do not contain the package name also relate to the same package whose name is shown in the first preceding row to display a package name For example consider the 1ist packages command and output shown here mcm list packages mysite qp 4 Package l Fath Hoste 4 4 4 yourpackage usr local ndb host 10 tonfisk usr local ndb host 20 flundra mypackage usr local mysql tont sk fusr local bin mysql flundra qp q 2 4 3 rows in set 1 07 sec 62 MySQL Cluster Manager Cluster Commands This output shows that there are two packages defined for the site named mysite these packages are named yourpackage and mypackage The package yourpackage consists of the MySQL Cluster b
22. 2 of the hosts each house a management server and an SQL node the other 2 hosts each house 2 data nodes However regardless of the distribution of cluster nodes among the hosts a MySQL Cluster Manager agent process must be runnings on each host A MySQL Cluster Manager client can be used to access the agent from any of the hosts making up the management site to which the cluster belongs In addition the client can be used on any computer that has a network connection to at least 1 of the hosts where an agent process is running The computer where the client itself runs is not required to be one of these hosts The client can connect to and use different agent processes on different hosts within the management site at different times to perform cluster management functions Chapter 2 MySQL Cluster Manager Installation Configuration Cluster Setup Table of Contents 2 1 Obtaining MySQL Cluster Manager 220 eee eee eee menn nnne nnns nn err nnne nns hn 5 2 2 Operating Platform and MySQL Cluster Version Compatibility seen 5 2 3 MySQL Cluster Manager Agent Installation seeesesssssese eene nnn 7 2 3 1 Installing MySQL Cluster Manager on Unix Platforms sse 8 2 3 2 Installing MySQL Cluster Manager on Windows Platforms eee 9 2 4 MySQL Cluster Manager Configuration File sse memes 19 2 5 Starting and Stopping the MySQL Cluster Manager Agent
23. 3 4 4 4 4 4 4 2 rows in set 1 76 sec lf you reset the process level setting the instance level setting remains and only the ndbd process having process ID 2 has its IndexMemory reset to the default value the instance level setting remains in effect as you can see from the following seguence of commands mcm reset IndexMemory ndbd mycluster 4 Command result 4 Cluster reconfigured successfully row in set 7 36 sec mcm get d IndexMemory mycluster pas SSS SSS SSS a Se gt gt gt Name Value Processl Idl Process2 Id2 Level Comment eee jp IndexMemory 18874368 ndbd 2 Default IndexMemory 750M ndbd 3 qe 5 5 a gt 2 rows in set 0 10 sec Note R If the order of the specifiers in the original command that set IndexMemory had been reversed as IndexMemory ndbd 3 750M IndexMemory ndbd 500M the instance level change would have been overridden by the process level change and the resulting IndexMemory setting for both ndbd processes would be 500M As discussed elsewhere a process level setting made after an instance 91 The reset Command level setting that affects the same process complet
24. 95 process status 95 processes changing 99 commands 96 defined 1 listing 102 starting 98 status 95 stopping 99 R ReceiveBufferMemory 85 92 replication 105 reset command 87 and attribute name 88 and TCP connections 92 order of operands 91 process level 88 scope 88 restart cluster command 67 rolling restarts 105 S scripts MySQL Cluster Manager client 50 SendBufferMemory 85 92 set command 81 and TCP connection attributes 85 instance level 82 paths used with Windows 85 Scope 81 83 undoing effects of 89 verifying effects 82 with multiple attributes 84 with multiple processes 84 show status command 93 cluster option 93 operation option 94 process option 95 slient commands cluster 63 start cluster command 66 start process command 98 stop agents command 96 stop cluster command 67 stop process command 99 syntax issues 105 T terminology 1 U upgrade cluster command 68 upgrades MySQL Cluster 105 139 140
25. comment continues to the end of the line The version of this file that is supplied with MySQL Cluster Manager reads similarly to what is shown here mcmd plugins manager manager port 1862 MYSQOL_UUID agent uuid log file mcmd log log level message manager username manager passwo rd Username and password for manager plugin pid file INSTALLDIR PLATFORM_PATH_SEPARATOR mcmd pid Top level directory for manager plugins information stored on disk manager directory INSTALLDIR PLATFORM_PATH_SEPARATOR mcm_data The meanings of these settings along with their types and allowed values are described in the following table Setting Type Format Default Permitted Description Values plugins A comma delimited To enable MySQL To enable MySQL Cluster Manager list of plugin names Cluster Manager this list must include manager this must include manager the default value For other possibilities see MySQL Proxy however you should be aware that we currently do not test MySQL Cluster Manager with any values for plugins other than manager manager port port Default 1862 Range A legal TC IP port number This is used to specify the port used by MySQL Cluster Manager client connections Normally there is no need to change it from the default value port 1862 so there is no need to uncomment this line Note Previously this setting could optionally take a ho
26. instance level use a filter specification of the form attribute name process name process id where process idis the process ID You cannot issue a reset command that resets all values for a given configuration attribute regardless of process type each reset command must specify a process type or instance of a process Otherwise the command fails as shown here mcm reset DataMemory mycluster ERROR 3 00MGR Illegal syntax You also cannot revert all configuration attributes for a given process type or instance of a process using a single filter specification you must always include the name of the attribute to be reset Otherwise the reset command fails as shown here mcm reset ndbd mycluster ERROR 3 00MGR Illegal syntax mcm reset ndbd 3 mycluster ERROR 3 00MGR Illegal syntax Suppose that the data memory for all ndbd processes in the cluster named mycluster has been set to 500 MB as shown in the output of this get command mcm get DataMemory mycluster qp qp 4 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment qp T q4 4 4 4 DataMemory 500M ndbd 4 Process DataMemory 500M ndbd 3 Process qp 4 4 4 4 2 rows in set 1 91 sec For
27. mcm get HostName DataDir mycluster 4 qp 4 4 4 4 4 Name Value Processl NodeIdl Process2 NodeId2 Level Comment 4 qp 4 4 4 4 4 DataDir opt cldata ndbd 1 HostName flundra ndbd 1 Read only DataDir opt c2data ndbd 2 HostName bontisk ndbd 2 Read only DataDir opt c49data ndb_mgmd 49 HostName grindval ndb_mgmd 49 Read only datadir opt c50data mysqld 50 HostName haj mysqld 50 Read only datadir opt c51data mysqid il HostName torsk mysqld sl Read only 4 4 4 4 4 4 4 0 rows iw set 0 05 sec To retrieve the values of HostName and DataDir for only the data nodes in mycluster you can use the get command shown here mcm get HostName ndbd DataDir ndbd mycluster 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment DataDir opt c2data ndbd 3 Host
28. ncluded in all copies or substantial portions of the Software m HE SOFTWARE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND XPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE WARRANTIES F MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE AND ONINFRINGEMENT IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT OLDERS BE LIABLE FOR ANY CLAIM DAMAGES OR OTHER LIABILITY HETHER IN AN ACTION OF CONTRACT TORT OR OTHERWISE ARISING ROM OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE eal E me Pes O B 7 LuaFileSystem Library License The following software may be included in this product LuaFileSystem Copyright 2003 Kepler Project Permission is hereby granted free of charge to any person obtaining a copy of this software and associated documentation files the Software to deal in the Software without restriction including without limitation the rights to use copy modify merge publish distribute sublicense and or sell copies of the Software and to permit persons to whom the Software is furnished to do so subject to the following conditions The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software THE SOFTWARE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND 121 md5 Message Digest Algorithm 5 License EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY FITNESS
29. 1 6 64 Solaris 10 x86 64 bit No solaris10 x86 tarfgz mcm 1 1 6 Windows 32 bit Yes cluster 7 2 6 win32 x86 msi mcm 1 1 6 win32 Windows 32 bit No x86 msi When selecting the appropriate installer for your operating system and hardware keep in mind that 32 bit programs can normally be run on 64 bit platforms but not the reverse It might be possible that some MySQL Cluster Manager 1 1 6 builds are compatible with versions of Linux or Solaris other than those listed previously For example the s1es11 x86 64bit version is known to run on 64 bit openSUSE 11 3 and later Your Oracle representative and MySQL Support personnel can assist you in determining whether this is the case and if so which build is most suitable for your Linux or Solaris operating platform On Windows systems MySQL Cluster Manager 1 1 6 is intended for use with Windows Server 2003 or later The information provided in this section is subject to change from release to release For more specific and timely information about MySQL Cluster Manager availability and support for different operating platforms and versions as well as for different MySQL Cluster software versions see Supported Platforms MySQL Cluster Manager at http www mysql com support supportedplatforms cluster manager html or contact your Oracle representative 2 3 MySQL Cluster Manager Agent Installation Installation of the MySQL Cluster Manager agent an
30. 1 6in the Description column as shown here 29 Installing the MySQL Cluster Manager Agent as a Windows Service iL Windows Task Ma nager File Options View Help Windows CardSpace IKE and AuthIP IPsec Kevin PnP X IP Bus Enumerator IP Helper CNG Key Isolation KtmRm for Distributed Tran Server Workstation Link Layer Topology Discov TCP IP NetBIOS Helper MySOL Cluster Manager 1 1 4 Media Center Extender Ser Multimedia Class Scheduler Windows Firewall Distributed Transaction Coo Microsoft iSCSI Initiator Ser You can also verify if the service is running using the Windows Service Manager as shown here 30 Installing the MySQL Cluster Manager Agent as a Windows Service Services File Action View Heb esl o el gt au Ci Microsoft Software Shadow C Manual Local S U Enables rel Started Automatic Local S o Provides a Disabled lt Netiogon Maintains a Manual Local S 4 Network Access Protection A The Netwo Manual Networ 4 Network Connections Manages o Started Manual Local S G Network List Service Identifies t Started Manual Local S Network Location Awareness Collects an Started Automatic Networ Extended A Standard The Service Manager also allows you to start stop or pause the MySQL Cluster Manager agent service manually using a GUI Note N When first installing the MySQL Cluster Man
31. 2200000000000 dake baiana ERE nana nn 66 3 4 4 The stop cluster Command eite kud eeepc d yea a eT AE yy TT a XY REPE Au Y UTR 67 3 4 5 The restart cluster Command 2 eee eee eee eee nene 67 3 4 6 The upgrade cluster Command cerisier nerin aan 0000000000000 NEE ERATEN 68 3 4 7 The list clusters CommMan 2 2 ee 000000 ee nene nn 69 3 5 MySQL Cluster Manager Configuration Commands sss 69 3 5 1 Ine get Command erreneren REE E Faroe uri ud sateen tartan Topreeve drip e 72 3 5 2 The set Command eet tende eine ecole aN A E a dE BAR Un 81 3 5 3 The reset Command 2 e ee deno binaan Nidaa Kana a eRka 87 3 6 The show status Command ioa denti ie eee ede 93 3 7 The stop agents Command sessi nennen nnns enn nens Kn ERNES 96 3 8 MySQL Cluster Manager Process Commands sss menn 96 3 8 1 The add process Command esses eene enne nnn nnns 96 3 8 2 Tlhie start process Commiarid 2 erede sre than ecran na darn o TE Ad ma Ro ERA XN E AE r d 98 3 8 3 The stop process Command cccccccccecessseeeceeeeeeeeeeaeeeeeeaaeeeeseaeeeeeesaaeeeeesaaeeeeeee 99 3 8 4 The change process Command 0000000000000 0000 neon 99 3 8 5 The list processes Command esses eene 102 MySQL Cluster Manager 1 1 6 User Manual 4 MySQL Cluster Manager Limitations and Known ISSUES
32. DataMemory ndbd 1 2 750M mycluster ERROR 3 00MGR Illegal syntax Instead you would need to use the following command mcm set DataMemory ndbd 1 750M DataMemory ndbd 2 750M mycluster q4 Command result q4 Cluster reconfigured successfully 4 1 row in set 7 70 sec Of course if these are the only two data nodes in mycluster then the command set DataMemory ndbd 750M mycluster also accomplishes the same task require you to refer to both processes in the course of setting them In such cases you must use a special process specification syntax see Setting TCP Connection Note E A few configuration attributes apply to connections between processes and so Attributes for information about how this is done You also cannot set values for multiple attributes in a single attribute assignment this means that the following commands do not work mcm gt set UndoDataBuffer 32M UndoIndexBuffer 8M ndbd mycluster ERROR 3 00MGR Illegal syntax mcm set DataMemory IndexMemory ndbd 1G mycluster ERROR 3 00MGR Illegal syntax However if you write a complete and valid attribute assignment for each attribute whose value you wish to update you can rewrite these two commands so that they execute successfully as shown here mcm set UndoDataBuffer ndbd 32M UndoIndexBuffer ndbd 8M
33. Default Comment kk ck ck ck ck ck ck ck ck kk ck ck ck ck ck Sk kv kx ko ko ko kokokok D row ck ck ck kk kk ok kk kk kk ke kx k kx ko kk k ko ko xk Name ArbitrationTimeout Value 7500 Processi ndbmtd NodeId1 1 Process2 NodelId2 Level Default Comment kckckckck ck ck ck kck ck ck ck ck ck kk kk kk kk kk k 1094 row ok ckckckckck ck ck ck ck ck ck ck kc k kk kk kk kkkkkk k Name DefaultOperationRedoProblemAction Value queue Processi ndbapi NodeId1 52 Process2 NodelId2 Level Default Comment ck ck ck ck ck ck ck ck ck kk kk kk kk ok ockckckckckckckck ck 1095 row ok ckckckckckckckck ck ock ck ko ck k ko k kk kk kkkkkk k Name ExecuteOnComputer Value NULL Processi ndbapi NodeId1 52 Process2 NodelId2 Level Default Comment KREKKKKKKKKKKKKKKKKKKKKKKKEEEK 1096 row kckckckckckck ck ck ck ck ck ck kk kk kk kk kkkkk k Name HeartbeatThreadPriority Value NULL Processi ndbapi NodeId1 52 Process2 NodelId2 Level Default Comment ck ck ck ck ck ck ck kk kk KKK KKK KKKKKKKKKK TOGT row ok ckckckckck ck ck ck ck ck ck ck kc k kk kk kk kkkkk Name HostName Value Processi ndbapi NodeId1 52 Process2 NodelId2 Level Default Comment ck ckckckck ck ck ko ako ko ko ku ck kk kk k kk kkkk k 1098 row ok ckckckckckck ck ck ck ck ck ko ck ck kk kk kk kkkkk k Name MaxScanBatchSize Value 262144 Processi ndbapi NodeId1 52 Process2 NodelId2 Level Default Comment ck ck ck ck ck ck ck kk kk kk kk kk
34. MySQL 33 Starting the MySQL Cluster Manager Client 5 1 or later should work without any issues for connecting to mcma In addition since the client server protocol used by MySQL Cluster Manager is platform independent you can use a mysal client on any platform supported by MySQL This means for example that you can use a mysal client on Microsoft Windows to connect to a MySQL Cluster Manager agent that is running on a Linux host Connecting to the MySQL Cluster Manager agent using the mysal client is accomplished by invoking mysql and specifying a hostname port number username and password using the following command line options e host hostname or h hostname This option takes the name or IP address of the host to connect to The default is Localhost Like the mcm client the mysq1 client does not perform host name resolution and relies on the host operating system for this task For this reason it is usually best to use a numeric IP address rather than a hostname for this option e port portnumber Or P portnumber This option specifies the TCP IP port for the client to use This must be the same port that is used by the MySQL Cluster Manager agent Although the default number of the port used by the MySQL Cluster Manager agent is 1862 which is also used by default by mcr this default value is not known to the mysql client which uses port 3306 the default port for the MySQL server if this option is not spec
35. MySQL Cluster Manager installation directory as its configuration file this can be overridden by passing the desired file s location as the value of the defaults file option The complete syntax for mcmd is shown here memd exe defaults file bootstrap log file log level By default the agent assumes that the agent configuration file is ecc mcmd ini in the MySQL Cluster Manager installation directory You can tell the agent to use a different configuration file by passing the path to this file to the defaults file option as shown here C Program Files x86 MMySQLMMySQL Cluster Manager 1 1 4 bin gt mcmd defaults file C MProgram Files x86 MySQLMMySQL Cluster Manager 1 1 4 etc mcemd ini The bootstrap option causes the agent to start with default configuration values create a default one machine cluster named mycluster and start it The use of this option with mcmd is shown here on a system having the host name torsk where MySQL Cluster Manager has been installed to the default location C Program Files x86 XMySOL MySOL Cluster Manager 1 1 4Xbin gt mcmd bootstrap MySQL Cluster Manager 1 1 4 started Connect to MySQL Cluster Manager by running C Program Files x86 MySQLMMySQL Cluster Manager 1 1 4 bin mcm a TORSK 1862 Configuring default cluster mycluster Starting default cluster mycluster Cluster mycluster started successfully ndb mgmd TORSK 1186 ndbd TORSK ndbd TOR
36. Note R In the case of a free ndbapi process it is not necessary to have the MySQL running Configuration changes to the newly created cluster can be made using the set command prior to starting the cluster This is often preferable to doing after the cluster has been started since set commands used to make configuration changes in a running cluster can require a rolling restart and rolling restarts of clusters having many nodes or large quantities of data or both may take a great deal of time to complete For more information see Section 3 5 2 The set Command machine MySQL Cluster Manager assigns the MySQL default port 3306 to each of them Therefore you must assign a unique port for each mysqid process in the Note R When creating a cluster having more than one mysqld process on the same host cluster 3 4 2 The delete cluster Command 65 The start cluster Command delete cluster cluster name This command deletes the cluster named c1uster name that is it removes the MySQL Cluster Manager files relating to this cluster delete cluster does notremove any MySQL Cluster binaries from hosts This example demonstrates how to delete a cluster named mycluster mcm delete cluster mycluster q4 Command result 4 Cluster deleted successfully q4 1 row in set 1 22 sec This command fails if the cluster
37. a 50 mysqld haj stopped Sa mysqld torsk stopped 58 ndbapi stopped 4p 4p 4p 4p 6 rows in set 0 05 sec The following command changes only the node having the process ID 2 from using the multi threaded data node daemon to the single threaded version mcm gt change process ndbmtd 2 ndbd mycluster Command result Process changed successfully 1 row in set 6 52 sec As you can see change process operates much more quickly when the process to be changed is not running As before you can verify that the command succeeded using show status mcm show status process mycluster 4 4 4 4 4 NodeId Process Host Status Nodegroup 4 4 4 4 qp 49 ndb mgmd flundra stopped il ndbmtd tonfisk stopped n a 2 ndbd grindval stopped n a 50 mysqld haj stopped gi mysqld torsk stopped 52 ndbapi aS stopped 4 4 6 rows in set 0 07 sec To complete the example we start the cluster again using start cluster then change node number 2 back from ndbd single threaded to ndbmt d mult
38. and conditions of your Oracle Software License and Service Agreement which has been executed and with which you agree to comply This document and information contained herein may not be disclosed copied reproduced or distributed to anyone outside Oracle without prior written consent of Oracle or as specifically provided below This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates This documentation is NOT distributed under a GPL license Use of this documentation is subject to the following terms You may create a printed copy of this documentation solely for your own personal use Conversion to other formats is allowed as long as the actual content is not altered or edited in any way You shall not publish or distribute this documentation in any form or on any media except if you distribute the documentation in a manner similar to how Oracle disseminates it that is electronically for download on a Web site with the software or on a CD ROM or similar medium provided however that the documentation is disseminated together with the software on the same medium Any other use such as any dissemination of printed copies or use of this documentation in whole or in part in another publication requires the prior written consent from an authorized representative of Oracle Oracle and or its affiliates reserve any and all rights to this documentat
39. and their meanings are listed later in this section Description In some cases depending on the command and its status this column may contain additional information Otherwise no message is displayed here Possible values for the Status column together with descriptions of these values are shown in the following table Status Value Description executing MySQL Cluster Manager is executing the command but has not yet completed doing so finished The command has executed and completed successfully failed The command failed to execute The Description column may contain information about the reason for the failure unknown MySQL Cluster Manager was unable to determine the status of this command 94 The show status Command process option When run with this option show status returns information about each process in the cluster named cluster name as shown in this example mcm show status process mycluster 4 4 4 qp TA Process Host Status Nodegroup 4 4 4 4 qp i ndb_mgmd tonfisk running 2 ndbd flundra running 0 3 ndbd rebo sewuesspberey 0 4 mysqid Tax running 4 4 4 4 4 4 rows in set 1 67 sec When the process option short f
40. are shown in a contrasting style 40 Migrating a MySQL Cluster to MySQL Cluster Manager mcm create cluster P mypackage R ndbapi 196 168 0 2 ndb_mgmd 192 168 10 2 ndbapi 196 168 0 4 ndb_mgmd 192 168 10 4 gt ndbd 192 168 10 10 ndbd 192 168 10 10 ndbd 192 168 10 11 ndbd 192 168 10 11 gt ndbapi 196 168 0 11 mysqld 192 168 10 20 gt ndbapi 196 168 0 20 mysqld 192 168 10 21 mycluster Since MySQL Cluster Manager does not expect to execute ndbapi processes itself the host names used with these dummy items are arbitrary the only requirement for these is that they are names of hosts belonging to the cluster 41 42 Chapter 3 MySQL Cluster Manager Client Commands Table of Contents 3 1 Online Help for MySQL Cluster Manager Commands sss 48 3 2 MySQL Cluster Manager Site Commands ssssssssssessseeeeeene n nennen nen ener 55 3 2 1 The eseaste Site Command pene ide pepe Idee eode ad add de EDI NES OP SeavP ED NOE 55 3 2 2 The delete site Command ecrire e rideo ka esa duro ne Y Rea a FERES Sue FEVER qua 56 3 2 3 The dust Sites GCommnd nece ee eoa ee eras EE EEE VERA Adast a ew Va debe v gua 57 3 2 4 The add hosts Command seessssessssseseee eene nennen nnns nennt EEKE inse nh nnns 57 3 2 5 The list hosts Gommarnd ice c easet osad seu eonun waa IERI da ao K6 dud k ARMAR Ad VERE TR R 58 3 3 MySQL Cluster Ma
41. attribute is NodeTd If you try to reset a mandatory attribute the attempt fails with an error as shown here mcm reset NodeId ndb mgmd 1 mycluster ERROR 6007 00MGR Config attribute NodeId is mandatory and cannot be reset mcm reset NodeId ndbd 2 mycluster ERROR 6007 00MGR Config attribute NodeId is mandatory and cannot be reset mcm reset NodeId mysqld 4 mycluster ERROR 6007 00MGR Config attribute NodeId is mandatory and cannot be reset A Read only attributes Important created A read only attribute can be neither changed nor reset by the user This means that a read only attribute is always a mandatory attribute One such attribute is Host Name which is read only for any type of MySQL Cluster process Any attempt to change or reset a read only attribute fails as shown here mcm reset HostName ndb mgmd mycluster ERROR 6008 00MGR Config attribute HostName is readonly and cannot be changed mcm reset HostName ndbd mycluster ERROR 6008 00MGR Config attribute HostName is readonly and cannot be changed mcm reset HostName mysqld mycluster 71 The get Command ERROR 6008 00MGR Config attribute HostName is readonly and cannot be changed mcm set HostName ndb mgmd mycluster ERROR 6008 00MGR Config attribute HostName is readonly and cannot be changed mcm set HostName ndbd mycluster ERROR 6008 00MGR Config attribute HostName is readonly and cannot be changed mcm set HostName
42. can use 1og 1evel option to override the 1og level set in the agent configuration file See Section 2 4 MySQL Cluster Manager Configuration File for information about possible values and their effects on logging The MySQL Cluster Manager agent must be started on each host in the MySQL Cluster to be managed To stop one or more instances of the MySQL Cluster Manager agent use the stop agents command in the MySQL Cluster Manager client see Section 3 7 The stop agents Command for more information and examples If the client is unavailable you can stop each agent process using the system s standard method for doing so such as C or kill In addition the agent does not automatically run as a daemon or service on Linux and other Unix like systems if an agent process fails you must either have your own mechanism in place for detecting the failure and restarting the agent process or restart it manually This is not true for MySQL Cluster Manager on Windows see Section 2 5 3 Installing the MySQL Cluster Manager Agent as a Windows Service for more information 23 Starting and Stopping the MySQL Cluster Manager Agent on Windows 2 5 2 Starting and Stopping the MySQL Cluster Manager Agent on Windows To start the MySQL Cluster Manager agent manually on a Windows host you should invoke mcmd exe found in the bin directory under the manager installation directory on that host By default the agent uses etc mcmd ini in the
43. causes the command to fail with an error as shown here mcm change process ndb mgmd mysgld mycluster ERROR 7009 00MGR Processes ndb mgmd and mysqld are not interchangable in this package mcm change process ndbd mysgld mycluster ERROR 7009 00MGR Processes ndbd and mysqld are not interchangable in this package 3 8 5 The 1ist processes Command list processes cluster name This command displays all processes making up a given cluster The following example demonstrates how to list all processes that are part of the cluster named mycluster mcm list processes mycluster 4 4 4 NodeId Name Host 4 4 4 49 ndb mgmd flundra JL ndbd tonfisk 2 ndbd grindval 50 mysqld haj 51 mysqld torsk 52 ndbapi 4 4 4 6 rows in set 0 03 sec The cluster name argument is required If this argument is omitted the command fails with an error as shown here mcm list processes ERROR 6 00MGR Illegal number of operands 102 Chapter 4 MySQL Cluster Manager Limitations and Known Issues Table of Contents 4 1 MySQL Cluster Manager Usage and Design Limitations ssseseseeeeenn 103 4 2 MySQL Cluster Manager 1 1 6 Limitations Relating to the MySQL Server ee 103 4 3 MySQL Cluster Manager Limitations Relating to MySQL Cluster eee 104 4 4 Syntax and Related Issues in MySQL Cluster Manager
44. documentation for PCRE supplied in the doc directory is distributed under the same terms as the software itself The basic library functions are written in C and are freestanding Also included in the distribution is a set of C wrapper functions THE BASIC LIBRARY FUNCTIONS Written by Philip Hazel Email local part ph10 Email domain cam ac uk University of Cambridge Computing Service Cambridge England Phone 44 1223 334714 Copyright c 1997 2006 University of Cambridge All rights reserved THE C WRAPPER FUNCTIONS Contributed by Google Inc 122 SHA 1 in C License Copyright c 2006 Google Inc All rights reserved THE BSD LICENCE Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are met Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution Neither the name of the University of Cambridge nor the name of Google Inc nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTO
45. get wait_timeout mysqld mycluster Empty set 1 42 sec This is because the default behavior of the get command is to display only those values that have been set either by the MySQL Cluster Manager or by the user Since wait_timeout has been allowed to revert to its default value you must use the include defaults short form d option to retrieve it as shown here mcm get d wait timeout mysqld mycluster qp 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 wait_timeout 28800 mysqld 4 Default 4 4 4 4 4 1 row in set 1 66 sec Now consider a situation in which process level and instance level settings have been made to a configuration attribute in this example we use IndexMemory First verify that IndexMemory is set to its default value for all data node processes in this case there are two of them mcm get d IndexMemory mycluster qp qp qp 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4 IndexMemory 18874368 ndbd 4
46. limitation the rights to se copy modify merge publish distribute sublicense and or sell copies of he Software and to permit persons to whom the Software is furnished to do so ubject to the following conditions a The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software THE SOFTWARE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM DAMAGES OR OTHER LIABILITY WHETHER IN AN ACTION OF CONTRACT TORT OR OTHERWISE ARISING FROM OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE B 6 Lua liblua License The following software may be included in this product Lua liblua Copyright 1994 2008 Lua org PUC RiO Permission is hereby granted free of charge to any person obtaining a copy of this software and associated documentation files the Software to deal in the Software without restriction including without limitation the rights to use copy modify merge publish distribute sublicense and or sell copies of the Software and to permit persons to whom the Software is furnished to do so subject to the following conditions H he above copyright notice and this permission notice shall be
47. list the contents you should see something similar to what is shown here shell cd mcm shell 1s bin cluster etc lib libexec licenses share var These directories are described in the following table Directory Contents bin MySQL Cluster Manager agent startup scripts cluster Contains the MySQL Cluster NDB 7 2 4 binary distribution 64 bit Installing MySQL Cluster Manager on Windows Platforms Directory Contents etc Contains the agent configuration file mcmd ini etc init d Init scripts not currently used Libraries needed to run the MySQL Cluster Manager agent 1ib and subdirectories libexec MySQL Cluster Manager agent and client executables licenses lgpl An archive containing source code including licensing and documentation for glib 2 1 share doc mcmd README txt file var XML files containing information needed by MySQL Cluster Manager about processes attributes and command syntax Normally the only directories of those shown in the preceding table that you need be concerned with are the bin and ecc directories For MySQL Cluster Manager 1 1 6 distributions that include MySQL Cluster the complete MySQL Cluster NDB 7 2 4 binary distribution is included in the cluster directory Within this directory the layout of the MySQL Cluster distribution is the same as that of the standalone MySQL Cluster binary distribution For example MySQL Cluster
48. mcm gt start cluster yourcluster ERROR 5001 00MGR Cluster yourcluster not defined In addition the cluster must not already be running as shown here mcm show status cluster mycluster dp ab Cluster Status dpe dome 66 The stop cluster Command mycluster fully operational qp 1 row in set 0 92 sec mcm gt start cluster mycluster ERROR 5005 00MGR Cluster mycluster is running 3 4 4 The stop cluster Command stop cluster cluster name This command stops the cluster named cluster name ifitis running as shown in this example mcm stop cluster mycluster 4 Command result Cluster stopped successfully 1 row in set 21 31 sec stop cluster fails if the cluster is not in an operational state see Section 3 6 The show status Command for information about obtaining the cluster s status mcm show status cluster mycluster 4 4 Cluster 1 row in set 1 49 sec mcm gt stop cluster mycluster ERROR 5006 00MGR Cluster mycluster is stopped 3 4 5 The restart cluster Command restart cluster cluster name This command performs a rolling restart see Performing a Rolling Restart of a MySQL Cluster of the cluster named cluster name The cluster must already be running in order fo
49. mycluster 4 Command result 4 Cluster reconfigured successfully row in set 6 62 sec mcm set DataMemory ndbd 1G IndexMemory ndbd 1G mycluster 4 Command result 4 Cluster reconfigured successfully row in set 7 04 sec 84 The sec Command In fact there is no reason that you cannot perform all four assignments in a single sec command using a list of four attribute assignments like this mcm set UndoDataBuffer ndbd 32M UndoIndexBuffer ndbd 8M DataMemory ndbd 1G IndexMemory ndbd 1G mycluster 4 Command result q4 Cluster reconfigured successfully MMMM 1 row in set 6 24 sec However it a good idea not to perform too many attribute assignments in any single set command since this makes it more difficult to spot errors On Windows when setting attributes whose values contain paths such as DataDir you must replace any backslash characters in the path with forward slashes Suppose that you want to use C temp node50 afor the tmpdi r attribute of the mysqid process having node ID 50 in a MySQL Cluster named mycluster w
50. of site site Note kK When IPv6 enabled Windows systems are used as MySQL Cluster hosts under MySQL Cluster Manager you must reference these hosts using IPv4 addresses or as localhost if this is applicable Otherwise MySQL Cluster Manager will be unable to connect to the agent processes on those hosts See Section 4 1 MySQL Cluster Manager Usage and Design Limitations 3 2 2 The delete site Command delete site site name The delete site command deletes an existing management site The command does not stop or remove any agents making up the deleted site instead these agents continue to run and remain available for use in other sites The command takes a single argument the name of the site to be deleted This example shows the deletion of a management site named mysite mcm delete site mysite q4 Command result 4 Site deleted successfully row in set 0 38 sec lf the site to be deleted does not exist the command fails with the error Command reguires a site to be defined If there are any packages referencing hosts belonging to the site delete site fails with the error Packages exist in site site name The command also fails if there are defined any clusters that include hosts belonging to the site 56 The list sites Command Note R The management client must be connected to a site in order to be able to
51. package command would look like this with the basedir option highlighted mcm add package basedir c mysql mypackage q4 Command result q4 Package added successfully q4 1 row in set 0 71 sec In the example just given we could also have issued the command as add package basedir usr local mysgl hosts tonfisk flundra mypackage Or add package basedir c mysql hosts tonfisk flundra mypackage on Windows with the same result but the hosts option was not required since the MySQL Cluster software s location is the same on each host Let us suppose however that the software is installed in usr local ndb host 10 on host tonfisk and in usr local ndb host 20 on host 1undra In this case we must issue 2 separate commands specifying the host as well as the base directory in each case as shown here mcm add package basedir usr local ndb host 10 e hosts tonfisk yourpackage 1 row in set 0 68 sec mcm add package basedir usr local ndb host 20 hosts flundra yourpackage Command result Package added successfully 59 The delete package Command 1 row in set 0 81 sec Assuming that both hosts belong to a site called mysite you can verify that these packages have been created as desired using the list packages com
52. performed MySQL Cluster Manager can perform this operation automatically so that the configuration change takes effect without further intervention required on the part of the operator Configuration attribute levels A configuration attribute value applies at one of the three levels described here Default This value is always used by any MySQL Cluster process of the type or types such as ndbd or mysqld to which the attribute applies unless this value is overridden by the user Process This value is used for all instances of a given type of MySQL Cluster process Instance This value is used for a specific instance of a MySQL Cluster process the instance being identified by its MySQL Cluster node ID Default values are hard coded into MySQL Cluster you can override a default value for a given configuration attribute using the sec command or reset a given attribute value to its default using the reset command but you cannot change a default value itself You can set or reset an configuration attribute s value on either the process level or the instance level using a single set or xeset command Once you have set or reset the value of a configuration attribute this value persists until it is changed by executing another set or reset command Note R When setting or resetting a configuration attribute value you must specify the level at which the setting applies MySQL Cluster Manager determines what value to use for a con
53. platforms where mcm itself or even mcmd is not available For more information see Connecting to the agent using the mysal client If you experience problems starting an MySQL Cluster Manager client session because the client fails to connect see Can t connect to local MySQL server for some reasons why this might occur as well as suggestions for some possible solutions To end a client session use the exit or quit command short form Na Neither of these commands requires a separator or terminator character For more information see Chapter 3 MySQL Cluster Manager Client Commands Connecting to the agent with the mcm client You can connect to the MySQL Cluster Manager agent by invoking mcm or on Windows mcm exe You may also need to specify a hostname port number or both using the following command line options e host hostname or h hostname This option takes the name or IP address of the host to connect to The default is localhost which may not be recongized on all platforms when starting a mcm client session even if it works for starting mysql client sessions You should keep in mind that the mcm client does not perform host name resolution any name resolution information comes from the operating system on the host where the client is run For this reason it is usually best to use a numeric IP address rather than a hostname for this option e port portnumber or P portnumber This option specifi
54. reset restart cluster set show status start cluster start process stop agents stop cluster stop process upgrade cluster version clusters commands hosts nextnodeids packages processes sites Add hosts to site Add a package alias Add cluster process Change process type Create cluster Create site Delete cluster Delete package Delete a site Get configuration variables List all clusters List the help text List hosts in site List next nodeids to be allocated List all packages List processes List all sites Reset configuration variables Restart a cluster Set configuration variables Show cluster process or operation status SyEEWeE amp y bun s Start a cluster process Stop agents in site Stop a cluster Stop a cluster process Upgrade a cluster Print version information a a a a GLOBAL OPTIONS Options that can be used with all commands help Print detailed help Use lt COMMAND gt help to see verbose help for individual commands 37 rows in set 0 00 sec Obtaining information about specific MySQL Cluster Manager client commands To obtain more detailed help specific to a given command invoke the command using the hne1p option as shown in this example mcm create site help create site options sitename Creates a site from the hosts listed in hosts Required options OS l Comma separated list of hostnames HOEMAE h
55. running cluster In other words an api section is created in the cluster config ini file but no HostName parameter is specified thus the mysqld or ndbapi can connect from any host Currently there is no way using MySQL Cluster Manager to specify that a mysgld or ndbapi process is restricted to connecting from a single host Aname for the cluster Once the cluster has been created this name is used to refer to it in other cluster management commands such as delete cluster start cluster stop cluster and so forth For information about these commands see the other subsections of Section 3 4 MySQL Cluster Manager Cluster Commands Like other object names used with MySQL Cluster Manager the cluster name must be valid according to the rules given elsewhere in this document for identifiers see Chapter 3 MySQL Cluster Manager Client Commands MySQL Cluster Manager 1 1 4 and later supports an additional verbose option for this command that Causes create cluster to output extra information as it is executed as shown later in this section For example consider the following command issued in the MySQL Cluster Manager client which creates a cluster named mycluster mcm create cluster package mypackage 64 The delete cluster Command gt processhosts ndb_mgmd flundra ndbd tonfisk ndbd grindval mysqld flundra mycluster 4 Command result 4
56. session Yes Session No Ndb api uk op count slave Yes Global No Ndb api wait exec complete count Yes Global No Ndb api wait exec complete cqunt session Yes Session No Ndb api wait exec complete cdunt slave Yes Global No Ndb api wait meta request count Yes Global No Ndb api wait meta request count session Yes Session No Ndb api wait meta request count slave Yes Global No Ndb api wait nanos count Yes Global No Ndb api wait nanos count session Yes Session No Ndb api wait nanos count slave Yes Global No Ndb api wait scam result count Yes Global No Ndb api wait scam result count session Yes Session No Ndb api wait scam result count slave Yes Global No ndb autoincremeniYeefetch sz Yes Yes Both Yes ndb batch size Yes Yes Yes Global No ndb blob read Yes Yes Yes Both Yes batch bytes ndb blob write Yes Yes Yes Both Yes batch bytes ndb cache check Nee Yes Yes Global Yes ndb cluster Yes Yes Yes Yes Global No connection pool Ndb cluster node id Yes Both No Ndb config from host Yes Both No Ndb config from port Yes Both No Ndb conflict fn epoch Yes Global No Ndb conflict fn epoch trans Yes Global No Ndb conflict fn max Yes Global No Ndb conflict fn old Yes Global No Ndb conflict trans conflict commit count Yes Global No Ndb conflict trans detect iter count Yes Global No Ndb conflict trans reject count Yes Global No 131
57. the following show status command mcm show status process mycluster 99 The change process Command 4 4 4 4 4 NodeId Process Host Status Nodegroup 4 4 4 4 4 49 ndb mgmd flundra running 1 ndbd tonfisk running n a 2 ndbd grindval running n a 50 mysqid haj running DA mysqld torsk running 52 ndbapi X running 4 4 4 4 4 6 rows in set 0 06 sec To change both data nodes to so that they use multi threaded ndbmt a processes issue the command shown here without any process id specifier mcm gt change process ndbd ndbmtd mycluster Command result 4 Process changed successfully 4 low S C Z Sec After the command has executed you can verify that both data nodes are now using ndbmt d by checking the output of the appropriate show status command as shown here mcm show status process mycluster 4 4 4 4 4 NodeId Process Host Status Nodegroup 4 4 4 4 4 49 ndb mgmd flundra running Jl ndbmtd tonfisk running n a 2 ndbmtd grindval running n a 50 mysqid haj running 51 mysqld torsk running 52 ndbapi g running 4
58. the software and use pieces of it in new free programs and that you are informed that you can do these things 110 GNU Lesser General Public License Version 2 1 February 1999 To protect your rights we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it For example if you distribute copies of the library whether gratis or for a fee you must give the recipients all the rights that we gave you You must make sure that they too receive or can get the source code If you link other code with the library you must provide complete object files to the recipients so that they can relink them with the library after making changes to the library and recompiling it And you must show them these terms so they know their rights We protect your rights with a two step method 1 we copyright the library and 2 we offer you this license which gives you legal permission to copy distribute and or modify the library To protect each distributor we want to make it very clear that there is no warranty for the free library Also if the library is modified by someone else and passed on the recipients should know that what they have is not the original version so that the original author s reputation will not be affected by problems that might be i
59. the terms of his License whose permissions for other licensees extend to the ntire whole and thus to each and every part regardless of who wrote EE oo fon W Gr 9 feb TS ct BUS scc Site ni o ee S SOHO CORSO AM gb SM OUO esSts your rights to work written entirely by you rather the intent is to exercise the right to control the distribution of derivative or collective works based on the Library In addition mere aggregation of another work not based on the Library with the Library or with a work based on the Library on a volume of a storage or distribution medium does not bring the other work under the scope of this License 3 You may opt to apply the terms of the ordinary GNU General Public icense instead of this License to a given copy of the Library To do his you must alter all the notices that refer to this License so hat they refer to the ordinary GNU General Public License version 2 nstead of to this License If a newer version than version 2 of the rdinary GNU General Public License has appeared then you can specify hat version instead if you wish Do not make any other change in hese notices ae ar e Gr Gr E Once this change is made in a given copy it is irreversible for hat copy so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy ct This option is useful when you wish to copy part of the code of the Library into a program
60. to grant MySQL Cluster Manager or MySQL Cluster access to public networks such as the Internet Note E The defaults file and bootstrap options are mutually exclusive The 1og file option allows you to override the default location for the agent log file normally mcmd 10g in the MySQL Cluster Manager installation directory You can use 1og 1evel option to override the 1og level set in the agent configuration file See Section 2 4 MySQL Cluster Manager Configuration File for information about possible values and their effects on logging The MySQL Cluster Manager agent must be started on each host in the MySQL Cluster to be managed 25 Installing the MySQL Cluster Manager Agent as a Windows Service It is possible to install MySQL Cluster Manager as a Windows service so that it is started automatically each time Windows starts See Section 2 5 3 Installing the MySQL Cluster Manager Agent as a Windows Service To stop one or more instances of the MySQL Cluster Manager agent use the stop agents command in the MySQL Cluster Manager client see Section 3 7 The stop agents Command for more information and examples You can also stop an agent process using the Windows Task Manager In addition if you have installed MySQL Cluster Manager as a Windows service you can stop and start the agent using the Windows Service Manager CTRL C or the appropriate NET STOP of NET START command as discussed in the next se
61. upgrade or downgrade in question and for any known issues regarding the changes you intend to make 3 4 7 The 1ist clusters Command list clusters site name This command lists all clusters defined for a given management site named site name together with the package used by each cluster For example the command shown here displays a list of all clusters defined for the site named mysite mcmc list clusters mysite 4 4 Cluster Package mycluster m 7eOoti yourcluster 57 0 someothercluster s 7 0 13 3 rows in set 2 07 sec If site name is omitted the command fails with an error as shown here mcm list packages ERROR 6 00MGR Illegal number of operands 3 5 MySQL Cluster Manager Configuration Commands This section covers the commands used in the MySQL Cluster Manager for getting and setting values of various types used in MySQL Cluster configuration We begin with a discussion of what we mean by the term configuration attribute and how this relates to the manual configuration of a MySQL Cluster using MySQL Cluster configuration parameters and MySQL Server options and variables that you may already be familiar with Configuration attributes Traditionally when administering MySQL Cluster it has been necessary to distinguish between 3 types of config
62. using the host s option short form h however this option is not required If host s is omitted the path is assumed to be valid for all hosts in the cluster that is created using this package see Section 3 4 1 The create cluster Command Important AN You cannot perform add package if you have not yet defined any sites each host referenced in an add package command must be associated with a site See Section 3 2 1 The create site Command for more information about defining sites For example suppose we have two Linux hosts named tonfisk and flundra and the MySQL Cluster software is installed in usr local mysal on both hosts In this case you can create a package named mypackage that accounts for both hosts as shown here mcm add package basedir usr local mysql mypackage 4 Command result Package added successfully 4 1 row in set 0 71 sec When this package is used to create a cluster the MySQL Cluster Manager knows that it should find the MySQL Cluster software in the usr local mysal directory on each of the hosts For options to MySQL Cluster Manager client command options having Windows paths as values you must use forward slashes in place of backslashes so if tonfisk and flundra are Windows hosts where MySQL Cluster has been installed to the directory C mysql1 the corresponding add
63. we recommend that you have all required software including the MySQL Cluster software in place Note R You can actually perform this step at any time up to the point where the software before executing any MySQL Cluster Manager client commands Management site definition Using the create site command in the MySQL Cluster Manager client define a MySQL Cluster Manager management site that is the set of hosts to be managed This command provides a name for the site and must reference all hosts in the cluster Section 3 2 1 The create site Command provides syntax and other information about this command To verify that the site was created correctly use the MySQL Cluster Manager client commands list sites and list hosts see Section 3 2 3 The list sites Command and Section 3 2 5 The list hosts Command for more information MySQL Cluster software package registration In this step you provide the location of the MySQL Cluster software on all hosts in the cluster using one or more add package commands See Section 3 3 1 The add package Command for more information about this command To verify that the package was created correctly use the list packages and list processes commands see Section 3 3 3 The 1ist packages Command and Section 3 8 5 The 1ist processes Command Cluster definition Execute a create cluster command to define the set of MySQL Cluster nodes processes and hosts on which each clus
64. what appears to be the correct get command but an empty result is returned as shown shown here mcm get DataMemory ndbd mycluster Empty set 1 19 sec This means that the Dat aMemory attribute has its default value for all data nodes in the cluster If you do not recall what this value is you can determine it easily by repeating the same command with the addition of the include defaults d option mcm get include defaults DataMemory ndbd mycluster qp qp q4 4 4 4 qp 4p t Name Value Processl Idl Process2 Id2 Level Comment qp qp 4 4 4 4 4 DataMemory 83886080 ndbd ah Default DataMemory 83886080 ndbd 2 Default qp q4 4 4 4 4 2 rows in set 0 62 sec Now suppose that you increase the Dat aMemory to 500 megabytes per data node then repeat the get command to verify the new value mcm gt set DataMemory ndbd 500M mycluster 4 Command result 4 Cluster reconfigured successfully row in set 7 77 sec mcm get include defaults DataMemory ndbd mycluster qp qp qp 4 qp
65. wrapper Connection id Current database n a Current user admin SSL Not in use Current pager less Using outfile Using delimiter A Server version 1 4 MySQL Cluster Manager Protocol version 0 Connection BA OO wia MER Server characterset lt n a gt Db characterset lt n a gt Client characterset lt n a gt Conn characterset n a VCP pore 1862 Note R You may use the command delimiter with mysq1 client commands but you are not required to do so For instance assuming that the delimiter in use was the default semicolon character we could have executed the status command like this mcm status home jon bin mcm bin mysgl Ver 14 14 Distrib 5 5 19 ndb 7 2 4 A particularly useful mysq1 client command that you can also employ with mcm is the source command short form which you can use for executing scripts containing MySQL Cluster Manager client commands On a Linux system you might have a text file in your home directory named get attributes mcm Whose contents are shown here get ndb mgmd mycluster G get ndbd mycluster G 50 Online Help for MySQL Cluster Manager Commands get mysqld mycluster G See Section 3 5 1 The get Command for more information about the get commands used in this script Assuming that you have created a cluster named mycluster you can run this script in the client the results vary according to how this cluster is actually configu
66. 4 4 4 4 6 rows in set 0 09 sec data node or data nodes to be changed are running However the command executes much more guickly if the data node or data nodes to be changed are not Note R The change process command can be used whether or not the cluster or the running The next set of examples illustrates this It is possible and sometimes desirable in MySQL Cluster NDB 7 0 and later to use ndbd and ndbmtd data node processes concurrently thus it is also possible using the change process command to change a single data node process from single threaded to multi threaded or from multi threaded to single threaded To do this you must specify the data node process using its process ID First we stop the cluster and verify that all processes are no longer running as shown here mcm stop cluster mycluster 4 Command result Cluster stopped successfully row in set 22 93 sec mcm show status process mycluster dpe f ff f ff NodeId Process Host Status Nodegroup 100 The change process Command 4p 4p 4p 4p 4p 49 ndb mgmd flundra stopped d ndbmtd tonfisk stopped n a 2 ndbmtd grindval stopped n
67. 6 64 Red Hat Linux 5 64 bit Yes cluster 7 2 6 64 linux rhel5 x86 tar gz mcm 1 1 6 64 linux Red Hat Linux 5 64 bit No rhel5 x86 tar gz mcm 1 1 6 32 SUSE Enterprise Linux 32 bit Yes cluster 7 2 6 32 10 linux sles10 x86 tar gz mcm 1 1 6 32 1linux SUSE Enterprise Linux 32 bit No sles10 x86 tar gz 10 mcm 1 1 6 64 SUSE Enterprise Linux 64 bit Yes cluster 7 2 6 64 10 linux sles10 x06 tdr gz mcm 1 1 6 64 1linux SUSE Enterprise Linux 64 bit No sles10 x86 tar gz 10 mem 1 1 6 32 SUSE Enterprise Linux 32 bit Yes cluster 7 2 6 32 11 linux slesl11 x86 tar gz mcm 1 1 6 32 linux SUSE Enterprise Linux 32 bit No slesll1 x86 tar gz 11 mcm 1 1 6 64 SUSE Enterprise Linux 64 bit Yes cluster 7 2 6 64 11 linux sles11 x86 tar gz mcm 1 1 6 64 linux SUSE Enterprise Linux 64 bit No slesl1 x86 tar gz 11 mcm 1 1 6 64 Solaris 10 SPARC 64 bit Yes cl ster 7 2 6 64 MySQL Cluster Manager Agent Installation Package OS Platform Architecture Includes MySQL Cluster NDB 7 2 6 solaris10 sparc tar gz mcm 1 1 6 64 Solaris 10 SPARC 64 bit No solaris10 Sparc tar gz mcm 1 1 6 32 Solaris 10 x86 32 bit Yes cluster 7 2 6 32 solaris10 x906 tarf gz mcm 1 1 6 32 Solaris 10 x86 32 bit No solaris10 xG0 tar gz mcm 1 1 6 64 Solaris 10 x86 64 bit Yes cluster 7 2 6 64 solaris10 x86 tar gz mcm 1
68. 98 The stop process Command for these processes as shown in the output of other mcm client commands such as get see Section 3 5 1 The get Command or in the output of ndo mgm e show 3 8 3 The stop process Command stop process process id cluster name This command stops the running MySQL Cluster process with the process ID process idin the cluster named cluster name The status of the process as shown by show status process must be running see Section 3 6 The show status Command For example suppose that the process ID of a data node in the cluster named mycluster is 3 Then this data node can be stopped as shown here mcm stop process 3 mycluster Command result 4 Process stopped successfully 1 row in set 33 07 sec You can use show status process Or list processes see Section 3 8 5 The list processes Command to obtain process IDs for all processes in a given cluster In the event of a disk failure where MySQL Cluster Manager loses its manager directory including its repository the agent is able to recover information from other agents but it does not actually control processes any longer although it can detect them This is due to the fact that the MySQL Cluster Manager agent cannot access the PID files In this case stop process no longer works and you must kill such process
69. AA Name HostName Value torsk Processi ndbmtd NodeId1 2 Process NodelId2 Level Comment Read only KAZ ZX ZXZAZAZ ck kck AZ AZ ck ck ck Z ZAZ AA AA AAA 6 row KAZ Z ck ck ck ck ck ck ck ck A k k A A A A A A AAA AAA Name NodeId Value 2 Processl ndbmtd NodeId1 2 Process2 Nodeld2 Level Comment Read only ckckckckck ck ck ck AA ck ck ck ck ck Z Z Z AA AA AAA Fs row AK XZ ck ck ck ck ck ck ck AA k A A kk A A A AAA AAA Name DataDir 73 The get Command Value home jon bin mcm mcm data clusters mycluster 49 data Processl ndb mgmd NodeId1 49 Process2 NodelId2 Level Comment kokot k ck kck ck ck ck ck ck kk kk kk kk kk 8 row kckckckckckck ck ck ck ck ck ko kc k kk kk kk kkkkkk k Name HostName Value torsk Processl ndb mgmd NodeId1 49 Process2 NodelId2 Level Comment Read only ck ck ck ck ck ck ck kk kk kk kk kk ck ockockockckckockckck ck 9 row ok ckckckckckckck ck ck kock kk ko kk kk kk kkkkkk k Name NodeId Value 49 Processl ndb mgmd NodeId1 49 Process2 NodelId2 Level Comment Read only ck ck ck ck ck ck ck kk kk kk KKK KKKKKKKKKKK EM row kckckckckckck ck ck ck ck ck ck kk kk kk kk kkkkkk k Name ndbcluster Value Processi mysqld NodelIdl 51 Process2 NodelId2 Level Comment Read only ck ck ck ck ck ck ck 0k 0k Ck ck Ck kk kk kk ckockockckckckckckck 5 row cock ck ckckckckckckckck ck ckckck ck ck ck ck ck ck ck ck ck ck ck ck Name NodeId Value 51 Processi my
70. B 9 PORE LICENSB MM 122 B OSAAN In C Licens Eic a kibuc decane ddd b a laada dv dduna va bud uad TET 123 Oracle acknowledges that certain third party and Open Source software has been used to develop or is incorporated in the MySQL Cluster Manager product This appendix includes required third party license information MySQL Cluster Manager 1 1 Section B 1 GLib License for MySQL Cluster Manager Section B 2 GNU Lesser General Public License Version 2 1 February 1999 Section B 3 1ibevent License Section B 4 libint1 License Section B 5 LPeg Library License Section B 6 Lua liblua License Section B 7 LuaFileSystem Library License Section B 8 md5 Message Digest Algorithm 5 License Section B 9 PCRE License Section B 10 SHA 1 in C License B 1 GLib License for MySQL Cluster Manager The following software may be included in this product GLib You are receiving a copy of the GLib library in both source and object code in the following mcm install dir lib and mcm install dir licenses lgpl folders The terms of the Oracle license do NOT apply to the GLib library it is licensed under the following license separately from the Oracle programs you receive If you do not wish to install this library you may create an exclude file and run tar with the X option as in the following example but the Oracle program might not 109 GNU Lesser General Pub
71. DING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE min heap h Copyright c 2006 Maxim Yegorushkin All rights reserved Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are met 1 Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution 3 The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE AUTHOR AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SER
72. FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM DAMAGES OR OTHER LIABILITY WHETHER IN AN ACTION OF CONTRACT TORT OR OTHERWISE ARISING FROM OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE B 8 md5 Message Digest Algorithm 5 License The following software may be included in this product md5 Message Digest Algorithm 5 This code implements the MD5 message digest algorithm he algorithm is due to Ron Rivest This code was written by Colin Plumb in 1993 no copyright is claimed This code is in the public domain do with it what you wish Equivalent code is available from RSA Data Security Inc This code has been tested against that and is equivalent except that you don t need to include two pages of legalese with every copy he code has been modified by Mikael Ronstroem to handle calculating a hash value of a key that is always a multiple of 4 bytes long Word 0 of the calculated 4 word hash value is returned as the hash value B 9 PCRE License The following software may be included in this product PCRE Perl Compatible Regular Expressions Library PORE LICENCE PCRE is a library of functions to support regular expressions whose syntax and semantics are as close as possible to those of the Perl 5 language Release 7 of PCRE is distributed under the terms of the BSD licence as specified below The
73. L Cluster Manager client set statement from it s w s s Nw set l process type 2 In the case of mysql and api sections of the con ig ini file you also need to determine whether the egivalent set statement should be applied using mysqld or ndbapi as the process name Important AN Some attributes such as HostName and Id are read only HostName is already defined by create site and create cluster node IDs are determined by MySQL Cluster Manager and cannot be overridden In addition you should always keep in mind that MySQL Cluster and MySQL Cluster Manager do not always use the same default values for parameters and their corresponding attributes This is crucial especially in the case of DataDirectory since the data nodes must be able to read these following the importation to acess the cluster s data See Migrating data directories Migrating data directories Do not start the new cluster before making sure that you have configured all processes in the new cluster to use the same data directories used by all nodes in the original cluster If the data nodes of the imported cluster are not configured to read the original data directories the imported cluster will be unable to access the original cluster s data Keep in mind that the default value used by MySQL Cluster Manager for the Dat aDirectory attribute manager directory clusters cluster name node id data is notthe same as the default set by MySQL Cluster o
74. MySQL Cluster Manager 1 1 6 User Manual MySQL Cluster Manager 1 1 6 User Manual Abstract Deprecated release series MySQL Cluster Manager 1 1 has been superseded by MySQL Cluster Manager 1 2 which adds new features and incorporates fixes to bugs found in MySQL Cluster Manager 1 1 MySQL Cluster Manager 1 1 is now considered obsolete and is no longer available for new installations users of MySQL Cluster Manager 1 1 should upgrade to MySQL Cluster Manager 1 2 Thus this document is archival in nature and no longer actively maintained Documentation for the most recent MySQL Cluster Manager 1 2 release can be found at http dev mysql com doc mysql cluster manager 1 2 en You can obtain documentation for the most recent releases of MySQL Cluster and related products at http dev mysal com doc index cluster html incorporates the NDB storage engine for high availability and data redundancy in a distributed computing environment This Manual applies to MySQL Cluster Manager 1 1 6 and contains information that may not apply to older versions of the MySQL Cluster Manager software For documentation covering previous MySQL Cluster Manager releases see MySQL Documentation MySQL Cluster on the MySQL website MySQL Cluster Manager features This manual describes features that may not be included in every version of MySQL Cluster Manager and such features may not be included in the version of MySQL Cluster Manager licensed to you If
75. N SharedBufferSize unsigned 10M 64K 4G N 135 136 Index A add hosts command 57 add package command 58 61 basedir option 59 add process command 96 agent configuration 19 defined 2 2 distribution 7 8 distribution layout 8 installing 7 starting 22 starting Linux 22 starting Windows 24 stopping Linux 23 stopping Windows 26 architecture 1 2 attributes case sensitivity 45 summary table 125 background option limitations 105 backgrounding of commands 105 basedir option add package command 59 C change process command 99 limitations 103 changing data node processess 99 client commands in 43 defined 2 3 executing scripts with 50 mysql client commands in 50 starting 32 client commands 43 add hosts 57 add package 58 61 add process 96 case sensitivity in 45 change process 99 command specific 49 configuration 69 create cluster 63 create site 55 delete cluster 65 delete package 60 delete site 56 get 72 help 55 identifiers in 44 information 48 list clusters 69 list hosts 58 list processes 102 list sites 57 online help 48 options 44 47 48 package 58 process 96 reset 87 restart cluster 67 results returned by 47 set 81 show status 93 site 55 start cluster 66 start process 98 status of 94 stop agents 96 stop cluster 67 stop process 99 syntax 43 upgrade cluster 68 c
76. NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE Parts developed by Adam Langley Based on err c which was adapted from OpenBSD libc err warncode Copyright c 2005 Nick Mathewson Copyright c 2000 Dug Song Copyright c 1993 The Regents of the University of California All rights reserved Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are met 1 Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution 3 Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE REGENTS 118 libevent License OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLU
77. Name tonfisk ndbd ab Read only DataDir opt c3data ndbd 2 HostName flundra ndbd 2 Read only 4 4 4 4 4 rows in set 1 36 sec In the example just shown each filter includes a process type specifier If you omit this specifier from one of the filters you obtain a result that you might not expect mcm get HostName DataDir ndbd mycluster 4 qp 4 4 q4 4 4 Name Value Processi Idi Precess2 ice Level Comment 4 q 4 4 4 HostName grindval ndb mgmd 49 Read only DataDir opt c2data ndbd d HostName tonfisk ndbd Al Read only DataDir opt c3data ndbd 2 78 The get Command HostName flundra ndbd 2 Read only HostName haj mysqld SO Read only HostName torsk mysqld Sil Read only 4 4 4 4 4 rows in set 0 58 sec The filter list Host Name DataDir ndbd is perfectly valid However it actually consists of the filters HostName and DataDir ndbd i
78. Notices Document generated on 2013 08 09 revision 35905 Table of Contents Preface and Legal Notices eessesssssessiesesessiesesssesee sean ee POP KK KK OA enne REE ENRERE snnt nennen V 1 Overview of MySQL Cluster Manager sssssssssssssessesen nennen nen h hn eh sens e err nr nne Ahn hn nn 1 1 1 MySQL Cluster Manager Terminology esssssseeeeeeneenn emen nennen 1 1 2 MySQL Cluster Manager Architecture sssssssssssssseseneeeenenenen enne nennen 2 2 MySQL Cluster Manager Installation Configuration Cluster Setup 2 2 eeeeee een 5 2 1 Obtaining MySQL Cluster Manager eee eee eee meme nnn hehehe eser 5 2 2 Operating Platform and MySQL Cluster Version Compatibility eee 5 2 3 MySQL Cluster Manager Agent Installation ssseseseeeenmnen 7 2 3 1 Installing MySQL Cluster Manager on Unix Platforms eee 8 2 3 2 Installing MySQL Cluster Manager on Windows Platforms eee 9 2 4 MySQL Cluster Manager Configuration File eee 200000000 eee nenene 19 2 5 Starting and Stopping the MySQL Cluster Manager Agent een 22 2 5 1 Starting and Stopping the Agent on Linux ssessseeemnn 22 2 5 2 Starting and Stopping the MySQL Cluster Manager Agent on Windows 24 2 5 3 Installing the MySQL Cluster Manager Agent as a Windows Service 26 2 6 Starting the MyS
79. OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE B 4 libint1 License The following software may be included in this product libintl COPVBHCD E LOS are ons Em Permission is hereby granted free of charge to any person obtaining a copy of this software and associated documentation files the Software to deal in he Software without restriction including without limitation the rights to se copy modify merge publish distribute sublicense and or sell copies of he Software and to permit persons to whom the Software is furnished to do so ubject to the following conditions me S ar H he above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software THE SOFTWARE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT IN NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM DAMAGES OR OTHER LIABILITY WHETHER IN AN ACTION OF CONTRACT TORT OR OTHERWISE ARISING FROM OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE Except as contained i
80. QL Cluster Manager Client esses 32 2 7 Setting Up MySQL Clusters with MySQL Cluster Manager ee eee 35 2 7 1 Creating a MySQL Cluster with MySQL Cluster Manager ee 35 2 7 2 Migrating a MySQL Cluster to MySQL Cluster Manager eee 37 3 MySQL Cluster Manager Client Commands essen emen nennen 43 3 1 Online Help for MySQL Cluster Manager Commands een 48 3 2 MySQL Cluster Manager Site Commands sss eene nnne nenne 55 3 2 1 The create site Command eee 000000 ee een ne sese sisi nn 55 3 2 2 The delete site Commi and eines elle iaaiiai 56 3 2 3 The list sites Command sae iaaa EERE nnne ens 57 3 2 4 The add hosts Command ect repe t ocetaa cest i aiaa dug 57 3 2 5 The list hosts Command sissisota deniona eee eee eee eee nnne ens 58 3 3 MySQL Cluster Manager Package Commands sse 58 3 3 1 The add package Command eese 58 3 3 2 The delete package Command 0000000000000 0000 neon nn 60 3 3 3 The list packages Command sessi eene 61 3 4 MySQL Cluster Manager Cluster Commands sss emen 63 3 4 1 The create cluster Command eee eee 000000 e onen sss 63 3 4 2 The delete cluster Command 2 022e 0020000000000 nene oo ana anne nn 65 3 4 3 The start cluster Command 22
81. RS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE End B 10 SHA 1 in C License The following software may be included in this product SHA 1 in C BRLA I sim By Steve Reid lt steve edmweb com gt 100 Public Domain 123 124 Appendix C Attribute Summary Tables This appendix provides tables of configuration attributes grouped according to their process type or the section of the MySQL Cluster configuration file in which they appear Each table provides the following information Name The name of the attribute The name of the attribute is linked to the attribute s full description in the online MySQL Cluster documentation Type Units The data type or unit by which the attribute is measured e Range The default value of the attribute if not set by the us
82. SK mysqld TORSK 3306 mysqld TORSK 730 ndbapi is Connect to the database by running C Program Files x86 MMySQLMMySQL Cluster Manager 1 1 4 eluster bin mysql h TORSK P 3306 u root You can then connect to the agent using the mcm client see Section 2 6 Starting the MySQL Cluster Manager Client and to either of the MySQL Servers running on ports 3306 and 3307 using mysql or another MySQL client application When starting the MySQL Cluster Manager agent for the first time you may see one or more Windows Security Alert dialogs such as the one shown here 24 Starting and Stopping the MySQL Cluster Manager Agent on Windows Windows Security Alert Windows Firewall has blocked some features of this program r Windows Firewall has blocked some features of momd exe on all public and private networks Name mcm d exel E Publisher Unknown Path C program files x86 mysql mysql duster manager 1 1 4lbinmamd exe Allow mcmd exe to communicate on these networks I Private networks such as my home or work network Public networks such as those in airports and coffee shops not recommended because these networks often have little or no security You should grant permission to connect to private networks for any of the programs mcmd exe ndb_mgmd exe ndbd exe ndbmtd exe of mysqid exe To do so check the Private Networks box and then click the Allow access button It is generally not necessary
83. SQL and other syntax Backgrounded commands and error handling MySQL Cluster Manager client commands which are run in the background that is when they are invoked with the background or B option do not issue any error messages in the client If you run a command in the background you must check the agent log or use the show status command to verify whether the backgrounded command was successful 105 106 Appendix A Changes in MySQL Cluster Manager MySQL Cluster Manager release notes are no longer published in the MySQL Cluster Manager User Manual Release notes for the changes in each release of mcm are located at MySQL Cluster Manager 1 1 Release Notes 107 108 Appendix B Licenses for Third Party Components Used in MySQL Cluster Manager 1 1 6 Table of Contents B 1 GLib License for MySQL Cluster Manager sssssssssseeneemeenenen nene 109 B 2 GNU Lesser General Public License Version 2 1 February 1999 lt 110 B 3 1ibewent LICENSE exert e Rene Em rt x Fein c eios azen bad elle add dues 118 B4 iba l LICENSE Hc 120 B 5 LPeg Library License i e ee EENIA du K Rodna EEEE d esa tns dedu N REEE A A ESKE egceteay ecasteuy EENES SEENE 120 BiG Lua Ibl a Bio ig p 121 B 7 tuaFileSystem Library LICONS eiit eire tette eee Eni eee E aee xe enia exe PS exe Eod exe pau 121 B 8 md5 Message Digest Algorithm 5 License sssem Hee 122
84. VICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE win32 c Copyright 2000 2002 Niels Provos Copyright 2003 Michael A Davis All rights reserved Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are met 1 Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution 3 The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE AUTHOR AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL 119 libintl License DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS
85. Y AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESSED OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU SHOULD THE LIBRARY PROVE DEFECTIVE YOU ASSUME THE COST OF ALL NECESSARY SERVICING REPAIR OR CORRECTION 16 IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER OR ANY OTHER PARTY WHO MAY MODIFY AND OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE BE LIABLE TO YOU FOR DAMAGES INCLUDING ANY GENERAL SPECIAL INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Libraries If you develop a new library and you want it to be of the greatest possible use to the public we recommend making it free software that everyone can redistribute and change You can do so by permitting redistribution under these terms or alternatively under the terms of the ordinary General Public License To apply these terms attach the following notices to the libra
86. age previously registered using add package see Section 3 3 1 The add package Command Alist process host list of MySQL Cluster processes and the hosts on which they are to run supplied as the value of the processhosts option short form R with list items separated by commas As with other lists passed as option values in MySQL Cluster Manager commands you must not use spaces before or after the commas Each item in the process host list consists of the name of a MySQL Cluster process joined with the name of the host on which it is located using an amphora sign also sometimes know as the at sign Permitted values for processes are ndb mgmd ndbd and mysqld When the cluster employs MySQL Cluster NDB 7 0 or later you can also use ndbmtd as process name In other words a valid process name is the name of a MySQL Cluster process daemon binary To support running your own NDB API applications with a cluster under MySQL Cluster Manager it is also possible to use ndbapi as a process type Such applications can be connected to a managed cluster Currently MySQL Cluster Manager recognises only that an NDB API application is connected to the cluster the NDB API application itself must be started stopped and configured manually It is also possible to specify one or more free mysqld and ndbapi processes without any hosts To do this simply use the wildcard asterisk character in place of the hostname or IP addres
87. ager agent as a service the service is not started automatically until Windows is started If you do not wish to restart Windows then you must start the service manually using either NET START on the command line or the graphical control provided in the Windows Service Manager You can remove the service using the SC DELETE command and the name of the service in this case MCM that was used in the SC CREATE command as shown here 31 Starting the MySQL Cluster Manager Client Microsoft Windows Version V rol Copyright c 2009 Hicrosoft Corporation All rights reserved C Windows system32 gt HET STOP MOM mE f The MySQL Cluster Manager 1 1 4 service is stopping The MySQL Cluster Manager 1 1 4 service was stopped successfully gt Windows systemad SE DELETE MCH C DeleteService SUCCESS C Windows systemd2 gt If the service is running at the time that SC DELETE is executed the removal of the service takes effect the next time the service is stopped In such a case you must stop the previous instance of the service manually and allow it to be removed before you can reinstall the service Once you have installed the MySQL Cluster Manager agent and the service is running correctly you are ready to connect to it using the MySQL Cluster Manager client See for information about how to do this 2 6 Starting the MySQL Cluster Manager Client This section covers starting the MySQL Cluster Manager client and con
88. ages are the reason we use the ordinary General Public License for many libraries However the Lesser license provides advantages in certain Special circumstances For example on rare occasions there may be a special need to encourage the widest possible use of a certain library so that it becomes a de facto standard To achieve this non free programs must be allowed to use the library A more frequent case is that a free library does the same job as widely used non free libraries In this case there is little to gain by limiting the free library to free software only so we use the Lesser General Public License In other cases permission to use a particular library in non free programs enables a greater number of people to use a large body of free software For example permission to use the GNU C Library in non free programs enables many more people to use the whole GNU 111 GNU Lesser General Public License Version 2 1 February 1999 operating system as well as its variant the GNU Linux operating system Although the Lesser General Public License is Less protective of the users freedom it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library The precise terms and conditions for copying distribution and modification follow Pay close attention to the difference between a work based on the library and a w
89. ameQ8host 96 The add process Command process name ndb mgmd ndbd ndbmtd mnysqld ndbapi attribute assignment list attribute assignment attribute assignment attribute assignment attribute name process name value This command adds one or more processes to an existing cluster these being specified using a process host list whose format is the same as that used with the create cluster command see Section 3 4 1 The create cluster Command Any hosts referenced in the list must be members of the site to which the cluster belongs Any new processes added by this command must be started explicitly using start process added see Section 3 8 2 The start process Command For example the following add process command adds two mysqld processes on hosts torsk and kolja to the cluster named mycluster mcm add process processhosts mysqld itorsk mysqld kolja mysite Command result Processes added successfully i cow nS Zam OS OSE c Processes added before the cluster is started for the first time are started with the cluster This makes it possible to use this command to break down what would otherwise be very long create cluster commands Consider the following set of commands which creates and then starts a cluster named mycluster create cluster processhosts ndb_mgmd hos
90. and mcm get SendBufferMemory mycluster2 4 4 4 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4 4 4 SendBufferMemory 4M ndbd 2 mysqld 4 Process SendBufferMemory 4M ndbd 2 mysqld 5 Process SendBufferMemory 4M ndbd 3 mysqld 4 Process SendBufferMemory 8M ndbd 3 mysqld 3 4 4 4 4 4 4 4 4 4 rows in set 0 59 sec Suppose that you wish to reset SendBuf ferMemory only for the connection between the ndbd process having process ID 3 and the mysgld process having process ID 5 The SendBuf ferMemory setting that applies to this connection is specified on the instance level as you can see because the Level column value corresponding to this connection is empty this means that it is possible to reset this value on the instance level You can do this using the reset command shown here mcm reset SendBufferMemory ndbd 3 mysgld 5 mycluster2 4 Command result q4 Cluster reconfigured successfully 1 row in set 7 03 sec You can verify that the attribute was reset using the get comman
91. and or new versions of the Lesser General Public License from time to time Such new versions will be similar in spirit to the present version but may differ in detail to address new problems or concerns Each version is given a distinguishing version number If the Library Specifies a version number of this License which applies to it and any later version you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation If the Library does not specify a license version number you may choose any version ever published by the Free Software Foundation 14 If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these write to the author to ask for permission For software which is copyrighted by the Free Software Foundation write to the Free Software Foundation we sometimes make exceptions for this Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally 116 GNU Lesser General Public License Version 2 1 February 1999 NO WARRANTY 15 BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE THERE IS NO WARRANTY FOR THE LIBRARY TO THE EXTENT PERMITTED BY APPLICABLE LAW EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND OR OTHER PARTIES PROVIDE THE LIBRAR
92. art the installer you may see a Windows Security Warning screen as shown here 10 Installing MySQL Cluster Manager on Windows Platforms Open File Security Warning The publisher could not be verified Are you sure you want to run this software Mame 4 releases mam 1 1 4 duster 7 2 4 win32 x86 msi Publisher Unknown Publisher Type Windows Installer Package Hom X MCMM 1 4 eleasesmem 1 1 4 duster 7 2 4 w an oes x This file does not have a valid digital signature that verifies its Q emen apo E C If you trust the source of the installer and that it has not been tampered with choose Run which allows the installer to continue to the Welcome screen shown in the following image Installing MySQL Cluster Manager on Windows Platforms T MySQL Cluster Manager 1 1 4 Setup Welcome to the MySQL Cluster Manager 1 1 4 Setup Wizard Please wait while the Setup Wizard prepares to guide you through the installation Computing space requirements Click the Next button to continue to the License Agreement screen as shown in the next figure Installing MySQL Cluster Manager on Windows Platforms ie MySQL Cluster Manager 1 1 4 Setup Please read the following icense agreement carefully MySQL Cluster Manager 1 1 Copyright 2010 2012 Oracle and or its affiliates All rights reserved Ihis software and related documentation are provided under a license agreement contain
93. at you have identified the hosts on which you plan to run the cluster and have decided on the types and distributions of the different types of nodes among these hosts as well as basic configuration requirements based on these factors and the hardware charactersitics of the host machines purposes simply by invoking mema with the boot strap option See Section 2 5 Note E You can create and start a MySQL Cluster on a single host for testing or similar Starting and Stopping the MySQL Cluster Manager Agent Creating a new cluster consists of the following tasks MySQL Cluster Manager agent installation and startup Install the MySQL Cluster Manager software distribution make any necessary edits of the agent configuration files and start the agent 35 Creating a MySQL Cluster with MySQL Cluster Manager processes as explained in Chapter 2 MySQL Cluster Manager Installation Configuration Cluster Setup Agent processes must be running on all cluster hosts before you can create a cluster This means that you need to place a complete copy of the MySQL Cluster Manager software distribution including license files which are supplied separately on every host The MySQL Cluster Manager software does not have to be in a specific location or even the same location on all hosts but it must be present you cannot manage any cluster processes hosted on a computer where mcmd is not also running MySQL Cluster Manager client session
94. ate your acceptance of this License to do so and all its terms and conditions for copying distributing or modifying the Library or works based on it 10 Each time you redistribute the Library or any work based on the Library the recipient automatically receives a license from the original licensor to copy distribute link with or modify the Library 115 GNU Lesser General Public License Version 2 1 February 1999 subject to these terms and conditions You may not impose any further restrictions on the recipients exercise of the rights granted herein You are not responsible for enforcing compliance by third parties with this License 11 If as a consequence of a court judgment or allegation of patent infringement or for any other reason not limited to patent issues conditions are imposed on you whether by court order agreement or otherwise that contradict the conditions of this License they do not excuse you from the conditions of this License If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations then as a consequence you may not distribute the Library at all For example if a patent license would not permit royalty free redistribution of the Library by all those who receive copies directly or indirectly through you then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library If a
95. ay prefer to set this to warning or error pid file A valid path to a Not normally used By uncommenting this line you can process ID pid cause a process ID file to be created file as mcmd pidin the MySQL Cluster Manager installation directory but this is not usually necessary Not supported on Windows manager The name of the Default admin The user name used for the MySQL username MySQL Cluster Cluster Manager user account Manager user optional manager The password for Default super The password used for the MySQL password the MySQL Cluster Cluster Manager user account Manager user account optional manager A valid absolute Default mcm data The manager directory contains directory path On Linux in the MySQL collections of MySQL Cluster Manager if the directory does not exist itis created on Windows the directory must be created if it does not exist Also on Windows the path may not contain any spaces and you must replace any backslash X characters with forward slashes Cluster Manager installation directory data files and MySQL Cluster configuration and data files such a repositories and these files is provided later in this section 21 Starting and Stopping the MySQL Cluster Manager Agent Using the manager username user name and manager password pass word options causes the creation of a MySQL user account having the username user name and the password
96. bd 10 100 10 98 ndbd 10 100 10 99 X mysqld 10 100 10 100 ndbapi 10 100 10 100 X ndbapi 10 100 10 100 ndbapi 10 100 10 100 gt mycluster 4 Command result Cluster created successfully 1 row in set 6 58 sec After this you can use a set command like this one to set the size of the connection pool according to the number of excess connections available in the config ini file mcm set ndb cluster connection pool mysqld 4 user attribute not supported for mysqld Trying to set the user attribute for a mysqld process is not currently supported and results in a warning being written to the MySQL Cluster Manager log 3 5 3 The reset Command reset filter specification list cluster name filter specification list filter specification filter specification filter specification attribute name process specification process specification 87 The reset Command process specification process name process id This command resets an attribute to its default value Attributes can be set on either the process level or instance level To reset an attribute on the process level use a filter specification having the form attribute name process name where attribute name is the name of the attribute to be reset and process name is the name of a MySQL Cluster process To reset a configuration attribute on the
97. bilities handled by the MySQL Cluster Manager agent include the following Starting stopping and restarting cluster nodes Cluster configuration changes Cluster software upgrades Host and node status reporting Recovery of failed cluster nodes Creating performing initial configuration of or starting a cluster requires that agent processes be running on all cluster hosts Once the cluster has been started it continues to run even if one or more agent MySQL Cluster Manager Architecture processes fail However any failed agent processes must be restarted before you can perform addition cluster management functions Client A MySQL Cluster Manager client is a software application used to access an MySQL Cluster Manager agent In MySQL Cluster Manager the client is actually nothing more than the mysql command line client started with the options that are necessary for it to connect to an MySQL Cluster Manager agent MySQL Cluster Manager 1 1 6 and later releases include an mcm client for ease of use this client consists of a script that acts as a wrapper for the mysq1 client with these options By way of example we show how MySQL Cluster Manager would be deployed for use with a MySQL Cluster running on 4 host computers This is illustrated in the following diagram 192 168 0 10 192 168 0 MySQL Cluster node ast MySQL Cluster Manager agent MySQL Cluster Manager client In this example cluster
98. binary programs such as ndb mgmd ndbd ndbmtd and ndb mgm can be found in cluster bin For more information see MySQL Installation Layout for Generic Unix Linux Binary Package and Installing a MySQL Cluster Binary Release on Linux in the MySQL Manual The MySQL Cluster Manager agent by default writes its log file as mcmd 1og in the installation directory When the agent run for the first time it also creates an mcm data directory where the agent stores its own configuration data Also by default the configuration data log files and data node file systems for a given MySQL Cluster under MySQL Cluster Manager control and named ciuster name can be found in mcm data clusters cluster name The location of the MySQL Cluster Manager agent configuration file log file and data directory can be controlled with mcmd startup options or by making changes in the agent configuration file For more information see Section 2 4 MySQL Cluster Manager Configuration File and Section 2 5 Starting and Stopping the MySQL Cluster Manager Agent 2 3 2 Installing MySQL Cluster Manager on Windows Platforms To install MySQL Cluster Manager 1 1 6 on Windows platforms you should first have downloaded the MSI installer file mcm 1 1 4 cluster 7 2 4 win32 x86 msi see Section 2 1 Obtaining MySQL Cluster Manager 1 1 6 for Windows is 32 bit as is the bundled MySQL Cluster NDB 7 2 4 these run on both 32 bit and 64 bit versions of Windows As men
99. ck ckockockckckckckock ck 1099 row kckck ck ck ckck ck ck ck ck ck ck ko k kk kk kk kkkkk k Name NodeId Value 52 Processi ndbapi NodeId1 52 Process2 NodelId2 76 The get Command Level Comment Read only ckckckckck ck ck ck AA ck ck ck ck ck kc k Z ZA AA AAA TOO row KAZ Z ck ck ck ck ck ck ck ck A k A A kk A A A AAA AAA Name TotalSendBufferMemory Value O0 Processl ndbapi NodeId1 52 Process2 NodelId2 Level Default Comment AA ZZ ck ck ck ck ck ckck ck ck ck Z Z Z Z Z A A AA AAA mo row KAZ ck ck ck ck ck ckck ck ck AAA A A A A A AA AA AAA Name wan Value false Processl ndbapi NodeId1 52 Process2 NodeId2 Level Default Comment 1101 rows in set 0 09 sec As you can see the output from this get command is quite long and the number of rows generated increases with the number of nodes in the cluster However it is possible to filter the output so that you can view only the attribute or attributes in which you are interested This can be done by using a comma separated list of one or more filter specifications A filter specification is defined as shown here condensed from that given at the beginning of this section but effectively the same attribute name process name process id Filtering can be applied per attribute per process type and per process instance We now provide some examples illustrating the use of such filters To obtain the value of a given attribute for all process
100. configured successfully row in set 7 78 sec mcm get d wait timeout mysgld 4 mycluster 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 qp 4 4 4 wait_timeout 200 mysqld 4 4 4 4 4 4 qp 4p row in set 0 98 sec Because the Level column is empty we know that this setting applies on the instance level If you try to reset it on the process level the attempt fails as shown here mcm reset wait timeout mysgld mycluster2 ERROR 6010 00MGR No matching user defined setting was found for config attribute wait timeout If you wish to reset this attribute to its default value you must use the reset command with the instance level filter specification wait timeout mysqid 4 as shown here mcm reset wait timeout mysqld 4 mycluster 89 The reset Command 4 Command result q4 Cluster reconfigured successfully 1 row in set 7 61 sec Once you have reset wait timeout it no longer appears in the output of the earlier get command mcm gt
101. cores in their names For example you can use either ndb batch size or ndb batch size with the MySQL Server and the variable is set correctly This is not the case in MySQL Cluster Manager where only the forms using underscores are accepted as attribute names For example assuming that mycluster is a viable cluster the command set ndb batch size mysgld 65536 mycluster works to set the size of ndb batch size on all mysqld processes in the cluster but set ndb batch size mysqld 65536 mycluster fails Dependencies between MySQL Cluster Manager mysqld attributes and MySQL server variables MySQL Cluster Manager does not track dependencies between mysqld attributes MySQL server options and variables For example MySQL Server 5 1 and earlier require when the binlog format attribute is set that the 1og bin attribute be used as well if binlog format is used without 1og bin mysqld fails to start MySQL Server Bug 42928 fixed in MySQL 5 5 and MySQL Cluster NDB 7 2 If you do this using MySQL Cluster Manager however the MySQL Cluster Manager agent reports that the operation was started successfully and from MySQL Cluster Manager s point of view this is correct MySQL Cluster Manager started the mysqid process with the indicated attribute settings and it is up to the operator to verify that the result was the one expected In such cases it is a good idea to check the status of the mysqld process perhaps using show status operation before co
102. creen as shown here 18 MySQL Cluster Manager Configuration File is MySQL Cluster Manager 1 1 4 Setup a x Completed the MySQL Cluster Manager 1 1 4 Setup Wizard Chick the Finish button to exit the Setup Wizard MySQL Cluster Manager 1 1 6 has now been installed to the destination directory click the Finish button to exit the installer 2 4 MySQL Cluster Manager Configuration File Before starting the MySQL Cluster Manager agent you should make any necessary changes to the mcmd section of the agent configuration file supplied with MySQL Cluster Manager as etc mcmd ini in the installation directory On Linux and similar operating systems you can edit this file in place on Windows it is recommended that you save a copy of this file to a convenient location for which the path does not contain any spaces such as C ncm data Note R Prior to MySQL Cluster Manager 1 1 1 this section of the configuration file used the heading mysql proxy The old name is still supported for backward compatibility but is now deprecated and is thus subject to removal in a future release of MySQL Cluster Manager For this reason you should change any 19 MySQL Cluster Manager Configuration File mysgl proxy section headings in existing configuration files to mcmd when upgrading to MySQL Cluster Manager 1 1 6 A character in the MySQL Cluster Manager configuration file indicates the beginning of a comment the
103. ction 2 5 3 Installing the MySQL Cluster Manager Agent as a Windows Service After installing the MySQL Cluster Manager Agent as a Windows service you can start and stop the agent using the Windows Service Manager The installation also configures the agent to start automatically whenever Windows starts and to shut down safely whenever Windows shuts down Note E The Windows service can be used to control the running of MySQL Cluster Manager agents on a single host only To shut down agents on multiple hosts you can use the stop agents command in the MySQL Cluster Manager client See Section 3 7 The stop agents Command for more information The installation is performed using the command prompt cmd exe as with installing or removing any Windows service it must also be done as a user having sufficient permissions such the system Administrator account If the account you are currently using has Administrator privileges you can simply start cmd exe Otherwise you must run the command prompt program as the Administrator To do this first locate a shortcut to the command prompt On most Windows systems you can do this using the Start Menu Find Programs or All Programs in some Windows versions then navigate to Accessories Under Accessories right click on the Command Prompt menu item From the context menu that appears select Run as Administrator You can see how this looks on a typical Windows system in the next figu
104. d However as noted previously once the instance level setting has been removed the process level setting for this attribute again takes effect so that the same setting applies to all connections between ndbd and mysqld processes as shown here mcm gt get SendBufferMemory mycluster2 4 4 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4 SendBufferMemory 4M ndbd 2 mysqld 4 Process SendBufferMemory 4M ndbd 2 mysqld 5 Process SendBufferMemory 4M ndbd 3 mysqld 4 Process SendBufferMemory 4M ndbd 3 mysqld 5 Process 4 4 4 4 rows in set 0 87 sec 92 The show status Command To reset this attribute on the process level you can use the following reset command mcm reset SendBufferMemory ndbd mysqld mycluster2 Command result q4 Cluster reconfigured successfully 1 row in set 8 01 sec You can verify that the attribute has been reset for al
105. d client programs varies according to platform On Unix platforms you must extract the binaries and other files from a tar gz archive and copy them to the correct locations manually For Windows platforms an MSI installer is provided which largely automates this process Installation of MySQL Cluster Manager using each of these methods is covered in the next two sections Installing MySQL Cluster Manager on Unix Platforms 2 3 1 Installing MySQL Cluster Manager on Unix Platforms Installing the MySQL Cluster Manager agent on Linux and similar platforms can be accomplished using the following steps 1 Extract the MySQL Cluster Manager 1 1 6 program and other files from the distribution archive You must install a copy of MySQL Cluster Manager on each computer that you intend to use as a MySQL Cluster host In other words you need to install MySQL Cluster Manager on each host that is a member of a MySQL Cluster Manager management site For each host you should use the MySQL Cluster Manager build that matches that computer s operating system and processor architecture On Linux systems you can unpack the archive using the following command using mcm 1 1 4 64 cluster 7 2 4 64 linux slesl11 x86 tar gz as an example the actual filename will vary according to the MySQL Cluster Manager build that you intend to deploy shell tar zxvf mcm 1 1 4 64 cluster 7 2 4 64 linux slesll x86 tar gz This command unpacks the archive into a di
106. delete it In addition if you execute a delete site command with the force option using one management agent while a different management agent is not running you must remove the missing management agent s site files manually For more information on site files see Section 2 4 MySQL Cluster Manager Configuration File 3 2 3 The 1ist sites Command list sites This command returns a list of the sites known to the management agent It does not require any arguments An example is shown here mcm list sites qp 4 Tp qp Site Pore toce Hosts 4 4 n sec dS aduexeeub geimisia nea 4 4 qp qp 1 row in set 0 06 sec The outputof list sites contains the following columns Site The name of the site Port The TCP IP port used for communications between management agents Local Hosts A comma separated list of the hosts making up the site 3 2 4 The add hosts Command add hosts hostsehost list site name O SA MS nose MBS z osel This command adds one or more hosts to an existing management site Agents using the same port as the management site must be running on any hosts added using this command It takes as arguments a required option host s whose value is a comma separated list of one or more hosts to be added to the site and the name of the site to which t
107. dresses or as localhost if this is applicable Otherwise MySQL Cluster Manager will be unable to connect to the agent processes on those hosts See Section 4 1 MySQL Cluster Manager Usage and Design Limitations 3 8 2 The start process Command start process initial i process id added cluster name This command starts the MySQL Cluster process having the process ID process idinthe cluster named cluster name The status of the process to be started as shown by show status process must be added or stopped see Section 3 6 The show status Command This example demonstrates how to start the process having the process ID 1 belonging to the cluster mycluster mcm start process 1 mycluster 4 Command result 4 Process started successfully 1 row in set 13 93 sec When the initial option short form i is used MySQL Cluster Manager starts a data node process with the initial option causing the data node to rebuild its file system Invoking this command with the added option rather than with a process ID starts all nodes previously added to the cluster using add process but not yet started You can obtain process IDs for all processes in a given cluster using show status processOrlist processes see Section 3 8 5 The 1ist processes Command These are the same as the node IDs
108. e as in the standard mysal client as shown in this example mcm get DataMemory mycluster G KKKKKKKKKKKKKKKKKKKKKKKKKKK il row KKKKKKKKKKKKKKKKKKKKKKKKKKK Name DataMemory Value 500M Processl ndbd delle Z Process2 CW g Level Process Comment KKKKKKKKKKKKKKKKKKKKKKKKKKK pos row KKKKKKKKKKKKKKKKKKKKKKKKKKK Name DataMemory Value 500M Processl ndbd ies 3 Process2 TC g Level Process Comment 2 rows in set 0 22 sec By convention for reasons of readability we do not normally include the command terminator when showing the syntax for a command in Backus Naur format or when including a MySQL Cluster Manager command inline in this text However if you do not use a statement terminator when you enter the command in the MySQL Cluster Manager client the client displays a special waiting prompt gt until you supply a terminator as shown here mcm list sites r Empty set 1 50 sec The is the same as the behavior of the mysq1 client when you fail to end a statement with a terminator A command option can also in many cases accept or even reguire a set of one or more values The next example includes such an option and also demonstrates setting of multiple values in a single option by passing them to the option as a comma separated list mcm create site hosts tonfisk flundra mysite 46 Site created successfully 1 row in set 7 41 sec The command just shown creates a site na
109. e locations we do not support concurrent client sessions You should be careful always to allow a command issued in one mcm client session to finish executing before issuing a new command in a different client session This is true especially when using the B or background option with mcm client commands see Backgrounded commands and error handling IPv6 and host names Windows When IPv6 support is enabled on Windows systems host names other than localhost are resolved using IPv6 When an IPv6 enabled Windows system is used as a MySQL Cluster host under MySQL Cluster Manager you must reference it using its IPv4 address or as localhost if this is applicable Otherwise mcm will be unable to connect to the agent process on that host This applies to host names used with the MySQL Cluster Manager client commands create cluster create site add hosts add package delete package stop agents and add process 4 2 MySQL Cluster Manager 1 1 6 Limitations Relating to the MySQL Server 103 MySQL Cluster Manager Limitations Relating to MySQL Cluster The limitations described in this section relate to functionality in the MySQL Server that is unsupported or reduced or otherwise differs when using it with MySQL Cluster Manager Replication Replication is currently not directly supported by MySQL Cluster Manager See Section 4 3 MySQL Cluster Manager Limitations Relating to MySQL Cluster for more information Limited mysqid o
110. ead only attributes or that have been set by the user after the cluster was created Hereafter in this discussion we refer to these as non default attributes Thus prior to setting any configuration attributes you can obtain a list of all mandatory and read only attributes by running the simplest possible form of this command as shown here mcm get mycluster mcm get mycluster G AA XZ ck ck ck ck ck kk ck ck ck ck ck kk kk AAA A AAA as row okckckck ck ckck ck ck k A A kk k A A A A A A AA AAA Name DataDir Value home jon bin mcm mcm data clusters mycluster 1 data Processi ndbmtd NodeId1 1 Process NodelId2 Level Comment AKA XZ ZAZ ck ck ckck ck ck ck ck ck kk A A kkk k k 2 row Okckck ck ck ck ck ck ck ck ck A k A A kk A A A AAA AAA Name HostName Value torsk Processi ndbmtd NodeId1 1 Process2 NodelId2 Level Comment Read only ckckckckck ck ck ck ckck ck ck ck ck ck Z k k AA AA AAA B row okckckckck ck ck kck ck A A A k A A A A A A AAA AAA Name NodeId Value 1 Processl ndbmtd NodeId1 1 Process2 NodeId2 Level Comment Read only ckckckckck ck ck kck ck ck ck ck ck ck kk ZA AA AA AAA do row Okckckckck ck ck ck ck ck ck ck k A A kk A A kk AA AAA Name DataDir Value home jon bin mcm mcm data clusters mycluster 2 data Processi ndbmtd NodeId1 2 Process2 NodelId2 Level Comment ckckckckck ck ck ck kck ck ck ck ck ck kk k kk kkk k k ig row okckckckck ck ck ck ck ck ck A k A A kk A A A A AA A
111. ed in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing If this software or related documentation is delivered to the U S Government or anyone licensing it on behalf of the U S Government the following notice is applicable U S GOVERNMENT RIGHTS Programs software databases and related documentation and technical data delivered to U S Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such the use duplication disclosure modification and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract and to the extent applicable by the terms of the Government contract the additional rights set forth in FAR 52 227 19 Commercial Computer Software License December 2007 Oracle USA Inc 500 Oracle Parkway Redwood City CA 94065 This software is developed for general use in a variety of inf
112. ed in it and that the Library and its use are covered by this License You must supply a copy of this License If the work during execution displays copyright notices you must include the copyright notice for the Library among them as well as a reference directing the user to the copy of this License Also you must do one of these things a Accompany the work with the complete corresponding machine readable source code for the Library including whatever changes were used in the work which must be distributed under Sections 1 and 2 above and if the work is an executable linked with the Library with the complete machine readable work that uses the Library as object code and or source code so that the user can modify the Library and then relink to produce a modified executable containing the modified Library It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions b Use a suitable shared library mechanism for linking with the Library A suitable mechanism is one that 1 uses at run time a copy of the library already present on the user s computer system rather than copying library functions into the executable and 2 114 GNU Lesser General Public License Version 2 1 February 1999 will operate properly with a modified version of the library if the user installs one as long as the modified ver
113. el can also be set using the mcma startup options 1og file and 1og level respectively 2 5 Starting and Stopping the MySQL Cluster Manager Agent Before you can start using MySQL Cluster Manager to create and manage a MySQL Cluster the MySQL Cluster Manager agent must be started on each computer that is intended to host one or more nodes in the MySQL Cluster to be managed 2 5 1 Starting and Stopping the Agent on Linux To start the MySQL Cluster Manager agent on a given host running a Linux or similar operating system you should run mcma found in the bin directory within the manager installation directory on that host The complete syntax for mcmd is shown here mcmd defaults file bootstrap log file log level 22 Starting and Stopping the Agent on Linux mcmd normally runs in the foreground If you wish you can use your platform s usual mechanism for backgrounding a process On a Linux system you can do this by appending an ampersand character amp like this not including any options that might be required shell bin mcmd amp By default the agent assumes that the agent configuration file is et c mcmd ini in the MySQL Cluster Manager installation directory You can tell the agent to use a different configuration file by passing the path to this file to the defaults file option as shown here shell bin memd defaults file home mcm mcm agent conf The bootstrap option cause
114. ely removes the instance level setting the instance level setting is not preserved and resetting the attribute on the process level merely restores the default setting for all processes of that type See Section 3 5 MySQL Cluster Manager Configuration Commands for more information Resetting TCP Connection Attributes Certain configuration attributes such as those relating to TCP connections apply to connections between processes rather than to individual processes or individual process types As shown elsewhere see Setting TCP Connection Attributes when you set such an attribute on the process level using MySQL Cluster Manager this means that the attribute applies to all connections between the two types of processes specified when issuing the sec command It is also possible to set such an attribute on the instance level in which case it applies only to a single connection between two process instances Similarly it is possible to reset such an attribute on either the process or instance level depending on the level or levels at which it was set In either case an extended form of the process specifier is required just as it is when setting an attribute that applies to a connection between processes Assume that the SendBuf ferMemory attribute has previously been set for all connections between the two ndbd processes and the two mysqld processes that are found in a MySQL Cluster named mycluster2 as shown in the output of this get comm
115. en set see Section 3 5 1 The get Command This means that prior to setting SendBuf ferMemory for the first time you obtain an empty result if you try to retrieve its value as shown here mcm get SendBufferMemory mycluster2 Empty set 0 18 sec mcm get include defaults SendBufferMemory mycluster2 Empty set 0 93 sec To set the SendBuf ferMemory to 4 MB for all TCP connections between data nodes and SQL nodes you can use the command shown here mcm set SendBufferMemory ndbd mysgld 4M mycluster2 4 Command result 4 Cluster reconfigured successfully 1 row in set 6 44 sec lf you check the attribute s value afterwards using get you can see that the value is applied to all possible connections between each of the two ndbd processes and each of the two mysqld processes in mycluster2 thus there are four rows in the output mcm get SendBufferMemory mycluster2 4 4 4 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 SendBufferMemory 4M ndbd 2 mysqld 4 Process SendBuff
116. ent HostName haj mysqid 50 Read only ck ck ck ck ck ck ck A A A ck A ck ck ck ck ck kk kk kk kA kx 3s row KKKKKKKKKKKKKKKKKKKKKKKKKKK Name Value Processl NodelIdl Process2 NodelId2 Level Comment log error home jon bin mcm mcm data clusters mycluster 50 data mysqld 50 out err mysqid 50 52 Online Help for MySQL Cluster Manager Commands Ck ock ck ck ok ck kk A A A ko 4 ck ck ck ck k k kk kk kk d row ck ck ck ck ck ck ck ck ck ck ck ck 4 kc k kk kk kk kk kk Name ndb nodeid Value 50 Processl mysqld NodeId1 50 Process2 NodeId2 Level Comment Read only ck ck ck ck ck ck ck ck ck Sk ock kk ck ko ko ko ko ko ko kock kc kock s row ck ck ck ck ck ck ck ck ck RREK kk ko ko k ko ko kock kc kck R Name ndbcluster Value Processl mysald NodeId1 50 Process2 NodeId2 Level Comment Read only ck ck ck ck ck ck ck ck ck Sk ock ck ckock ZA ko A ko ko A A ko AAA 6 row kkkkxkxkxkkkkkkkkkkkkkkkkkkkxkxx k Name NodeId Value 50 Processl mysqld NodeId1 50 Process2 NodeId2 Level Comment Read only ck ck ck ck ck ck ck ck ck ck ock ck ockock ko ko ko ko ko ck kock ck KKK Whe row KKEKEKKKKKKKKKKKKKKKKKKKAKKKKK Name port Value 3306 Processl mysqld NodeId1 50 Process2 NodelId2 Level Comment ck ck ck ck ck ck ck ck ck ck ock ck ckockckock ko ko kock c kock kc kok K O row ck ck ck ck ck ck ck ck ck koc KA AA AA k ko ko kock kc AAA Name socket Value tmp mysql mycluster 50 sock Proce
117. er and the minimum and maximum values which can be set for the attribute Hestart Type The type of restart required for a change in value in this attribute to be applied in a running MySQL Cluster The restart type is indicated in this column by an N for a node restart or an S for a system restart Data node attributes The presence of an I in this column indicates that a data node must be restarted using the initial option for a change to take effect Attributes having restart type N can be changed using a rolling restart of the cluster and thus can be changed at any time even if the cluster is running Changing an attribute whose restart type is N requires a complete shutdown of all cluster nodes followed by a restart of the nodes once all of them have been stopped Currently such attributes can be set only before starting a cluster for the first time Table C 1 Management Node Configuration Parameters Name Type Units Default Min Value Max Value Restart Type ArbitrationDelay milliseconds 4G N ArbitrationRank 0 2 1 2 N DataDir path N ExecuteOnComputer name S ExtraSendBufferMem bytes 32G N HeartbeatThreadPriority HostName name or IP address S Id unsigned 1 63 IS LogDestination CONSOLE FILE N SYSLOG FILE filename ndb_hodeid_cluster log maxsize 1000000 maxfiles 6 MaxNoOfSavedEventaunsigned 100 4G N Nodeld unsigned 1 63 IS PortNumber unsigned 1186 64K N PortNumberStats
118. er hosts perform any necessary agent configuration then start the MySQL Cluster Manager agent as described in Chapter 2 MySQL Cluster Manager Installation Configuration Cluster Setup MySQL Cluster Manager agent processes must be running on all hosts where cluster processes are running before proceeding any further MySQL Cluster Manager client session startup Start a MySQL Cluster Manager client session you can connect to a MySQL Cluster Manager agent process running on any of the cluster hosts see Section 2 6 Starting the MySQL Cluster Manager Client Management site definition Define a MySQL Cluster Manager site that includes all hosts in the cluster using the create site command See Section 3 2 1 The create site Command for syntax and other details MySQL Cluster software package registration Register a package referencing the location of the MySQL Cluster software on each cluster host using one or more add package commands see Section 3 3 1 The add package Command Be sure to specify the actual location of the MySQL Cluster software on each host Cluster definition Define a cluster in MySQL Cluster Manager using the create cluster command see Section 3 4 1 The create cluster Command making sure to reference all cluster processes and hosts when doing so 37 Migrating a MySQL Cluster to MySQL Cluster Manager Important AN When creating a cluster MySQL Cluster Manager automatically assigns
119. er screen where you can choose the installation directory The next figure shows the Destination Folder screen with the default location On English language 32 bit Windows systems this is C Program Files MySQL MySQL Cluster Manager 1 1 4 on English 64 bit Windows systems the default is C Program Files x86 MySQL MySOL Cluster Manager 1 1 4 You can click the Change button to change the directory where MySQL Cluster Manager should be installed 14 Installing MySQL Cluster Manager on Windows Platforms im MySQL Cluster Manager 1 1 4 Setup q Zl x Click Next to install to the default folder or dick Change to choose another Instal MySQL Cluster Manager 1 1 4 to Once you have selected the destination directory the installer has gathered all the information that it requires to perform the installation Click Next to continue to the Ready screen shown here 15 Installing MySQL Cluster Manager on Windows Platforms is MySQL Cluster Manager 1 1 4 Setup Ready to install MySQL Cluster Manager 1 1 4 Click Install to begin the installation Click Back to review or change any of your installation settings Click Cancel to exit the wizard Click the Install button to install MySQL Cluster Manager As the installer begins to copy files and perform other tasks affecting the system you may see a warning dialog from Windows User Access Control as shown here 16 Installing MySQL Cluster Manager o
120. erMemory 4M ndbd 2 mysqld 3 Process SendBufferMemory 4M ndbd Pes mysqld 4 Process SendBufferMemory 4M ndbd E3 mysqld 3 Process 4 4 4 4 4 4 4 rows in set 1 63 sec To override this setting for only the connection between the data node with process ID 2 and the mysqld process process ID 4 you can include the process ID in each of the two parts of the process specification as shown here mcm set SendBufferMemory ndbd 2 mysqld 4 8M mycluster2 4 Command result 4 Cluster reconfigured successfully 1 row in set 7 95 sec 86 The reset Command When you check the result using a get command you can see that the new setting applies on the instance level and only to the connection between processes having IDs 2 and 4 the process level setting made previously still applies to the remaining 3 connections mcm get SendBufferMemory mycluster2 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4
121. es manually Keep in mind that if StopOnError is set to 0 the MySQL Cluster Manager agent restarts the data node process automatically if StopOnError is 1 the default then you must execute the start process command manually 3 8 4 The change process Command change process old proc type proc id new proc type cluster name old proc type new proc type ndbd ndbmtd This command is used MySQL Cluster NDB 7 0 and later to change the process type for a given MySQL Cluster process or group of MySQL Cluster processes from one process type o1d process type to another process type new process type Currently the only two process types available for use with this command are ndbd and ndbmtd This means that change process can be used to change the data node process running on one or more data nodes from the single threaded data node daemon ndbd to the multi threaded data node daemon ndbmtd or vice versa This command effectively has no use when managing a MySQL Cluster running MySQL Cluster NDB 6 3 since the multi threaded data node daemon is not available in that version of MySQL Cluster By default change process affects all data nodes running the o7 d process type By specifying an optional process id its action can be restricted to the data node having that process ID For example suppose you have a cluster which is named mycluster and which has two data nodes using ndbd processes as reflected in the output of
122. es the TCP IP port for the client to use This must be the same port that is used by the MySQL Cluster Manager agent As mentioned eslewhere if no agent port is specified in the MySQL Cluster Manager agent configuration file mcmd ini the default number of the port used by the MySQL Cluster Manager agent is 1862 which is also used by default by mcm mcm accepts additional mysq1 client options some of which may possibly be of use for MySQL Cluster Manager client sessions For example the pager option might prove helpful when the output of get contains too many rows to fit in a single screen The prompt option can be used to provide a distinctive prompt to help avoid confusion between multiple client sessions However options not shown in the current manual have not been extensively tested with mcm and so cannot be guaranteed to work correctly or even at all See mysq1 Options for a complete listing and descriptions of all mysql client options causes the output to be formatted vertically This can be helpful when using a terminal whose width is restricted to some number of typically 80 characters See Note R Like the mysql client mcm also supports G as a statement terminator which Chapter 3 MySQL Cluster Manager Client Commands for examples Connecting to the agent using the mysq1 client As mentioned previously mcm actually serves as a wrapper for the mysql client In fact a mysql client from any recent MySQL distribution
123. es to which it applies in the cluster you need only use the name of the attribute as a filter For example to obtain the HostName of all processes in the cluster named mycluster you can execute the command shown here mcm get HostName mycluster 4 4 4 4 4 4 4 4 Name Value Processl Nodeldl Process2 NodeId2 Level Comment 4 4 4 4 4 4 4 4 HostName flundra ndbd a Read only HostName tonfisk ndbd lz Read only HostName grindval ndb_mgmd 49 Read only HostName haj mysqld 50 Read only HostName torsk mysqld S Read only 4 4 4 4 4 4 4 4 5 rows in set 0 04 sec To obtain the value of a given attribute for all processes of a given type you can specify a filter of the form attribute name process type The following command retrieves the Host Name of all ndbd processes only in the cluster mycluster mcm get HostName ndbd mycluster 4 4 4 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4 4 4 HostName flundra ndbd a
124. essfully 1 row in set 6 16 sec If you execute the same get command as shown previously the result is now empty mcm get DataMemory mycluster Empty set 0 74 sec This is because the get command by default does not report default values To retrieve the DataMemory values after resetting them you must invoke get using the include defaults short form d option mcm get include defaults DataMemory mycluster qp 4 4 4 4 4 4p 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4 4 DataMemory 83886080 ndbd 2 Default DataMemory 83886080 ndbd 3 Default 4 4 4 4 4 4 4 2 rows in set 1 21 sec The DataMemory values are now included in the output and are marked with the word Default in the Comment s column Now suppose that the mysqld configuration attribute wait timeout for the mysqld process having the ID 4 in the cluster named mycluster has previously been set to the value 200 as shown here and that no other changes have been to this attribute mcm set wait timeout mysgld 4 200 mycluster Command result qp Cluster re
125. figuration attribute relating to a given process by following these steps for each MySQL Cluster process 70 MySQL Cluster Manager Configuration Commands For each configuration attribute 1 Is an attribute value defined for the node ID of this process Yes Use the value that was defined for this node ID and exit No Proceed to the next step 2 ls an attribute value specified on the process level that is for all processes of this type Yes Use the value that was specified for all processes of this type and exit No Use the default value that applies to processes of this type and exit In the steps just shown exit can be taken to mean If there are more configuration attributes applicable to this process that have not yet been set proceed to the next attribute until there are no more attributes to be set for this process a configuration attribute for a specific process then later specify a process level value for this attribute the process level value is used for all processes of that type Note R The most recently specified value takes precedence This means that if you set including the instance for which you earlier set an instance specific value Mandatory attributes Some attributes must be defined in the MySQL Cluster Manager at the process type or instance level itself cannot be removed entirely Another way of stating this is that a mandatory attribute has no default value An example of a mandatory
126. he agents in a given management site by listing the hosts where they are running with the host s option along with the name of the site to which they belong The result of the following command is to stop MySQL Cluster Manager agents running on hosts kol ja and torsk both of which are members of the management site mysite mcm stop agents hosts kolja torsk mysite Multiple host names following the host s option should be separated by commas with no intervening spaces Invoking stop agents with this option without supplying a site name causes a syntax error Using an undefined site name or names of hosts not belonging to the site with this command also results in an error Note R When IPv6 enabled Windows systems are used as MySQL Cluster hosts under MySQL Cluster Manager you must reference these hosts using IPv4 addresses or as localhost if this is applicable Otherwise MySQL Cluster Manager will be unable to connect to the agent processes on those hosts See Section 4 1 MySQL Cluster Manager Usage and Design Limitations 3 8 MySQL Cluster Manager Process Commands This section contains information about MySQL Cluster Manager client commands used to start and stop MySQL Cluster processes and to determine which processes are currently running 3 8 1 The add process Command add process processhosts process host list set attribute assignment list cluster name process host 11st process namedhost process n
127. he hosts are to be added For example the following command adds two hosts named torsk and kol ja to management site mysite mcm add hosts hosts torsk kolja mysite q4 Command result q4 Hosts added successfully q4 1 row in set 0 48 sec None of the hosts added by this command may already be members of management site site name 57 The list hosts Command It is not currently possible using MySQL Cluster Manager to drop or delete hosts from a management site Note R This command does not support the force option Note R When IPv6 enabled Windows systems are used as MySQL Cluster hosts under MySQL Cluster Manager you must reference these hosts using IPv4 addresses or as localhost if this is applicable Otherwise MySQL Cluster Manager will be unable to connect to the agent processes on those hosts See Section 4 1 MySQL Cluster Manager Usage and Design Limitations 3 2 5 The 1ist hosts Command list hosts site name The 1ist hosts command is used to obtain a list of the hosts comprising a given management site The command requires a single argument the name of the site to be examined For each host listed the information returned includes the hostname availability the Status column and version of the management agent software in use as shown in this example mcm list hosts mysite 4 qp
128. hich is running on Windows The original value for this attribute can be seen using the appropriate get command mcm get tmpdir mycluster q qp q4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 qp 4 4 tmpdir c c50data tmp mysqld 99 4 4 2 qp 4 4p 1 row in set 0 22 sec The correct set command to make the desired configuration change is shown here mcm set tmpdir mysqld 50 c temp node50 mycluster 4 Command result q4 Cluster reconfigured successfully 1 row in set 2 62 sec Note that when you check the value using get even though it was originally shown using backslashes the forward slashes are used when displaying the new value mcm get tmpdir mycluster qp qp qp 4 qp 4 Name Value Processl Idl Process2 Id2 Level Comment qp qp qp 4 4 4 4p tmpdir c temp node50 mysqld SO 4
129. i threaded using change process then verify the change using show status mcm gt start cluster mycluster Command result Cluster started successfully row in set 36 43 sec mcm gt change process ndbd 2 ndbmtd mycluster Command result Process changed successfully nnn row in set 2 min 10 41 sec mcm show status process mycluster p p p p qp NodeId Process Host Status Nodegroup 49 ndb mgmd ilbmeose rodem l ndbmtd tonm rsk rannina nya 2 ndbmtd grindval running n a 20 mysqld haj uum The list processes Command yal mysqld torsk running 593 ndbapi ow running 4 4 4 4 6 rows in set 0 11 sec You can see that it can require much less time to stop the cluster change a data node process and then start the cluster again than it is to change the process while the cluster is running However if you do this the cluster is not available while it is stopped As noted previously change process works only with ndbd and ndbmtd processes attemtpting to use any other process type
130. ified when mysql is invoked Thus you must use the port or P option to connect to the MySQL Cluster Manager agent using the mysql client even if the agent process is using the MySQL Cluster Manager default port and even if the agent process is running on the same host as the mysqi client Unless the correct agent port number is supplied to it on startup mysal is unable to connect to the agent user username Or u username Specifies the username for the user trying to connect Currently the only user permitted to connect is admin this is hard coded into the agent software and cannot be altered by any user By default the mysql client tries to use the name of the current system user on Unix systems and ODBC on Windows so you must supply this option and the username admin when trying to access the MySQL Cluster Manager agent with the mysq1 client otherwise mysql cannot connect to the agent e password password or p password Specifies the password for the user trying to connect If you use the short option form p you must not leave a space between this option and the password If you omit the password value following the password or p option on the command line the mysql client prompts you for one Specifying a password on the command line should be considered insecure It is preferable that you either omit the password when invoking the client then supply it when prompted or put the passw
131. in psuper h localhost P 1862 prompt mcm Adjust the path to the mysq1 exe client executable as necessary to match its location on your system If you save this file to a convenient location such as the Windows desktop you can start a MySQL Cluster Manager client session merely by double clicking the corresponding file icon on the desktop or in Windows Explorer the client session opens in a new cmd exe DOS window 2 7 Setting Up MySQL Clusters with MySQL Cluster Manager This section provides basic information about setting up a new MySQL Cluster with MySQL Cluster Manager It also supplies guidance on migration of an existing MySQL Cluster to MySQL Cluster Manager For more information about obtaining and installing the MySQL Cluster Manager agent and client software see Chapter 2 MySQL Cluster Manager Installation Configuration Cluster Setup See Chapter 3 MySQL Cluster Manager Client Commands for detailed information on the MySQL Cluster Manager client commands shown in this chapter 2 7 1 Creating a MySQL Cluster with MySQL Cluster Manager In this section we discuss the procedure for using MySQL Cluster Manager to create and start a new MySQL Cluster We assume that you have already obtained the MySQL Cluster Manager and MySQL Cluster software and that you are already familiar with installing MySQL Cluster Manager see Chapter 2 MySQL Cluster Manager Installation Configuration Cluster Setup We also assume th
132. inaries in the directory usr 1ocal ndb host 10 on host tonfisk and in the directory usr local ndb host 20 on host 1undra The package named mypackage consists of the MySQL Cluster binaries in the directory usr 1ocal mysql on host tonfisk and in the directory usr local bin mysql on host flundra If you omit the site name argument the command fails with an error as shown here mcm list packages ERROR 6 00MGR Illegal number of operands 3 4 MySQL Cluster Manager Cluster Commands This section contains descriptions of MySQL Cluster Manager commands used to perform operations on clusters These include creating and deleting a cluster starting stopping and restarting a cluster upgrading a cluster that is upgrading the MySQL Cluster software used by a given cluster and listing clusters known to MySQL Cluster Manager 3 4 1 The create cluster Command create cluster package P package name processhosts R process host list cluster name verbose v process host list process_name host process_name host process_name ndb_mgmd ndbd ndbmtd mysqld ndbapi This command creates a cluster to be managed by the MySQL Cluster Manager However it does not start the cluster see Section 3 4 3 The start cluster Command create cluster requires the following arguments A package name supplied as the value of the package option short form P This must be the name of a pack
133. ing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify Laccept the terms in the License Agreement You should read the license text in the text area and when you have done so check the box labelled I accept the terms in the License Agreement Until you have checked the box you cannot complete the MySQL Cluster Manager installation it is possible only to go back to the previous screen print the license or cancel the installation using the buttons labelled Back Print and Cancel respectively Checking the box enables the Next button as shown here 13 Installing MySQL Cluster Manager on Windows Platforms im MySQL Cluster Manager 1 1 4 Setup Please read the following license agreement carefully MySQL Cluster Manager 1 1 Copyright 2010 2012 Oracle and or its affiliates All rights reserved This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify gt V I accept the terms in the License Agreement m m net f a Click the Next button to continue to the Destination Fold
134. initial restart to be changed must be set before the cluster is started for the first time 3 4 6 The upgrade cluster Command upgrade cluster package P Jpackage name cluster name This command upgrades the cluster named cluster name to the software package package name If the cluster is running then upgrade cluster accomplishes this by performing a rolling restart of the cluster The new package must be registered using add package before you can use it for an upgrade otherwise upgrade cluster fails with an error For example suppose mycluster is using MySQL Cluster NDB 7 1 17 and the binaries are registered with a package named 7 1 17 as shown by this 1ist clusters command mcm list clusters mysite 4 4 Cluster Package 4 l mycluster 7 11 17 4 4 1 row in set 1 80 sec Now you wish to upgrade mycluster to MySQL Cluster NDB 7 1 19 Assuming that you have placed the NDB 7 1 19 binaries in the same directory on each host the add package command to create a new package named 7 1 19 that contains these binaries might look something like this mcm add package basedir usr local ndb 7 1 19 7 1 19 4 Command result 4 Package added successfully 4 1 row in set 0 88 sec for the add package command s basedi
135. ion not expressly granted above For more information on the terms of this license or for details on how the MySQL documentation is built and produced please visit MySQL Contact amp Questions For help with using MySQL please visit either the MySQL Forums or MySQL Mailing Lists where you can discuss your issues with other MySQL users For additional documentation on MySQL products including translations of the documentation into other languages and downloadable versions in variety of formats including HTML and PDF formats see the MySQL Documentation Library vi Chapter 1 Overview of MySQL Cluster Manager Table of Contents 1 1 MySQL Cluster Manager Terminology ssssssesseseenenen enne nennen enses enar nns 1 1 2 MySQL Cluster Manager Architecture 2222000000000 eee 400000 eene rtr nnne nnne na 2 This chapter provides a overview of MySQL Cluster Manager as well as its architecture purpose and capabilities 1 1 MySQL Cluster Manager Terminology This section provides definitions of key terms used to describe MySQL Cluster Manager and its components in this manual and in other documentation relating to MySQL Cluster Manager and MySQL Cluster Site A set of hosts on which MySQL Cluster processes to be managed by MySQL Cluster Manager are located A site can include one or more clusters Cluster A MySQL Cluster deployment A cluster consists of a set of MySQL Cluster processes running o
136. is passed as the value of the host s option short form h This is an example of a create site command that creates a site named mysite consisting of the hosts tonfisk and flundra mcm create site hosts tonfisk flundra mysite 4 Command result Site created successfully q4 1 row in set 0 31 sec 55 The delete site Command Tip You can verify that the site was created as intended using the list sites command as shown here mcm list sites 4p 4 Site Port toed Hosts dr rms IIS Imc co cons na q 4p T qp 2 2 1 row in set 0 06 sec See Section 3 2 3 The list sites Command for more information about this command Agents must be running on all hosts specified in the host s option when create site is executed otherwise the command fails with the error Agent on host host port is unavailable The host where the agent used to issue the command is running must be one of the hosts listed Otherwise the command fails with the error Host host name is not a member of site site name A given agent may be a member of one site only if one of the management agents specified in the host list already belongs to a site the command fails with the error Host host is already a member
137. isk flundra mysite ERROR 3 00MGR Illegal syntax Any option value containing one or more whitespace characters one or more dash characters or both must be quoted using single quotation marks Multiple values should be separated by commas only do not insert spaces before or after any of the commas Using spaces before or after the commas in a list of values causes the command to fail with an error as shown here mcm create site hosts tonfisk flundra mysite ERROR 6 00MGR Illegal number of operands As you can see from the examples just shown a MySQL Cluster Manager client command returns a result set just as an SQL statement does in the standard mysq1 client The result set returned by a MySQL Cluster Manager client command consists of one of the following A single row that contains a message indicating the outcome of the command The create site command in the last example returned the result Site created successfully to inform the user that the command succeeded One or more rows listing requested objects or properties An example of such a command is list processes as shown here mcm list processes mycluster p p p NodeId Name fen p p p 49 ndb mgmd flundra 1 ndbd ons 2 ndbd grindval 47 Online Help for MySQL Cluster Manager Commands S mysqld haj S mysqid torsk 52 ndbapi
138. it unknown The MySQL Cluster Manager was unable to determine the cluster s status This may or may not indicate a problem with the cluster it is possible that the problem lies with one or more MySQL Cluster Manager agents or the MySQL Cluster Manager client You should attempt to determine the status of the cluster by other means such as using show status process in the MySQL Cluster Manager client described later in this section or employing one of the commands available in the ndb mgm client see ndb mgm The MySQL Cluster Management Client such as SHOW Or ALL STATUS operation option When the operation option short form o is used it causes SHOW STATUS to display the status of the latest command to be executed This includes commands that were issued using the background option short form bg An example of this command is shown here mcm show status operation mycluster 4 4 p Command Status Description 4 4 4 restart cluster executing lt no message gt 4 4 4 1 row in set 1 60 sec The output contains 3 columns described in the following list Command The text of the command last issued previous to the show status operation command less any options or arguments Status The current state of the command Possible values
139. k A A A A A ko ko ZA kk k Name ndbcluster Value Processl mysqld NodeId1 51 Process2 NodelId2 Level Comment Read only ck ck ck ck ck ck ck ck ck kk AA A ZA Z A ZA kA AAA dS row ck ck ck ck ck ck ck ck ck koc kA A A A AZ A ko ko kA kok ok Name NodeId Value 51 Processl mysqld NodeId1 51 Process2 NodelId2 Level Comment Read only ck ck ck ck ck ck ck ck ck kk kA A AA ko ko kA kock kck ck k KO row A AX ZX ck ck ck ck ck ck AKA AA AA k ko ko kock ko kk Name port Yalues 2307 Processl mysqld NodeId1 51 Process2 NodelId2 Level Comment ck ck ck ck ck ck ck ck ck ck ck ck ck AA ko A kA kA A 1L row ck ck ck ck ck ck ck ck ck ck ok ck ck AA A AA ko ko ko ck ko A AH Name socket Value tmp mysql mycluster 51 sock Processl mysqld NodeId1 51 Process2 NodelId2 Level Comment ck ck ck ck ck ck ck ck ck kk AA A ZA ko A ko ko kA AA ILE row ck ck ck ck ck ck ck ck ck kk kk ko ko A A A ko ko A kc AAA Name tmpdir Value home jon bin mcm mcm data clusters mycluster 51 data tmp Processl mysqld NodeId1 51 Process2 NodelId2 Level 54 MySQL Cluster Manager Site Commands Comment L8 rows in set 0 05 sec mcm Note that you are not returned to the client prompt until the script has finished executing Similarly on Windows you can create a batch file using Notepad or another text editor copy the same get commands as shown previously into it and save it as get attributes bat in a convenient loca
140. kiai 93 3 7 The stop agents Command 212 c2d cose reae eprv osa des Tera reset ad son Gas FUN PRA eu Te rade adu 2 k DIE Fa e IUe 96 3 8 MySQL Cluster Manager Process Commands eee eee ee nennen nnns 96 3 8 1 The add process Combarnd 2 2 022 nedidbd a nona add oddanou aa Id Ra a OE dd ERROR aaa uud 96 3 8 2 The start process Command EEEn NEEE KEE ENA E EENKEER nnne 98 3 8 3 The stop process Command eccirni EAE aq ie coa ee do ade rud CRY E kd ac 99 3 8 4 The change process Command sessi nnne nnne 99 3 8 5 The list processes Command aterert ad eae n ea bo eA e ePi dare ET A se ee PE sees 102 The sections in this chapter describe commands used in the MySQL Cluster Manager 1 1 6 client for tasks such as defining sites packages and MySQL Cluster instances clusters configuring a MySQL Cluster and getting the status of a running MySQL Cluster These commands are issued to the management agent using the mysql client program included with the MySQL Cluster distribution for information about the mysql client not specific to using MySQL Cluster Manager see mysql The MySQL Command Line Tool Each MySQL Cluster Manager client command takes the form shown here instruction options arguments options option Loption L5 option option long name value list option short name value list value list value value 43 arguments argument a
141. l 1 row in set 1 94 sec When used with the cluster option short form c the output of this command consist of two columns The Cluster column contains the name of the cluster The Status column contains a description of the cluster s status possible values and their meanings are shown in the following table Status Value Meaning fully operational All cluster processes are running operational All node groups are up and running but at least one data node process ndbd or ndbmt d is not running The cluster is online but you should determine why any missing data nodes are not running and correct the problem as soon as possible non operational The cluster is not operational because at least one node group is offline You must investigate and fix the problem or problems then restart the 93 The show status Command Status Value Meaning cluster before the cluster can be used for data storage and retrieval operations stopped The cluster is not running because it has been stopped by the user This normally does not indicate any problem as such but you must restart the cluster before it can be used by any applications created The cluster has been created successfully using the create cluster command but has never been started You must start the cluster using the start cluster command before you can make use of
142. l MySQL Cluster Manager 1 1 6 client commands with the exception of add hosts 3 background short form B Rather than waiting for the command to complete the MySQL Cluster Manager client immediately returns the command prompt allowing you to perform addition tasks in the client while that command continues to execute in the background This can be useful when executing commands that might require some time to complete such as starting a cluster with a great many nodes This option is supported by all client commands except for create site delete site add hosts add package and delete package 3 1 Online Help for MySQL Cluster Manager Commands Online help is available in the MySQL Cluster Manager client for MySQL Cluster Manager client commands The client can provide both general and command specific information In addition you can obtain information about mysq1 client commands that are independent of the MySQL server and thus are also available for use when connected to the MySQL Cluster Manager agent Listing MySQL Cluster Manager client commands For a list of all commands with brief descriptions use the list commands command as shown here mcm list commands 48 Online Help for MySQL Cluster Manager Commands COMMANDS add hosts add package add process change process create cluster create site delete cluster delete package delete site get ase illicito illicito illicito illicito Ilisie IHSE
143. l connection between ndbd processes and mysqld processes by using the get command as shown here mcm get d SendBufferMemory mycluster2 Empty set 1 39 sec As noted elsewhere in this manual see Section 3 5 1 The get Command the empty result set is to be expected in this case even when get is invoked using the include defaults or d option because the MySQL Cluster Manager client does not display attributes that appear in the tcp shm or sci sections of the con ig ini configuration file if they have not been explicitly set by the user 3 6 The show status Command show status cluster c cluster name show status operation o cluster name show status process r cluster name This command is used to check the status of clusters cluster processes and commands issued in the MySQL Cluster Manager client The type of status returned depends on which of the three options cluster short form c operation short form o or process short form r is used with the command If none of these is used cluster is assumed These options are described in more detail in the next few paragraphs cluster option When this option is used show status reports on the status of the cluster named cluster name as shown in this example mcm show status cluster mycluster 4 4 Cluster Status 4 4 mycluster fully operationa
144. ld var cdata mycluster 4 Command result 4 Cluster reconfigured successfully 1 row in set 7 66 sec mcm gt get DataDir mycluster mcm get DataDir mycluster 4 qp 4 4 4 4 4 4 Name Value Processl NodeIdl Process2 NodeId2 Level Comment 4 q 4 4 4 4 4 DataDir var cdata ndbmtd di DataDir var cdata ndbmtd 2 DataDir war edata ndo mgmd 49 datadir war edata mysqld 50 datadir vwar edata mysqld Sul 4 4 4 4 4 4 4 4 5 rows in set 0 08 sec As you can see from the get command just shown the attribute assignments were successful and took effect on the process level 83 The sec Command See Case sensitivity behavior for more information about case sensitivity issues in Note R In MySQL Cluster Manager configuration attribute names are not case sensitive MySQL Cluster Manager Similarly you cannot reference multiple process IDs in a single attribute assignment even if they are processes of the same type the following command does not work mcm gt set
145. lic License Version 2 1 February 1999 operate properly or at all without the library tar xvfX lt package tar file gt exclude file where the exclude file contains e g package name lib libglib 2 0 s0 0 1600 6 package name lib libglib 2 0 so 0 package name lib libglib 2 0 so Example tar xvtX mysqgl cluster manager 1 1 1 solarisi0 x96 32bit tar Exclude Exclude File mysql cluster manager 1 1 1 solarisl10 x86 32bit lib libglib 2 0 s0 0 1600 6 mysql cluster manager 1 1 1 solarisl10 x86 32bit lib libglib 2 0 so 0 mysql cluster manager 1 1 1 solarisl10 x86 32bit lib libglib 2 0 so This component is licensed under Section B 2 GNU Lesser General Public License Version 2 1 February 1999 B 2 GNU Lesser General Public License Version 2 1 February 1999 The following applies to all products licensed under the GNU Lesser General Public License Version 2 1 You may not use the identified files except in compliance with the GNU Lesser General Public License Version 2 1 the License You may obtain a copy of the License at http www gnu org licenses lgpl 2 1 html A copy of the license is also reproduced below Unless required by applicable law or agreed to in writing software distributed under the License is distributed on an AS IS BASIS WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND either express or implied See the License for the specific language governing permissions and limitations under the Licen
146. liseconds 1500 10 4G N HeartbeatOrder 65535 S HostName name or IP address localhost S Id unsigned 1 48 IS 126 Name Type Units Default Min Value Max Value Restart Type IndexMemory bytes 18M 1M 1T N InitFragmentLogFiles see values SPARSE IN InitialLogFileGroup see S documentation InitialNoOfOpenFiles files 27 20 4G N InitialTablespace see S documentation lOThreadPool threads 8 4G N LockExecute ThreadT oCPU ID 64K 64K N LockMaintThreadsToUPRU ID 64K 64K N LockPagesInMainMemory 2 N LogLevelCheckpoint log level 15 N LogLevelCongestion levelr 15 N LogLevelConnection integer 15 N LogLevelError integer 15 N LogLevellnfo integer 15 N LogLevelNodeRestart integer 15 N LogLevelShutdown integer 15 N LogLevelStartup integer 1 15 N LogLevelStatistic integer 15 N LongMessageBuffer bytes 1M 512K 4G N MaxAllocate unsigned 32M 1M 1G N MaxBufferedEpochByltbytes 26214400 26214400 4294967039 N 0x01900000 OxFFFFFEFF MaxBufferedEpochs epochs 100 100000 N MaxDMLOperationsPtopenatianBdBD ML 4294967295 32 4294967295 N MaxLCPStartDelay seconds 600 N MaxNoOfAttributes integer 1000 32 4G N MaxNoOfConcurrentlnd egaperations 8K 4G N MaxNoOfConcurrentOi tegons 32K 32 4G N MaxNoOfConcurrentS zbger 256 2 500 N MaxNoOfConcurrentSub lgeeations 256 4G N MaxNoOfConcurrent1 iategartions 4096 32 4G S MaxNoOfFiredTriggernsn
147. localhost if this is applicable Otherwise MySQL Cluster Manager will be unable to connect to the agent processes on those hosts See Section 4 1 MySQL Note R When IPv6 enabled Windows systems are used as MySQL Cluster hosts under Cluster Manager Usage and Design Limitations 3 3 3 The list packages Command list packages package name site name This command lists registered packages It requires a single argument that being the name of the site with which the packages are registered as shown in this example mcm list packages mysite dp O dpm Package l Path Hosts dpe Nerii eS SS SS e SSS SSS SS SS SSS SSS SSS SSS pss SS SS SS SSS SSS yourpackage usr local ndb host 10 tonfisk usr local ndb host 20 flundra mypackage usr local mysql ton isk tlindra dpe jee Ss SS SS SSS SS SS SS SS SS SSS LLL 3S rows an ser m O Sec 61 The list packages Command If tonfisk and flundra are Windows hosts the list of packages might look something like this mcm list packages mysite q Package l R th Hosts 4 4 yourpackage c cluster ndb host 10 tonfisk c cluster ndb host 20 Menara mypackage es mysql tonfisk flundra 4
148. luster Empty set 1 76 sec mcm get include defaults DataMemory ndbd mycluster qp qp qp 4 4 4p 4p Name Value Processl Idl Process2 Id2 Level Comment qp q4 qp 4 q4 4 4p 4p DataMemory 83886080 ndbd Default DataMemory 83886080 ndbd 2 Default 4 4 4 4 qp 4 4 2 rows in set 1 01 sec For more information about these commands see Section 3 5 2 The set Command and Section 3 5 3 The reset Command The get command does not normally display configuration attributes applying to TCP SHM or SCI connections However such attributes can be set in the MySQL Cluster Manager client using the set command and once they have been set they are displayed by applicable get commands See Setting TCP Connection Attributes which provides an example of this 3 5 2 The set Command set attribute_assignment_list cluster_name attribute_assignment_list attribute assignment attribute assignment attribute assignment attribute name process specification process specification value process specification process name process id This command is used to set values for one or more configuration attributes Attributes can be set on either the proces
149. luster defined 1 cluster option show status command 93 cluster processes adding 96 cluster status 93 clusters creating 35 35 63 importing 37 38 38 38 listing 69 migrating to MySQL Cluster Manager 37 see also importing clusters removing 65 restarting 67 starting 66 stopping 67 upgrading 68 command status 94 common terms 1 concurrent client sessions unsupported 103 configuration derivation of attributes 69 configuration attributes 69 defined 2 for TCP connections 85 getting 72 how determined by MySQL Cluster Manager 70 levels applying 70 137 mandatory 71 read only 71 resetting 87 setting 81 configuration commands 69 configuration file 19 configuration parameters see configuration attributes configuration variables see configuration attributes connecting to agent with mcm client 33 with mysql client 33 create cluster command 63 assignment of node IDs in 64 create site command 55 hosts option 56 D DataDir 38 delete cluster command 65 delete package command 60 delete site command 56 deployment example 3 downgrades MySQL Cluster 105 G get command 72 filtering output 77 include defaults option 75 with multiple attributes 78 H help command 55 help for commands 49 help option 49 HostName 38 hosts defined 1 hosts option create site 56 Id node ID 38 40 identifiers 44 case sensitivity 45 spaces in 46 imp
150. mand as shown here mcm list packages mysite qp 4 Package l Path Hosts qp 4 yourpackage usr local ndb host 10 tonfisk usr local ndb host 20 flundra mypackage usr local mysql tonfisk flundra qp q qp For more information about this command see Section 3 3 3 The list packages Command It is possible to assign the same base directory or directories on the same host or hosts to multiple packages as shown in this example in which we assume that hosts tonfisk and flundra have previously been assigned to a site named mysite mcm add package b usr local mysql cluster mypackage Command result 4 Package added successfully q4 row in set 1 41 sec Command result Package added successfully row in set 1 58 sec 4 4 4 Package Path Hosts 4 4 4 mypackage usr local mysql cluster tonfisk flundra yourpackage usr local mysql cluster tonfisk flundra 4
151. med mysite consisting of two hosts named tonfisk and flundra See Section 3 2 1 The create site Command for more information about this command Since we used the long form of the nosts option we were required to use an equals sign to mark the end of the option name and the beginning of the values list You must not insert any space characters before or after the equal sign doing so causes an error as shown here mcm create site hosts grindval haj yoursite ERROR 7 00MGR Option hosts requires a value mcm create site hosts grindval haj yoursite ERROR 7 00MGR Option hosts requires a value The short form of an option does not use an equal sign Instead the value list is separated from the option by a space Using the hn option which is the short form of the host s option the previous create site command can be entered and executed like this mcm create site h tonfisk flundra mysite 4 Command result Site created successfully q4 1 row in set 7 41 sec The short forms of options actually accept multiple spaces between the option name and the values list however a single space is sufficient If you omit the space or try to use an equal sign the command fails with an error as shown here mcm create site htonfisk flundra mysite ERROR 6 00MGR Illegal number of operands mcm create site h tonf
152. more information about this command see Section 3 5 1 The get Command We can see from the entries in the Level column that the DataMemory setting for both ndbd processes applies on the process level A process level setting cannot be reset on the instance level as shown here mcm gt reset DataMemory ndbd 2 mycluster ERROR 6010 00MGR No matching user defined setting was found for config attribute DataMemory mcm reset DataMemory ndbd 3 mycluster ERROR 6010 00MGR No matching user defined setting was found for config attribute DataMemory The following reset command also does not work although you might think that it would do so since it attempts to reset the attribute s value for both n aba processes mcm reset DataMemory ndbd 2 DataMemory ndbd 3 mycluster ERROR 6010 00MGR No matching user defined setting was found for config attribute DataMemory The previous command fails because MySQL Cluster Manager regards this as an attempt to apply two instance level configuration changes Because the Dat aMemory setting is a process level setting you 88 The reset Command must instead reset Dat aMemory to its default value on the process level you can do this by using the filter specification Dat aMemory ndbd in the reset command as shown here mcm reset DataMemory ndbd mycluster 4 Command result 4 Cluster reconfigured succ
153. mysqld mycluster ERROR 6008 00MGR Config attribute HostName is readonly and cannot be changed An attribute that is mandatory or read only is set when a cluster is created Neither a mandatory attribute nor a read only attribute can be reset Neither type of attribute has a default value other than what is set for it when the cluster is created A mandatory attribute can be changed at any time by the user a read only attribute cannot be changed once the cluster has been created You can obtain a listing of mandatory and read only attributes using the get command see Section 3 5 1 The get Command A listing of attribute properties also can be found in the output of ndb config configinfo xml see ndb config Extract MySQL Cluster Configuration Information for more more complete information see Configuration of MySQL Cluster NDB 6 1 7 1 MySQL Cluster Manager determines internally which attributes are considered read only for reasons of cluster stability and performance You can use the get command to see which attributes are read only 3 5 1 The get Command get include defaults d filter specification list cluster name filter specification list filter Spectat ed sem Spec atom filter specification attribute name process specification process specification process specification process name process id This command is used in the MySQL Cluster Manager client to obtain configuration attribute val
154. n Windows Platforms 7 User Account Control O Do you want to allow the following program from an unknown publisher to make changes to this computer Program name X MCM 1 1 4 rele mem 1 1 4 duster 7 2 4 win32 x86 ms Publisher Unknown v show detais If this occurs click the Yes button to allow the installation to continue A Setup Wizard screen with a progress bar is displayed while the installer runs as shown in the next figure 17 Installing MySQL Cluster Manager on Windows Platforms jis MySQL Cluster Manager 1 1 4 Setup Ic x Installing MySQL Cluster Manager 1 1 4 Please wait while the Setup Wizard installs MySQL Cluster Manager 1 1 4 Status Generating script operations for action The Setup Wizard may require several minutes to copy all of the necessary files for MySQL Cluster Manager 1 1 6 and MySQL Cluster NDB 7 2 4 to the installation directory and to perform other required changes Note E The MySQL Cluster Manager 1 1 6 installer places MySQL Cluster NDB 7 2 4 in the cluster directory under the installation directory By default this is C Program Files MySQL MySQOL Cluster Manager 1 1 4Ncluster Or C Program Files x86 MMySQLMMySQL Cluster Manager 1 1 4 cluster The location of the MySQL Cluster binaries is not separately configurable using the MySQL Cluster Manager installer When the Setup Wizard finishes the installer displays the Installation Completed s
155. n one or more hosts A minimal cluster is usually considered to include one management node two data nodes and one SQL node A typical production cluster may have one or two management nodes several SQL nodes and 4 or more data nodes The exact numbers of data and SQL nodes can vary according to data size type and rating of hardware used on the hosts expected throughput network characteristics and other factors the particulars are beyond the scope of this document and you should consult MySQL Cluster NDB 6 1 7 1 for more specific information and guidelines Host A computer The exact meaning depends on the context A computer where one or more MySQL Cluster processes are run In this context we sometimes refer more specifically to a cluster host The number of cluster processes and number of cluster hosts may be but are not necessarily the same A computer where an instance of the MySQL Cluster Manager agent runs In order to run a MySQL Cluster using MySQL Cluster Manager the MySQL Cluster Manager agent must be running on each host where cluster processes are to be run In other words when using MySQL Cluster Manager all cluster hosts must also be MySQL Cluster Manager agent hosts although the reverse is not necessarily true Therefore you should understand that anytime we use the term host we are referring to a host computer in both of the senses just given Process In the context of MySQL Cluster a process more s
156. n other words it means the Host Name for all processes and the DataDir for ndbd processes Suppose you wish to obtain the values for Host Name for just the ndb mgmd and mysqld processes in mycluster You might be tempted to try using something like HostName ndb_mgma mysqld for the filter list but this does not work as you can see here mcm gt get HostName ndb mgmd mysgld mycluster ERROR 6003 00MGR No such config variable mysqld for process This is due to the fact that each filter in the filter list must be a valid filter and must include an attribute name In the filter list just shown MySQL Cluster Manager tries to interpret the first string following the comma as an attribute name The correct filter list to use in a get command for retrieving the HostName for the ndb mgmd and mysqld processes in mycluster is shown in this example mcm get HostName ndb mgmd HostName mysqld mycluster 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4 HostName grindval ndb mgmd 49 Read only HostName haj mysqld 59 Read only HostName torsk mysqld SU Read only 4
157. n this notice the name of the X Consortium shall not be used in advertising or otherwise to promote the sale use or other dealings in this Software without prior written authorization from the X Consortium FSF changes to this file are in the public domain Copyright 1996 2007 Free Software Foundation Inc Taken from GNU libtool 2001 Originally by Gordon Matzigkeit lt gord gnu ai mit edu gt 1996 This file is free software the Free Software Foundation gives unlimited permission to copy and or distribute it with or without modifications as long as this notice is preserved You are receiving a copy of the libintl library The terms of the Oracle license do NOT apply to the libintl library it is licensed under the following license separately from the Oracle programs you receive If you do not wish to install this program you may create an exclude file and run tar with the X option This component is licensed under Section B 2 GNU Lesser General Public License Version 2 1 February 1999 B 5 LPeg Library License The following software may be included in this product LPeg Use of any of this software is governed by the terms of the license below Copyright 2008 Lua org PUC RiIO 120 Lua liblua License Permission is hereby granted free of charge to any person obtaining a copy of this software and associated documentation files the Software to deal in he Software without restriction including without
158. nager Package Commands eee enne nnne 58 3 3 1 The add package Combmand 2 5 2 enki ode evan red ot a ea DR ep Tr oaa e Rv eM aor o dd 58 3 3 2 The delete package Command ssessssssessssseeee nennen enne sn th nn nn 60 3 3 3 The List packages Command occorrens esed oe vnd ranae avv we aa ra ELA d Y FE Tad RR TAa Y UTE 61 3 4 MySQL Cluster Manager Cluster Commands eee eee eee nnne nnns 63 3 4 1 The create cluster Command 2 2 2000000000000 eee ana sr nass assa ns 63 3 4 2 The delete cluster Command 2 0000 sni estais ssa a nsa sns ssa ns 65 3 4 3 The stave cluster Command tetas t cere o nep sene ona Paese ooa E EEEa 66 3 4 4 The stop cluster Command 2 00 0000000000000 00 000000000 A nan EENEN TEREA 67 3 4 5 The restart cluster Command 220200200 a erii ansa sas Emit 67 3 4 6 The upgrade cluster Command orreri e iNi eee 68 347 The list Clusters Command elles tro epe a a aa EO davs DU KEEA 69 3 5 MySQL Cluster Manager Configuration Commands sss eene 69 3 5 l The get Command T 72 3 0 2 The set uut P 81 3 5 3 The peset COImdaLrdaci osse erede nay cena pra epe dp e e nu YR REP EAEYR FO uER YR RE day wA WR RET a YER UR 87 3 6 The show Status Command 4 5 teneor bake REN ue Fk eeu vada rri aun dan ons ERI REEL
159. nature of Ty Coon 3 April 1990 Ty Coon President of Vice mase Ve Cu thence sto dell B 3 libevent License The following software may be included in this product libevent Copyright c 2000 2007 Niels Provos lt provos citi umich edu gt All rights reserved Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are met 1 Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution 3 The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE AUTHOR AS IS AND ANY EXPRESS OR MPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED N NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT INDIRECT NCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING
160. ndBufferMem bytes 256K 4G N wan false N Table C 4 MySQL Server Option and Variable Reference for MySQL Cluster Name Cmd Line Optionfile System Var Status Var Var Scope Dynamic Com show ndb status Yes Both No Handler discover Yes Both No have ndbcluster Yes Global No Ndb api bytes received count Yes Global No Ndb api bytes received count session Yes Session No 129 Name Cmd Line Option file System Var Status Var Var Scope Dynamic Ndb api bytes received count slave Yes Global No Ndb api bytes seht count Yes Global No Ndb api bytes sent count session Yes Session No Ndb api bytes sent count slave Yes Global No Ndb api event bytes count Yes Global No Ndb api event byles count injector Yes Global No Ndb api event data count Yes Global No Ndb api event data count injector Yes Global No Ndb api event nondata count Yes Global No Ndb api event nondata count injector Yes Global No Ndb api pk op count Yes Global No Ndb api pk op count session Yes Session No Ndb api pk op count slave Yes Global No Ndb api pruned scan count Yes Global No Ndb api pruned scan count se sion Yes Session No Ndb api pruned scan count slave Yes Global No Ndb api range scan count Yes Global No Ndb api range scan count session Yes Session No Ndb api range
161. necting to the MySQL Cluster Manager agent MySQL Cluster Manager 1 1 6 includes a command line client mcm located in the installation bin directory mcm can be invoked with any one of the options shown in the following table Long form Short form Description help Display mcm client options version V Shows MySQL Cluster Manager agent client version W Shows MySQL Cluster Manager agent client version with version of mysql used by mcm address a Host and optional port to use when connecting to mcmd in host port format defaultis 127 0 0 1 1862 mysgl help I Show help for mysal client see following The client server protocol used by MySQL Cluster Manager is platform independent You can connect to any MySQL Cluster Manager agent with an mcm client on any platform where it is available This means 32 Starting the MySQL Cluster Manager Client for example that you can use an mcm client on Microsoft Windows to connect to a MySQL Cluster Manager agent that is running on a Linux host mcm actually acts as a wrapper for the mysql client that is included with the bundled MySQL Cluster distribution Invoking mcm with no options specified is equivalent to the following ehnell gt mysql uadmin psuper nm I27 0 0 1 P 1862 These u and p options and values are hard coded and cannot be changed This means that you can use the mysal client to run MySQL Cluster Manager client sessions on
162. ng get command mcm get DataMemory mycluster qp T qp 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment qp Tp qp 4 4 4 qp 4p DataMemory 500M ndbd il Process DataMemory 500M ndbd 2 Process 4 4 4 4 4 4 2 rows in set 0 79 sec Note E For more information about this command see Section 3 5 1 The get Command To set an attribute for a specific process instance include the process ID in the attribute assignment the form of such an attribute assignment is attribute name process nameiprocess id value For example to set the wait timeout attribute for the mysqld process that has process ID 50 to 200 you would issue a set command that contains the attribute assignment wait timeout mysqid 51 200 like this mcm set wait timeout mysgld 50 200 mycluster q4 Command result 4 Cluster reconfigured successfully 1 row in set 6 18 sec You can verify that the setting has taken effect using an applicable get command mcm get wait timeout mycluster qp qp q4 4 4
163. nt options A MySQL Cluster Manager client command option is always employed as part of a MySQL Cluster Manager client command it is not passed to the mysql client when invoking it In addition you cannot issue queries or other SQL statements in the MySQL Cluster Manager client These are not recognized by the client and are rejected with an error The converse of this is also true MySQL Cluster Manager client commands are not recognized by the standard mysql client The instruction just shown takes the argument mysite The argument is usually an identifier that names the object to be effected in this case the command deletes the site whose name matches the argument For more information see Section 3 2 1 The create site Command Changes in client commands in version 1 1 6 An additional verbose option has been added in MySQL Cluster Manager 1 1 6 to the create cluster and add process commands In both cases using the option causes the command to return a list of the MySQL Cluster processes affected by the command this includes their node IDs process types and the hosts where they are located For additional information and examples see Section 3 4 1 The create cluster Command and Section 3 8 1 The add process Command MySQL Cluster Manager identifiers A legal MySQL Cluster Manager identifier consists of any sequence of characters from among the following The letters a through z and A through z The digits 0 th
164. ntinuing MySQL Cluster Manager mysqld attributes and MySQL user variables MySQL user variables are not accessible as MySQL Cluster Manager configuration attributes 4 3 MySQL Cluster Manager Limitations Relating to MySQL Cluster This section describes limitations relating to MySQL Cluster functionality that is unsupported or curtailed by MySQL Cluster Manager 1 1 6 MySQL Cluster Manager and replication 104 Syntax and Related Issues in MySQL Cluster Manager MySQL Cluster Manager currently does not provide any explicit support for MySQL Cluster Replication However you should still be able to perform manual setup of replication of a MySQL Cluster that is managed by MySQL Cluster Manager Backup and restore operations MySQL Cluster Manager does not currently provide any integrated backup or restore functionality You can back up NDB databases and tables using the ndb mgm client START BACKUP command and restore them using the ndb restore program Both of these programs are supplied with the MySQL Cluster distribution For more information see Online Backup of MySQL Cluster and ndo restore Restore a MySQL Cluster Backup Because of this configuration attribute changes which require a system initial restart currently cannot be made using MySQL Cluster Manager after a cluster is started for the first time since this type of restart removes all cluster data and thus requires a complete backup and restore of the cluster Fo
165. ntroduced by others Finally software patents pose a constant threat to the existence of any free program We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder Therefore we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license Most GNU software including some libraries is covered by the ordinary GNU General Public License This license the GNU Lesser General Public License applies to certain designated libraries and is quite different from the ordinary General Public License We use this license for certain libraries in order to permit linking those libraries into non free programs When a program is linked with a library whether statically or using a shared library the combination of the two is legally speaking a combined work a derivative of the original library The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom The Lesser General Public License permits more lax criteria for linking other code with the library We call this license the Lesser General Public License because it does Less to protect the user s freedom than the ordinary General Public License It also provides other free software developers Less of an advantage over competing non free programs These disadvant
166. ny portion of this section is held invalid or unenforceable under any particular circumstance the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system it is up to the author donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License 12 If the distribution and or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries so that distribution is permitted only in or among countries not thus excluded In such case this License incorporates the limitation as if written in the body of this License 13 The Free Software Foundation may publish revised
167. o creating starting and stopping clusters obtaining cluster and cluster process status reports getting cluster configuration information and setting cluster configuration attributes 1 2 MySQL Cluster Manager Architecture This section provides an architectural overview of MySQL Cluster Manager its components and their deployment MySQL Cluster Manager is a distributed client server application consisting of two main components The MySQL Cluster Manager agent is a set of one or more agent processes that manage MySQL cluster nodes and the MySQL Cluster Manager client provides a command line interface to the agent s management functions Agent The MySQL Cluster Manager agent is comprised of the set of all MySQL Cluster Manager agent processes running on the hosts making up a given management site A MySQL Cluster Manager agent process is a daemon process which runs on each host to be used in the cluster In MySQL Cluster Manager there is no single central server or process all agents collaborate in managing a cluster as a whole This means that any connected agent can be used to carry out tasks that effect the entire cluster Each agent process is responsible for managing the MySQL Cluster nodes running on the host where the agent is located MySQL Cluster management and SQL nodes are managed directly by the MySQL Cluster Manager agent cluster data nodes are managed indirectly using the cluster management nodes Management responsi
168. o disable condition pushdown in the indicated mysqld process but if you invoke the mysqld executable from a system prompt using Engine Condition Pushdown 0 mysqld fails to start In this manual for easy recognition we show configuration attribute names as having the same lettercase used in other MySQL documentation thus we always refer to DataMemory rather than datamemory Or DATAMEMORY and engine condition pushdown rather than Engine Condition Pushdown or ENGINE CONDITION PUSHDOWN While you are not required to do this when using MySQL Cluster Manager we suggest that you also follow this convention 45 Note R Values that contain space characters must be quoted using single quote characters For example if you wish to define a package named mypackage for a site named mysite using usr local mysql cluster 7 1 where a space occurs between mysql and cluster as the path to the base directory on all hosts the correct command would be add package basedir usr local mysql cluster 7 1 mypackage To decrease the possibility of errors in reading and entering MySQL Cluster Manager commands we recommend avoiding the use of space characters whenever possible Each command must end with a terminator character By default this is the semicolon character However the sequences g and G are also supported as command terminators The G terminator causes the output to be vertically formatted the sam
169. old where to find its configuration file using the defaults file option Both of these paths must be absolute Important AN Installation of the MySQL Cluster Manager agent as a service is recommended However you Soulg not install MySQL Cluster processes ndb mgmd exe ndbd exe ndbmtd exe mysgld exe as services on Windows hosts to be used as MySQL Cluster n nodes under management by MySQL Cluster Manager since the MySQL Cluster Manager agent itself controls MySQL Cluster nodes independently of the Windows Service Manager Assume that youn have installed ados oid Manager to the default location for 64 bit Windows systems C P1 x8 ySQL MySQL Cluster Manager 1 1 4N C Program F on 32 bit Windows systems and that its Files MyS configuration file i is located ir in c es 1 1 4 etc Then the io oWilge Con natalie MySQL Cluster Manager as a service named mcm with the display name MySQL Cluster Manager 1 1 6 5 Mx COT NMSrzCGOT jatar Nagwer x86 MySQL MySQL Cluster Manager SC CreateService SUCCESS Cg This command can be quite long For enhanced legibility we have broken it across several lines but you should always enter it on a single line allowing it to wrap naturally similar to what is shown here Microsoft Windows Version 6 1 7601 Copyright c 2009 Microsoft Corporation ALL rights reserved C Windows systems 7 gt 50 CREATE MEM DisplayHame MySQL Cluster Manager tart
170. on short form h is used with this command the base directory settings for the host or hosts named by the option are removed as well All hosts given in the host list must be members of the site to which the package is registered Otherwise the command fails A package that is in use by a cluster cannot be unregistered the cluster must first be deleted see Section 3 4 2 The delete cluster Command Here is an example that demonstrates how to unregister a package named mypackage mcm gt delete package mypackage 4 Command result 4 Package deleted successfully 1 row in set 1 23 sec You can also verify that the package was unregistered using the list packages command the package name should no longer appear in the output of this command see Section 3 3 3 The 1ist packages Command If you attempt to use the unregistered package in a create cluster command the command fails as shown here mcm create cluster package mypackage gt processhosts ndb_mgmd tonfisk ndbd grindval ndbd flundra mysqld tonfisk mycluster ERROR 4001 00MGR Package mypackage not defined An upgrade cluster command that references an unregistered package also fails see Section 3 4 6 The upgrade cluster Command for more information MySQL Cluster Manager you must reference these hosts using IPv4 addresses or as
171. ord in a startup script or configuration file Currently the password is hard coded as super and cannot be changed or overridden by MySQL Cluster Manager users Therefore if you do not include the password or p option when invoking mysql it cannot connect to the agent In addition you can use the prompt option to set the mysq1 client s prompt This is recommended since allowing the default prompt mysql gt to be used could lead to confusion between a MySQL Cluster Manager client session and a MySQL client session Thus you can connect to a MySQL Cluster Manager agent by invoking the mysq1 client on the same machine from the system shell in a manner similar to what is shown here shell mysql h127 0 0 1 P1862 uadmin p prompt mcm 34 Setting Up MySQL Clusters with MySQL Cluster Manager For convenience on systems where mcm itself is not available you might even want to put this invocation in a startup script On a Linux or similar system this script might be named mcm client sh with contents similar to what is shown here bin sh usr local mysgl bin mysgl h127 0 0 1 P1862 uadmin p prompt mcm In this case you could then start up a MySQL Cluster Manager client session using something like this in the system shell shell mcm client On Windows you can create a batch file with a name such as mcm client bat containing something like this C mysql bin mysql exe uadm
172. ork that uses the library The former contains code derived from the library whereas the latter must be combined with the library in order to run GNU LESSER GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING DISTRIBUTION AND MODIFICATION 0 This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License also called this License Each licensee is addressed as you A library means a collection of software functions and or data prepared so as to be conveniently linked with application programs which use some of those functions and data to form executables The Library below refers to any such software library or work which has been distributed under these terms A work based on the Library means either the Library or any derivative work under copyright law that is to say a work containing the Library or a portion of it either verbatim or with modifications and or translated straightforwardly into another language Hereinafter translation is included without limitation in the term modification Source code for a work means the preferred form of the work for making modifications to it For a library complete source code means all the source code for all modules it contains plus any associated interface definition files plus the scripts used
173. orm r is used with show status the output contains 5 columns described in the following list Id This is the node ID of the process as a node in cluster cluster name e Process The type of process that is the name of the corresponding MySQL Cluster executable Allowed values are ndb mgmd ndbd ndbmtd and mysqld Host The hostname or IP address of the computer where the process is running Status The state or condition of this process Possible values for this column are given later in this section e Nodegroup lfthe Process is ndbd or ndbmt d that is if the process is a data node process then this column shows the ID of the node group to which the process belongs For any other value of Process this column is empty Possible values for the Status column are shown in the following table together with a description of what this value represents Status Value Meaning running The process is running normally stopped The process has been stopped by the user added The process has been added to the cluster but not yet started starting The process has been started but is not yet fully running For data nodes you can determine which start phase the node is currently in by using the status command in the ndb mgm client stopping The process has received a command to stop and is now shutting down failed The process has shut down unexpectedly likely to have crashed You should determine
174. ormation management applications It is not developed or intended for use in any inherently dangerous applications including applications which may create a risk of personal injury If you use this software in dangerous applications then you shall be responsible to take all appropriate fail safe backup redundancy and other measures to ensure the safe use of this software Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications Legal Notices Oracle is a registered trademark of Oracle Corporation and or its affiliates MySQL is a trademark of Oracle Corporation and or its affiliates and shall not be used without Oracle s express written authorization Other names may be trademarks of their respective owners This software and documentation may provide access to or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services Oracle Corporation and its affiliates will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services This document in any form software or printed matter contains proprietary information that is the exclusive property of Oracle Your access to and use of this material is subject to the terms
175. orting clusters 37 and configuration 38 and data directories 38 and host names 38 and Node IDs 38 and node IDs 38 40 restarting under MySQL Cluster Manager 39 include defaults option get command 75 installation 5 IPv6 and hostnames Windows 103 L license keys 22 and operating platform 103 limitations 103 background option 105 backup 105 105 change process command 103 client 104 104 104 104 cluster upgrades and downgrades 105 concurrent usage 103 IPv6 103 license keys 103 MySQL server variables 104 104 MySQL user variables 104 operating systems 103 relating to MySQL Server 103 replication 105 restarts 105 syntax 105 Windows 103 list clusters command 69 list commands command 48 list hosts command 58 list processes command 102 list sites command 57 M management site defined 1 management sites adding hosts 57 creating 55 deleting 56 listing 57 listing hosts 58 mcm client and mysq client 32 memd 22 mcmd exe 24 migrating clusters to MySQL Cluster Manager 37 see also importing clusters multiple client sessions 103 mysql client commands 50 mysql cluster manager OBSOLETE see mcmd 22 mysqld options 104 N node IDs and create cluster command 64 138 O obtaining MySQL Cluster Manager 5 operation option show status command 94 P packages defined 2 listing 58 61 registering 58 removing 60 process option show status command
176. ostName Value tonfisk Processi ndbd NodeId1 1 Process NodelId2 Level 51 Online Help for MySQL Cluster Manager Commands Comment Read only ck ck ck ck ck ck A A A A A A A A 4 ck ck ck ko kc k kk kk S row ck ck ck ck ok ck ko AA A A A A A 4 4 4 444444444 Name NodeId Value 1 Processi ndbd NodeId1 1 Process2 NodelId2 Level Comment Read only KKKKKKKKKKKKKKKKKKKKKKKKKKK ko row ck ck ck ck ck AAA A A A ck ck ck ck ko 4 kk kk kk kk Name DataDir Value home jon bin mcm mcm data clusters mycluster 2 data Processi ndbd NodeId1 2 Process2 NodelId2 Level Comment KKKKKKKKKKKKKKKKKKKKKKKKKKK A row ck ck ck ck ck AAA A A A A ck ck ck ck kk k kk kk kk Name HostName Value grindval Processi ndbd NodeId1 2 Process2 NodeId2 Level Comment Read only ck ck ck ck ck ck ck A A A A A A A AAA A AAA A kk kx 6 row KKKKKKKKKKKKKKKKKKKKKKKKKKK Name NodeId Value 2 Processi ndbd NodeId1 2 Process2 NodelId2 Level Comment Read only 6 rows in mcm get set 0 10 sec mysgld mycluster G ck ck ck ck ck ck ck A A A A A A A AAA AA kk kk kA kx dle row KKKKKKKKKKKKKKKKKKKKKKKKKKK Name Value Processl NodelIdl Process2 Nodeld2 Level Comment datadir home jon bin mcm mcm data clusters mycluster 50 data mysqid 50 ck ck ck ck ck ck ck A A A A A A ck ck ck ck ck ck kk kk kA De row KKKKKKKKKKKKKKKKKKKKKKKKKKK Name Value Processl NodeId1 Process2 NodelId2 Level Comm
177. ostis host gt Ahose gt Valid options Dacko B Run command in background to the user immediately Comma separated list of hostnames HORM hosts hosti estos and return prompt OSS li in set 0 00 sec For any MySQL Cluster Manager client command the he1p option may be abbreviated to 49 Online Help for MySQL Cluster Manager Commands mcm list processes list processes lt sitename gt Lists all processes defined in the specified cluster 4 rows in set 0 00 sec As mentioned elsewhere in this manual see Chapter 3 MySQL Cluster Manager Client Commands many other MySQL Cluster Manager command options have short forms as well These are included in the documentation for each command You can also find out what these are for a given command by invoking it with the help or option mysql client commands in the MySQL Cluster Manager client You can also use most standard mysql client commands in the MySQL Cluster Manager client but not SQL statements which depend on being connected to a MySQL server such as prompt quit and status For example the output of the status command when connected to the MySQL Cluster Manager agent looks something like this depending on the exact version of the client and agent which you are using and possibly other factors mcm status home jon bin mcm bin mysql Ver 14 14 Distrib 5 5 19 ndb 7 2 4 for linux2 6 x86 64 using EditLine
178. pass word This account is created with all privileges on the MySQL server including the granting of privileges In other words it is created using GRANT ALL PRIVILEGES ON WITH GRANT OPTION Note E The existing MySQL root account is not altered and the test database is preserved License files License keys were required for early MySQL Cluster Manager releases They are not needed in order to use MySQL Cluster Manager version 1 1 6 MySQL Cluster Manager agent repositories manager directory The manager directory contains MySQL Cluster Manager data files as well as a rep directory in MySQL Cluster data files for each MySQL Cluster under MySQL Cluster Manager control are kept Normally there is no need to interact with these directories beyond specifying the location of the manager directory in the agent configuration file mcmd ini However in the event that an agent reaches an inconsistent state it is possible to delete the contents of the rep directory in which case the agent attempts to recover its repository from another agent Important AN In such cases you must also delete the checksum file repchk sum from the manager directory Otherwise the agent reads this file and raises a checksum error due to the now empty rep directory A minimal agent configuration file as used in production might look like this memd plugins manager manager port 1862 log file mcmd log log level message log file and log lev
179. pecifically a cluster process is a MySQL Cluster node of one of the following 3 types management node ndb mgmd data node ndbd or ndbmtd or SQL node mysqld For more information about these node types and their functions in a cluster see MySQL Cluster Core Concepts and MySQL Cluster Nodes Node Groups Replicas and Partitions Package MySQL Cluster Manager Architecture A copy of the MySQL cluster software This should include the binary executables needed to run the cluster processes of the desired types on a given host The simplest way to make sure that this is done is to place a copy of the entire MySQL Cluster distribution on each computer that you intend to use as a cluster host Configuration attribute A value whose setting affects cluster operations in a clearly defined and measurable way When running MySQL Cluster manually configuration is accomplished using cluster configuration parameters MySQL server options and MySQL system and status variables MySQL Cluster Manager masks the differences between these provides a unified view of them see Configuration attributes for more information Agent A MySQL Cluster Manager process that runs on each cluster host responsible for managing the cluster processes running on that host Client The MySQL Cluster Manager client is a software application that allows a user to connect to MySQL Cluster Manager and perform administrative tasks such as but not limited t
180. ption modifier support MySQL Cluster Manager does not recognize the 1oo0se maximum nable and disable prefixes for mysqld options used as MySQL Cluster Manager configuration attributes for a description of these modifiers see Program Option Modifiers For example the command set 1oose skip innodb mysqld true mycluster fails with the error No such config variable loose skip innodb for process mysqld The skip option modifier is supported in some but not all cases so that commands such as set Skip innodb mysqld true mycluster and set skip grant tables mysqld true mycluster can be used with MySQL Cluster Manager while set skip column names mysqld true mycluster cannot Bug 48559 Bug 47779 Visibility of MySQL Cluster Manager mysqld attributes and MySQL server variables Due in part to issues with mappings between my cnf option names mysqld command line option names and names of MySQL server variables some MySQL server variables are not visible to MySQL Cluster Manager or have different names For example the storage engine server variable shown in the output of SHOW VARIABLES in the mysql client maps to the default storage engine configuration attribute used in the MySQL Cluster Manager get and set commands Dashes and underscores in MySQL option and variable names When using the mysql client or other MySQL client applications many MySQL system options and variables can be named using either dashes or unders
181. quired to follow this convention if you do not wish to do so however since the corresponding executables are named and must be invoked in lowercase we suggest that you use lowercase Configuration attribute names are case insensitive For example either of the commands get include defaults DataMemory ndbd mycluster orget include defaults datamemory ndbd mycluster returns the data memory allocated for each ndbd process in the cluster named mycluster either of the commands set engine condition pushdown mysqld 4 0 myclusterOrset Engine Condition Pushdown mysgld 4 0 mycluster disables the condition pushdown optimization in the mysqld process having the node ID 4 in the MySQL Cluster named mycluster Note R Configuration attributes in the MySQL Cluster Manager derive from two different sources MySQL Cluster configuration parameters and MySQL Server options MySQL Cluster configuration parameters are case insensitive but their canonical forms use upper camelcase that is medial capitalization including the first letter This means that whether you set a value for data memory using the MySQL Cluster Manager client or in the config ini file you can refer to it as DataMemory datamemory Or dATAmEMORY without any negative impact However MySQL Server command line options are case sensitive and use only lowercase This means that for example set Engine Condition Pushdown mysqld 4 0 mycluster in the MySQL Cluster Manager client works t
182. r MySQL Server as described here 38 Migrating a MySQL Cluster to MySQL Cluster Manager For a management node or data node MySQL Cluster uses the process working directory as the DataDirectory Which means that if the DataDirectory was not set explicitly to an absolute path in the original cluster s con ig ini file the arguments with which which the cluster executable was invoked and the location it was started from may also affect this value For a mysqid processes the default location of the data directory depends on the method that was used to install the mysqid binary see Installation Layouts for more information this value can also be overridden from the command line or in the mysqld s my cnf file Due to these many factors which can affect the locations of the nodes data directories you should always verify the true location of the original data directory for each node in the original cluster by inspection of the file system then set DataDirectory using MySQL Cluster Manager for each node in the new cluster explicitly Fora config ini setting that applies to a single process of type process type and having node ID node id you can use the following regular expression to generate a set statement that applies the same setting to the same cluster process S Nw Ns 2Ns Nw set 1 process name node id 2 Cluster shutdown and startup Once you have finished migrating the cluster configuration data you are read
183. r information about restart types required for individual configuration attributes see Appendix C Attribute Summary Tables Note R Backups of tables using storage engines other than NDB as well as of all other database objects which are not tables must be made using some other method such as mysqldump See mysqldump A Database Backup Program Rolling restarts Currently all cluster nodes must be running in order to perform a rolling restart using MySQL Cluster Manager However MySQL Cluster itself requires only that at least one management server and all data nodes are running in other words any mysqld processes and any additional ndb mgmd processes can be stopped In such cases you can perform the rolling restart manually after stopping the MySQL Cluster Manager agent When making changes in configuration attributes only those nodes requiring a restart to make the change take effect are actually restarted ndbapi nodes are never restarted by MySQL Cluster Manager Cluster upgrades and downgrades Not all upgrades and downgrades between different versions of MySQL Cluster are supported This is not an issue with MySQL Cluster Manager but rather a limitation in the MySQL Cluster software For information on supported online upgrades and downgrades see Upgrading and Downgrading MySQL Cluster 4 4 Syntax and Related Issues in MySQL Cluster Manager This section covers MySQL Cluster Manager issues relating to limitations in
184. r option with forward slashes See Section 3 3 1 The add package Command for additional information and Note R On Windows you must replace any backslash characters in the path used examples Both packages should now be listed in the output of the command 1ist packages mysite To perform the upgrade to the 7 1 19 package use the upgrade cluster command as shown here 68 The list clusters Command mcm upgrade cluster package 7 1 19 mycluster 4p Command result 4 Cluster upgraded successfully 4 1 row in set 3 min 17 00 sec Once the upgrade cluster command has been successfully executed you can verify that mycluster is now using the 7 1 19 package from the output of the appropriate List clusters command mcm gt list clusters mysite 4 Cluster Package p 4 myclaster 1 119 4 4 1 row in set 1 80 sec Despite the name of this command upgrade cluster can also be used to perform MySQL Cluster downgrades MySQL Cluster Manager does not allow cluster upgrades or downgrades not supported by MySQL Cluster Before attempting any upgrade or downgrade using the upgrade cluster command be sure to consult Upgrading and Downgrading MySQL Cluster to determine whether MySQL Cluster supports the
185. r this command to succeed For information about how to determine the operation state of the cluster see Section 3 6 The show status Command For example the command shown here performs a rolling restart of the cluster named mycluster mcm restart cluster mycluster 4 Command result Cluster restarted successfully 1 row in set 1 min 22 53 sec If the cluster is not already running restart cluster fails with an error as shown here mcm show status cluster mycluster p 4 Cluster Scans 1 row in set 1 49 sec 67 The upgrade cluster Command mcm restart cluster mycluster ERROR 5009 00MGR Restart can not be performed as processes are stopped in cluster mycluster Note R Depending on the number of nodes and the amount of data stored in the cluster a rolling restart can take a considerable amount of time up to several hours for a cluster with a great many data nodes and a large amount of data For this reason you may want to execute this command with the background option short form B to allow it to run in the background freeing the MySQL Cluster Manager client for other tasks Currently there is no mechanism in MySQL Cluster Manager for performing system initial restarts of a cluster This means that attributes that require an
186. rates the NDB storage engine for high availability and data redundancy in a distributed computing environment This manual does contain certain basic information about MySQL and MySQL Cluster however it is not in any way intended as an exhaustive reference for either of these products Current versions of MySQL Cluster compatible with MySQL Cluster Manager are based on MySQL Server 5 1 and versions 6 3 7 0 and 7 1 of the NDB storage engine these versions of MySQL Cluster are known as MySQL Cluster NDB 6 3 MySQL Cluster NDB 7 0 and MySQL Cluster NDB 7 1 For complete information about MySQL 5 1 please refer to the MySQL 5 1 Manual which also includes information specific to MySQL Cluster NDB 6 3 and later MySQL Cluster versions see MySQL Cluster NDB 6 1 7 1 If you do not have the MySQL and MySQL Cluster documentation this documentation can be obtained free of charge from the MySQL Documentation Library on the MySQL website For license information see the Legal Notices This product may contain third party code For license information on third party code see Appendix B Licenses for Third Party Components Used in MySQL Cluster Manager 1 1 6 Legal Notices Copyright 2009 2013 Oracle and or its affiliates All rights reserved This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitt
187. re 26 Installing the MySQL Cluster Manager Agent as a Windows Service Command Prompt Connect to a Network Projector DTE Bl Connect to a Projector L Getting Started as administrate z Math Input Panel Unpin from Start Menu Notepad i al Paint Restore previous versions K Remote Desktop Connection Send to bd Cut CB Snipping Tool mm L Sound Recorder M Sticky Notes Delete B Sync Center Rename ied Windows Explorer JE Windows Mobility Center E WordPad Jp Ease of Access JE System Tools JE Tablet PC p Windows PowerShell If a Windows UAC dialog referring to cmd exe appears click Yes to allow the command prompt to run as Administrator and thus to continue You should now have a command prompt window open on your desktop running a session with Administrator privileges To install the MySQL Cluster Manager agent as a service we use the SC CREATE command This command allows us to specify a name for the service for use in NET START and NET STOP commands a display name to be shown in the Service Manager a startup mode automatic or manual start and a path to the executable to be run as a service Use mcmd svc exe rather than mcmd exe as the executable The path must also include any arguments needed by the program in the case of MySQL 27 Installing the MySQL Cluster Manager Agent as a Windows Service Cluster Manager ncmd svc exe must be t
188. rectory having the same name as the archive less the tar gz extension Important A Because the Solaris version of tax cannot handle long filenames correctly the MySQL Cluster Manager program files may be corrupted if you try to use it to unpack the MySQL Cluster Manager archive To get around this issue on Solaris operating systems you should use GNU tar gtar rather than the default tar supplied with Solaris On Solaris 10 gt ar is often already installed in the usr sfw bin directory although the gt ar executable may not be included in your path If gt ar is not present on your system please consult the Solaris 10 system documentation for information on how to obtain and install it In general the location where you place the unpacked MySQL Cluster Manager directory and the name of this directory can be arbitrary For purposes of this discussion we assume that you rename the extracted directory to mcm and place it in the directory of the user account which will be used to operate MySQL Cluster Manager On a typical Linux system you can accomplish this task like this shell gt mv mcm 1 1 4 64 cluster 7 2 4 64 linux sleslil x86 mem For ease of use we recommend that you put the MySQL Cluster Manager files in the same directory on each host where you intend to run it Contents of the MySQL Cluster Manager Unix Distribution Archive If you change to the directory where you placed the extracted MySQL Cluster Manager archive and
189. red but should be similar to this mcm get attributes mcm mcm get ndb mgmd mycluster G KAZ ZX ck ck ck ck ck AA ck ck ck ck k kk kk kk kkkk k l row okckckck ck ck ck ck ck k kk A A A A A A A A AAA AAA Name DataDir Value home jon bin mcm mcm data clusters mycluster 49 data Processl ndb mgmd NodeId1 49 Process2 NodelId2 Level Comment ckckckckck ck ck ck ckck ck ck ck ck ck ck k k kk kkkk k 2 row Okckck ck ck ck ck ck ck ck AA A A kk A A k A AAA AAA Name HostName Value flundra Processl ndb mgmd NodeId1 49 Process2 NodelId2 Level Comment Read only ckckckckckck ck ck AA ck Z Z Z A AA AA AAA 3 row KAZ Z ck ck ck ck ck ck ck ck ck k k A A kk A A AAA AAA Name NodeId Value 49 Processl ndb mgmd NodeId1 49 Process2 NodelId2 Level Comment Read only KREKKKKKKKKK AZ Z ck Z Z Z Z ZAZ ZA AA AAA do row okckck ck ck ck ck ck ck ck ck A k A A kk A A A AAA AAA Name PortNumber Value 1186 Processl ndb mgmd NodeId1 49 Process2 Nodeld2 Level Process Comment 4 rows in set 0 09 sec mcm get ndbd mycluster G KEK KK KKK KKK KK KKK KKK ko ko kock ckockokok ills row KEK KKK KKK KKK KEK KEK KKK ko ko ko ko kokockok Name DataDir Value home jon bin mcm mcm data clusters mycluster 1 data Processi ndbd NodeId1 1 Process2 NodelId2 Level Comment ck ck KKK KKK ck ck ock ck ck ck ckockockockockckckock kckck ok 2 row ck ck ck ck ck ck ck ck ck ck ck ck ck ck AA ko ko ko ko kockckockokok Name H
190. reset Command mcm reset IndexMemory ndbd 3 mycluster 4 Command result 4 Cluster reconfigured successfully MMMM row in set 6 41 sec mcm get IndexMemory mycluster qp 4 4 4 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 4 4 4 4 4 4 IndexMemory 500M ndbd 2 Process IndexMemory 500M ndbd 3 Process 4 4 4 4 4 4 4 2 rows in set 1 09 sec Now re apply the instance level IndexMemory setting and verify using get that it has taken effect mcm set IndexMemory ndbd 3 750M mycluster q4 Command result q4 Cluster reconfigured successfully row in set 6 79 sec mcm get IndexMemory mycluster 4 4 4 Name Value Processl Idl Process2 Id2 Level Comment 4 qp qp 4 IndexMemory 500M ndbd 2 Process IndexMemory 750M ndbd
191. rgument For example consider the following MySQL Cluster Manager command which starts a MySQL Cluster named mycluster and backgrounds the deletion process so that the client can be used to execute other commands in the meantime without having to wait on the start cluster command to complete Start cluster background mycluster In this example the command contains a delete site instruction An instruction consists of one or two keywords such as set Of show status This instruction is modified by the background option which follows it however this option assigns no values Most command options have short forms consisting of single letters in addition to their long forms Using the short form of the background option the previous example could also be written like this delete site B mysite The long form of an option must be preceded by a double dash and is case insensitive lower case being the canonical form The short form of an option must be preceded by a single dash and is case sensitive In either case the dash character or characters must come immediately before the option name and there must be no space characters between them Otherwise the MySQL Cluster Manager client cannot parse the command correctly More information about long and short forms of options is given later in this section Important AN Do not confuse options given to MySQL Cluster Manager client commands with mysql clie
192. rough 9 The dash period and underscore characters A MySQL Cluster Manager identifier must begin with a letter or digit 44 Case sensitivity behavior The rules for case sensitivity of MySQL Cluster Manager identifiers commands command options process names and configuration attributes are as follows Identifiers are case sensitive For example delete site mycluster cannot be used to delete a site named myCluster Command keywords and the long forms of command options are case insensitive For example any of the three commands delete cluster mycluster DELETE CLUSTER mycluster and DeLeTe cLuStEr mycluster works to delete the MySQL Cluster instance named mycluster In this manual we show command keywords and the long forms of command options in lowercase but you are not required to follow this convention if you do not wish to do so The short forms of command options are case sensitive For example b lowercase is the short form of the basedir option but B uppercase is the short form of the background option Names of MySQL Cluster processes are case insensitive For example either of the commands get include defaults DataMemory ndbd mycluster 0f get include defaults datamemory NDBD mycluster reports the data memory allocated for each ndbd process in the cluster named mycluster In this manual we show names of MySQL Cluster processes in lowercase You are not re
193. ry It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty and each file should have at least the copyright line and a pointer to where the full notice is found one line to give the library s name and a brief idea of what it does Copyright C year name of author his library is free software you can redistribute it and or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation either version 2 1 of the License or at your option any later version This library is distributed in the hope that it will be useful but WITHOUT ANY WARRANTY without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE See the GNU Lesser General Public License for more details You should have received a copy of the GNU Lesser General Public License along with this library if not write to the Free Software Foundation Inc 51 Franklin Street Fifth Floor Boston MA OZV USA Also add information on how to contact you by electronic and paper mail You should also get your employer if you work as a programmer or your ooo seam O SSM COD VAC S erae crac llaloreewey aie necessary Here is a sample alter the names Yoyodyne Inc hereby disclaims all copyright interest in the library Frob a library for tweaking knobs written by James Random Hacker 117 libevent License xsig
194. s like this 63 The create cluster Command Free mysqld process mysqld Free ndbapi process ndbapie A mysqld process or ndbapi process that is specified without a host in this fashion is permitted to connect to the cluster from any host that can access the cluster over the network Otherwise the process may connect to the cluster only from the specified host By convention items in the process host list are listed according to the process type in the following order 1 Management node processes ndb mgmd 2 Data node processes MySQL Cluster NDB 6 3 ndbd MySQL Cluster NDB 7 0 and later ndba ndbmtd 3 SQL node processes mysqld 4 Custom NDB API applications ndbapi Note R For information about writing your own NDB API applications see The NDB API in the MySQL CLuster API Developer Guide While the order in which the items are listed does not affect whether the create cluster command succeeds we suggest that you follow this convention for readability as well as compatibility with other MySQL Cluster management tools such as ndb_mgm Note R create cluster causes cluster node IDs to be assigned consecutively in the order that the nodes are specified in the process host list Each host referenced in the list must be part of the site for which the package used in create cluster is defined For processes of types mysqld and ndbapi the hostname is required but not enforced in the
195. s level or instance level set commands are executed whether or not the cluster has been started In a cluster that is not running the MySQL Cluster Manager merely updates the configuration files However in a running cluster the MySQL Cluster Manager in addition automatically performs any node restarts or rolling restarts see Performing a Rolling Restart of a MySQL Cluster that are required to cause the attribute changes to take effect However since restart operations particularly rolling restarts where each process in the cluster must be stopped and restarted in turn can take a great deal of time it is preferable to make configuration changes before starting the cluster and putting it into use To set an attribute on the process level use a set statement that contains an attribute assignment having the form attribute name process name value 81 The sec Command For example to set DataMemory to 500 MB on the ndbd process level so that the new value applies to all ndbd processes in the cluster you can issue a set command containing the attribute assignment DataMemory ndbd 500M as shown here mcm set DataMemory ndbd 500M mycluster Command result q4 Cluster reconfigured successfully 1 row in set 5 68 sec To verify that the new setting is being used you can issue the followi
196. s the agent to start with default configuration values create a default one machine cluster named mycluster and start it This option works only if no cluster has yet created and is mutually exclusive with the defaults file option Currently any data stored in the default cluster mycluster is not preserved between cluster restarts this is a known issue which we may address in a future release of MySQL Cluster Manager The use of the boot st rap option with mcma is shown here on a system having the host name torsk where MySQL Cluster Manager has been installed to home 3on mcm shell mcmd bootstrap MySQL Cluster Manager 1 1 6 started Connect to MySQL Cluster Manager by running home jon mcm bin mcm a torsk 1862 Configuring default cluster mycluster Starting default cluster mycluster Cluster mycluster started successfully ndb mgmd torsk 1186 ndbd torsk ndbd torsk mysqid torsk 3306 mysqid torsk 3307 ndbapi Connect to the database by running home jon mcm cluster bin mysql h torsk P 3306 u root You can then connect to the agent using the mcm client see Section 2 6 Starting the MySQL Cluster Manager Client and to either of the MySQL Servers running on ports 3306 and 3307 using mysql or another MySQL client application The 1og file option allows you to override the default location for the agent log file normally mcmd log in the MySQL Cluster Manager installation directory You
197. scan count slave Yes Global No Ndb api read row count Yes Global No Ndb api read row count session Yes Session No Ndb api read row count slave Yes Global No Ndb api scan batch count Yes Global No Ndb api scan batch count session Yes Session No Ndb api scan batch count slave Yes Global No Ndb api table scan count Yes Global No Ndb api table scan count sesslon Yes Session No Ndb api table scan count slave Yes Global No Ndb api trans abort count Yes Global No Ndb api trans abort count session Yes Session No Ndb api trans abort count slave Yes Global No Ndb api trans close count Yes Global No Ndb api trans close count session Yes Session No Ndb api trans close count slave Yes Global No Ndb api trans commit count Yes Global No Ndb api trans commit count session Yes Session No Ndb api trans commit count sl ve Yes Global No Ndb api trans local read row dount Yes Global No 130 Name Cmd Line Option file System Var Status Var Var Scope Dynamic Ndb api trans local read row dount session Yes Session No Ndb api trans local read row count slave Yes Global No Ndb api trans start count Yes Global No Ndb api trans start count session Yes Session No Ndb api trans start count slave Yes Global No Ndb api uk op count Yes Global No Ndb api uk op count
198. se GNU LESSER GENERAL PUBLIC LICENSE Version 2 1 February 1999 Copyright C 1991 1999 Pree Software Foundation Inc SL Imeemedlin Seas Mizra Wile Bose MWA W290 Sy Everyone is permitted to copy and distribute verbatim copies of this license document but changing it is not allowed This is the first released version of the Lesser GPL It also counts as the successor of the GNU Library Public License version 2 hence the version number 2 1 Preamble The licenses for most software are designed to take away your freedom to share and change it By contrast the GNU General Public Licenses are intended to guarantee your freedom to share and change free software to make sure the software is free for all its users This license the Lesser General Public License applies to some specially designated software packages typically libraries of the Free Software Foundation and other authors who decide to use it You can use it too but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case based on the explanations below When we speak of free software we are referring to freedom of use not price Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software and charge for this service if you wish that you receive source code or can get it if you want it that you can change
199. sequential node IDs beginning with 1 in the order specified by the process host list used in the create cluster command If the node IDs in the existing cluster are not purely sequential without any gaps between consecutive node IDs or if the node IDs taken in order do not begin with 1 see Workaround for non sequential node IDs before executing create cluster Cluster configuration There is no facility in MySQL Cluster Manager 1 1 6 for importing configuration data from an existing cluster therefore this step must be performed manually Consolidate all configuration information from the existing cluster this includes parameters set in the cluster s config ini file or files mysqld options set in my cnf or my ini files and any arguments that were passed to MySQL Cluster executables on the command line when invoking them For most attributes you need to execute a set statement that is equivalent to a setting in a config ini or my cnf file Suppose that the config ini file contains an ndbd default setting such as this one DataMemory 2400G In this case you would need to execute this sec command in the MySQL Cluster Manager client mcm set DataMemory ndbd 2400G More generally if you have a my cnf file entry ina process type default section of config ini where process type is the name of a MySQL Cluster process ndb mgmd ndba mysqld or api then you can use the following regular expression to derive an equivalent MySQ
200. shown for mysqld nodes in the get output from the previous example and is not marked Read only MySQL Cluster Manager does not support socket files on Windows For this reason you should not attempt to set socket attributes for Windows mysqld processes using MySQL Cluster Manager To include default values for attributes that have not or not yet been set explicitly you can invoke this command with the include defaults option short form d as shown here in part mcm get include defaults mycluster G ckckckckck ck ck ck AA AZ AZ ck ck ck Z Z ZA AAA AAA ils row Okckck ck ck ck ck ck ck ck ck AA A A kk A A A AAA AAA Name ndbmt classic Value NULL Processi ndbmtd NodelIdl 1 Process2 NodelId2 Level Default Comment ckckck ck ck ck ck ck ckck ck ck ck ck A A A A AA AAA 2 row Okckckck ck ck ck ck ck k k A A kk A A A AA AAA AAA Name ndbmt lgh threads Value NULL Processl ndbmtd NodeId1 1 Process2 NodeId2 Level Default Comment ckckckck ck ck ck ck AA ck ck ck ck ck ck ck k k kk AA AAA 3 row Okckck ck ck ck ck ck ck ck AA A A kk A A k A AAA AAA Name _ ndbmt lqh workers Value NULL Processl ndbmtd NodeIdi 1 Process2 NodeId2 Level Default Comment ck ck ck ck ck ck ck ck ck ck ock ck ck ck ckock kk ko ko kock kockckok ale row KEK KKK KKK KKK KKK KKK ko ko ko kok kokokok Name Arbitration Value Default Processl ndbmtd NodeId1 1 Process2 75 The get Command NodelId2 Level
201. sion is interface compatible with the version that the work was made with C Accompany the work with a written offer valid for at least three years to give the same user the materials Specified in Subsection 6a above for a charge no more than the cost of performing this distribution d If distribution of the work is made by offering access to copy from a designated place offer equivalent access to copy the above specified materials from the same place e Verify that the user has already received a copy of these materials or that you have already sent this user a copy For an executable the required form of the work that uses the Library must include any data and utility programs needed for reproducing the executable from it However as a special exception the materials to be distributed need not include anything that is normally distributed in either source or binary form with the major components compiler kernel and so on of the operating system on which the executable runs unless that component itself accompanies the executable It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system Such a contradiction means you cannot use both them and the Library together in an executable that you distribute 7 You may place library facilities that are a work based on the Library side by side in a single library together with o
202. sqld NodelIdl 51 Process2 NodelId2 Level Comment Read only kkkkkkk k k k k k k k k k k kkkk kk kk k 26 row okckckckckckckck ck ck ck ck ck kk kk kk kk kkkkk k Name port Value 3307 Processi mysqld NodelIdl 51 Process2 NodelId2 Level Comment okckckckck ck ck ck kck ck ck ck ck ck ck k kk kk kk kk k m row kckckckckckck ck ck ck ko kk ko k kk kk kk kkkkk k Name socket Value tmp mysgl mycluster 51 sock Processl mysqld NodelIdl 51 Process2 NodelId2 Level Comment okckckckck ck ck ck kck ck ck ck ck ck kc k kk kk kk kk me row kckck ck ck ck ck kck ck ck ck ck ko k kk kk kk kkkkkk k Name tmpdir Value home jon bin mcm mcm data clusters mycluster 51 data tmp 74 The get Command Processl mysqld NodeIdl 51 Process2 NodelId2 Level Comment KAZ ZX ck ck ck ck ck ckck ck ck Z ck Z Z Z k A AA AAA AA 29 row AKA XZ ck ck ck ck ck ck ck ck k k A A A A A A A AAA AAA Name NodeId Value 52 Processl ndbapi NodeIdl 52 Process2 NodelId2 Level Comment Read only 29 rows in set 0 05 sec On Windows no substitutions for backslashes or other characters used in values of paths reported by the get command is performed However it is possible to see forward slashes used in such paths if the values were set using the set command See Section 3 5 2 The set Command and in particular Setting Attributes Containing Paths on Windows 85 for more information Although a socket attribute is
203. ssl mysqld NodeId1 50 Process2 NodeId2 Level Comment ck ck ck ck ck ck ck ck ck ck ock ck ck A AAA ko ko ko AA ck AAA 9 row kkkkxkxkxkkkkkkkkkkkkkkkkkkkxk kxx k Name tmpdir Value home jon bin mcm mcm data clusters mycluster 50 data tmp Processl mysqld NodeId1 50 Process2 NodeId2 Level Comment ck ck ck ck ck ck ck ck ck ck ock ck ck AAA ko ko ko ko kock kc kck OL row KKEKKKKKKKKKKKKKKKKKKKKAKKKKK Name datadir Value home jon bin mcm mcm data clusters mycluster 51 data Processl mysqld NodeId1 51 Process2 NodeId2 Level Comment A AX ZX ck ck ck ck ck ck ok ock ck ockock oko ko ko ko ko ko kock kc kok ok UE row A AX ck ck ck ck ck ck ck koc KA AA A A A KA A ko AAA Name HostName Value torsk Processl mysqld 53 Online Help for MySQL Cluster Manager Commands NodeId1 51 Process2 NodelId2 Level Comment Read only ck ck ck ck ck ck ERER RRR A ko ko ko A ZA kA A dA row ck ck ck ck ck ck ck ck ck ck ck kA AA A A A ko ko Z kk kk Name log error Value home jon bin mcm mcm data clusters mycluster 51 data mysqld 51 out err Processi mysqld NodeId1 51 Process2 NodelId2 Level Comment ck ck ck ck ck ck ck ck kA AA A ko ko ko A ko ko kock ko AAA 1 5 row ck ck ck ck ck ck ck ck ck koc kk kk A A A ko ko kA kk k Name ndb nodeid Value 51 Processl mysqld NodeId1 51 Process2 Nodeld2 Level Comment Read only ERRAR RER ERER ERE RRE R ERR ko kA kk k dd row ck ck ck ck ck ck ck ck ck ck ok k
204. st name in addition to the port number but in MySQL Cluster Manager 1 1 1 and later the host name is no longer accepted agent uuid A legal UUID value Set internally This value needs to be set explicitly only when configuring multiple agents on the same host normally there is no need to uncomment this line A valid path optional on Linux and filename log file Default mcmd log You can change this if desired but there is no need to do so On Linux and similar operating systems you can use a relative 20 MySQL Cluster Manager Configuration File Setting Type Format Default Permitted Description Values path this is in relation to the MySQL Cluster Manager installation directory and not to the bin or ecc subdirectory On Windows you must use an absolute path and it cannot contain any spaces in addition and you must replace any backslash characters in the path with forward slashes log level The log event level One of debug This is the log event severity level see critical error MySQL Cluster Logging Management info message Commands for definitions of the levels warning Default which are the same as these except that message ALERT is mapped to critical and the Unix syslog LOG_NOTICE level is used and mapped to message The debug message and info levels can result in rapid growth of the agent log so for normal operations you m
205. startup Starting the MySQL Cluster Manager client and connect to the MySQL Cluster Manager agent You can connect to an agent process running on any of the cluster hosts using the mcm client on any computer that can establish a network connection to the desired host See Section 2 6 Starting the MySQL Cluster Manager Client for details On systems where mcm is not available you can use the mysal client for this purpose See Connecting to the agent using the mysql client MySQL Cluster software deployment The simplest and easiest way to do this is to copy the complete MySQL Cluster distribution to the same location on every host in the cluster If you have installed MySQL Cluster Manager 1 1 6 on each host the MySQL Cluster NDB 7 2 4 distribution is already included in mcm installation dir cluster If you do not use the same location on every host be sure to note it for each host Do not yet start any MySQL Cluster processes or edit any configuration files when creating a new cluster MySQL Cluster Manager takes care of these tasks automatically On Windows hosts you should not install as services any of the MySQL Cluster node process programs including ndb mgmd exe ndbd exe ndbmtd exe and mysqid exe MySQL Cluster Manager manages MySQL Cluster processes independently of the Windows Service Manager and does not interact with the Service Manager or any Windows services when doing so package is registered using add package However
206. t uses the Library uses material from a header file that is part of the Library the object code for the work may be a derivative work of the Library even though the source code is not Whether this is true is especially significant if the work can be linked without the Library or if the work is itself a library The threshold for this to be true is not precisely defined by law If such an object file uses only numerical parameters data structure layouts and accessors and small macros and small inline functions ten lines or less in length then the use of the object file is unrestricted regardless of whether it is legally a derivative work Executables containing this object code plus portions of the Library will still fall under Section 6 Otherwise if the work is a derivative of the Library you may distribute the object code for the work under the terms of Section 6 Any executables containing that work also fall under Section 6 whether or not they are linked directly with the Library itself 6 As an exception to the Sections above you may also combine or link a work that uses the Library with the Library to produce a work containing portions of the Library and distribute that work under terms of your choice provided that the terms permit modification of the work for the customer s own use and reverse engineering for debugging such modifications You must give prominent notice with each copy of the work that the Library is us
207. t1 ndbd host1 ndbd host2 X mysqld host3 mysqld host4 mycluster start cluster mycluster The long create cluster command can be divided into a shorter and more manageable version of itself plus several add process commands This set of commands performs the same task as the previous set creating mycluster with exactly the same processes and hosts as before and then starting it create cluster processhosts ndb mgmdGhostl mycluster add process processhosts ndbd hostl ndbdGhost2 mycluster add process processhosts mysqld host3 mysqld host4 mycluster start cluster mycluster Because mycluster was never started before the ndbd and mysqld processes were added to it using the add process commands shown it is not necessary to use the added option with the start cluster command in this case all 5 processes are started A newly added process inherits its configuration attribute settings from those in effect for its process type on the parent cluster or assume the default settings for that process type if none apply Existing attribute settings in the cluster must have process level scope to be inherited by new processes added later instance level settings set for existing process instances prior to adding any new ones do not apply to any of the added processes See Configuration attributes for more information about the scope of attribute settings Inherited attribute settings can be overridden when adding processes to do
208. teger 4000 4G N MaxNoOtfLocalOperatitmeger UNDEFINED 32 4G N MaxNoOfLocalScans integer UNDEFINED 32 4G N MaxNoOfOpenFiles unsigned 20 4G N MaxNoOfOrderedIndexdeger 128 4G N MaxNoOfSavedMessaig ager 25 4G N 127 Name Type Units Default Min Value Max Value Restart Type MaxNoOfSubscribers unsigned 4G N MaxNoOfSubscriptionsinsigned 4G N MaxNoOfTables integer 128 8 20320 N MaxNoOfTriggers integer 768 4G N MaxNoOfUnigueHashindeges 64 4G N MaxParallelScansPerfrgiement 32 O gt Mo he IN MaxStartFailRetries unsigned 3 4G N MemReportFrequencyunsigned 4G N MinFreePct unsigned 5 100 N NodeGroup 65536 IS Nodeld unsigned 48 IS NoOfFragmentLogFilemteger 16 3 4G IN NoOfReplicas integer 1 4 IS Numa 1 N ODirect false N RealtimeScheduler false N RedoBuffer bytes 8M 1M 4G N RedoOverCommitCounter 3 4G N RedoOverCommitLimi amp econds 20 4G N ReservedSendBufferMsgytes y 256K 4G N RestartOnErrorlnsert error code 2 4 N SchedulerExecutionT msec 50 11000 N SchedulerSpinTimer usec 500 N ServerPort unsigned 1 64K N SharedGlobalMemory bytes 20M 64T N StartFailRetryDelay unsigned 4G N StartFailureTimeout milliseconds 4G N StartNoNodeGroupTimmeitliseconds 15000 4294967039 N StartPartialTimeout milliseconds 30000 4G N StartPartitionedTimeoumilliseconds 60000 4G N StartupStatusReportFeenenty N StopOnError true N StringMemory 96 or by
209. ter process runs making up a the MySQL Cluster This command also uses the name of the package registered in the previous step so that MySQL Cluster Manager knows the location of the binary running each cluster process For more about this command see Section 3 4 1 The create cluster Command You can use the 1ist clusters and list processes commands to determine whether the cluster has been defined as desired 36 Migrating a MySQL Cluster to MySQL Cluster Manager see Section 3 4 7 The list clusters Command and Section 3 8 5 The list processes Command respectively for more information about these MySQL Cluster Manager client commands If you wish to use SQL node connection pooling see Setup for mysqld connection pooling before creating the cluster Initial configuration Perform any configuration of the cluster that is required or desired prior to starting it You can set values for MySQL Cluster Manager configuration attributes MySQL Cluster parameters and MySQL Server options using the MySQL Cluster Manager client set command which is explained in detail in Section 3 5 2 The set Command You do not need to edit any configuration files directly in fact you should not do so Keep in mind that certain attributes are read only and that some others cannot be reset after the cluster has been started for the first time You can use the get command to verify that attributes have been set to the correct values see Sec
210. tes 25 4G S TcpBind INADDR ANY false N TimeBetweenEpochs milliseconds 100 32000 N TimeBetweenEpochs Innil setonds 4000 256000 N TimeBetweenGlobalCineitligecatkis 2000 10 32000 N TimeBetweenlnactive Imillisac amp nd amp bortCheck 000 1000 4G N 128 Name Type Units Default Min Value Max Value Restart Type TimeBetweenLocalCheckpbertsf 4 byte 20 31 N words as a base 2 logarithm TimeBetweenWatchDogi isecionnds 6000 70 4G N TimeBetweenWatchDonilllsecbimii al 6000 70 4G N TotalSendBufferMemobytes 256K 4G N TransactionBufferMemtyrtes 1M 1K 4G N TransactionDeadlockDeikis ono noseout 1200 50 4G N TransactionInactiveTimetiseconds 4G 4G N TwoPasslnitialNodeRestartCopy false N UndoDataBuffer unsigned 16M 1M 4G N UndolndexBuffer unsigned 2M 1M 4G N Table C 3 API Node Configuration Parameters Name Type Units Default Min Value Max Value Restart Type ArbitrationDelay milliseconds 4G N ArbitrationRank 0 2 2 N AutoReconnect false N BatchByteSize bytes 32K 1024 1M N BatchSize records 64 1 992 N ConnectionMap N DefaultHashMapSize LDM threads 240 3840 N DefaultOperationRedoProblemAction ABORT ExecuteOnComputer name S ExtraSendBufferMem bytes 32G N HeartbeatThreadPriority HostName name or IP address S Id unsigned 1 63 IS MaxScanBatchSize bytes 256K 32K 16M N Nodeld unsigned 1 63 IS TotalSe
211. that is not a library 4 You may copy and distribute the Library or a portion or derivative of it under Section 2 in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine readable source code which must be distributed under the terms of Sections 1 and 2 above ona medium customarily used for software interchange If distribution of object code is made by offering access to copy 113 GNU Lesser General Public License Version 2 1 February 1999 from a designated place then offering equivalent access to copy the Source code from the same place satisfies the requirement to distribute the source code even though third parties are not compelled to copy the source along with the object code 5 A program that contains no derivative of any portion of the Library but is designed to work with the Library by being compiled or linked with it is called a work that uses the Library Such a work in isolation is not a derivative work of the Library and therefore falls outside the scope of this License However linking a work that uses the Library with the Library creates an executable that is a derivative of the Library because it contains portions of the Library rather than a work that uses the library The executable is therefore covered by this License Section 6 states terms for distribution of such executables When a work tha
212. the cause for this unplanned shutdown fix the problem and restart the process as soon as possible unknown MySQL Cluster Manager is unable to establish the current status of this process You should try to determine its status using other means You must supply the name of an existing cluster with this command or else show status fails with an error as shown here mcm show status ERROR 6 00MGR Illegal number of operands 95 The stop agents Command mcm show status c nosuchcluster ERROR 5001 00MGR Cluster nosuchcluster not defined Important a different syntax and which can be used only in the standard mysqi client The MySQL Cluster Manager client command accepts only those options shown at the beginning of this section and does not accept a LIKE or WHERE clause A Do not confuse this command with the MySQL SHOW STATUS statement which has 3 7 The stop agents Command stop agents hosts host list site name This command is introduced in MySQL Cluster Manager 1 1 1 It stops one or more MySQL Cluster Manager agents When used without any arguments stop agents stops the agent to which the client is currently connected When used with the name of a management site the command stops all agents running on hosts making up the site The following stops all MySQL Cluster Manager agents running on hosts in mysite mcm stop agents mysite You can also stop a subset of t
213. ther library facilities not covered by this License and distribute such a combined library provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted and provided that you do these two things a Accompany the combined library with a copy of the same work based on the Library uncombined with any other library facilities This must be distributed under the terms of the Sections above b Give prominent notice with the combined library of the fact that part of it is a work based on the Library and explaining where to find the accompanying uncombined form of the same work 8 You may not copy modify sublicense link with or distribute the Library except as expressly provided under this License Any attempt otherwise to copy modify sublicense link with or distribute the Library is void and will automatically terminate your rights under this License However parties who have received copies or rights from you under this License will not have their licenses terminated so long as such parties remain in full compliance 9 You are not required to accept this License since you have not signed it However nothing else grants you permission to modify or distribute the Library or its derivative works These actions are prohibited by law if you do not accept this License Therefore by modifying or distributing the Library or any work based on the Library you indic
214. this use the start process command s set option This option takes as its argument an attribute assignment list similar in format to that used with the get and set commands Suppose that the current ndbd process level setting in the 97 The start process Command cluster named mycluster for the DataDir attribute is home users ndb cluster data but you wish to add two new ndbd processes that use tmp cluster data instead You can do this using the following command mcm add process processhosts mysqldGtorsk mysqld8kolja gt set ndbd DataDir tmp cluster data mysite Note R The equals sign immediately following the set option is required When setting attributes in this way which contain paths for processes running on Windows you must replace any backslashes used with forward slashes just as with the set command See Setting Attributes Containing Paths on Windows 85 in Section 3 5 2 The set Command for more information After a process has been added using add process you can also use the set command to modify its configuration attribute settings or specify additional ones as you would with any other cluster process being managed with MySQL Cluster Manager It is not currently possible to drop or delete cluster processes using MySQL Cluster Manager Note R When IPv6 enabled Windows systems are used as MySQL Cluster hosts under MySQL Cluster Manager you must reference these hosts using IPv4 ad
215. tion such as the Windows desktop You can view a list of available mys gl client commands using the help command For more information about these view the help output or see mysql Commands in the MySQL Manual 3 2 MySQL Cluster Manager Site Commands In this section we discuss commands used to work with MySQL Cluster Manager management sites computers where MySQL Cluster Manager agents are running Each agent is identified by the combination of two pieces of information The hostname or IP address of the machine where the agent is running The number of the port used by the agent for communications Note E MySQL Cluster makes extremely intensive use of network connections and DNS lookups can contend with MySQL Cluster and MySQL Cluster Manager for bandwidth resulting in a negative impact on the performance of MySQL Cluster and the applications using it For this reason we recommend that you use numeric IP addresses rather than hostnames for MySQL Cluster and MySQL Cluster Manager host computers whenever feasible 3 2 1 The create site Command create site hosts h host_list site name POSER INSE basie pIMOEE laaa The create site command is used to create a MySQL Cluster Manager management site that is a set of MySQL Cluster Manager management agents running on one or more host computers The command requires a list of one or more hosts where management agents are running and a name for the site The host list
216. tion 3 5 1 The get Command Cluster startup Once you have completed the previous steps including necessary or desired initial configuration you are ready to start the cluster The start cluster command starts all cluster processes in the correct order You can verify that the cluster has started and is running normally after this command has completed using the MySQL Cluster Manager client command show status see Section 3 6 The show status Command At this point the cluster is ready for use by MySQL Cluster applications 2 7 2 Migrating a MySQL Cluster to MySQL Cluster Manager MySQL Cluster Manager is designed primarily for managing MySQL Cluster deployments that are created by it rather than introducing it into existing MySQL Cluster instances that are already in use Currently there is no integrated functionality for importing an existing MySQL Cluster into MySQL Cluster Manager and it is not currently possible to perform this task without shutting down and restarting the cluster This section outlines a suggested procedure for importing an existing MySQL Cluster manually into MySQL Cluster Manager It is in many ways similar to creating a new cluster in MySQL Cluster Manager but differs in how initial configuration of the cluster is carried out The importation procedure includes the following steps MySQL Cluster Manager agent installation and startup Deploy the MySQL Cluster Manager software distribution on the clust
217. tion attribute was set to a user defined value Attempting to set it on the instance level may leave the cluster the MySQL Cluster Warning e The mandatory NoOfReplicas attribute must be set on the process level only Manager or both in an unusable configuration Unlike the case with the get command you cannot issue a set acting on a global scope that is you cannot in a single attribute assignment set a single value for an attribute such that the new attribute value applies to all processes regardless of process type even if the attribute having that name can be applied to all process types Nor can you specify multiple process types in a single attribute assignment Attempting to do either of these things causes an error as shown here mcm set DataDir var cluster data mycluster ERROR 3 00MGR Illegal syntax mcm set DataDir ndb mgmd ndbd mysgld var cluster data mycluster ERROR 3 00MGR Illegal syntax Instead you must use a process level attribute assgnment for each process type However you are not necessarily required to issue a separate set command for each process type Instead you can also make multiple attribute assignments in a single set command supplying the assignments as a comma separated list This set command assigns var cdata as the data directory DataDir for all MySQL Cluster processes in the cluster named mycluster mcm set DataDir ndb mgmd var cdata DataDir ndbd var cdata X DataDir mysq
218. tioned elsewhere see for example Section 2 7 1 Creating a MySQL Cluster with MySQL Cluster Manager you must install a copy of MySQL Cluster Manager on each computer where you intend to host a MySQL Cluster node Therefore the following procedure must be performed separately on each host computer For ease of installations and upgrades on multiple machines it is recommended that you install MySQL Cluster Manager to the same location on each host This is C Program Files MySQL MySOL Cluster Manager 1 1 4 orcC Program Files x86 MMySQLMMySQL Cluster Manager 1 1 4X by default but it is possible to install MySQL Cluster Manager to an alternate location such as C mem Installing MySQL Cluster Manager on Windows Platforms In the discussion that follows we assume that you have downloaded the MySQL Cluster Manager MSI installer as user jon to this user s Downloads directory C NUsersN jon Downloads MCM on a 64 bit Windows system Navigate to this directory in Windows Explorer as shown in the following screenshot 5 C Users jon Downloads MCM Organize Indudeinlbrary v Sharewih v Newfolder i v 7 Favorites jB mem 1 1 4 duster 7 2 4 nin32 x86 msi Libraries jE Computer yg Network 1 tem To run the installer double click on the file icon in Windows Explorer Some versions of Windows also provide an Install item in the Windows Explorer menu that can be used to run the installer When you st
219. to be deleted is running as shown here mcm gt delete cluster mycluster ERROR 5010 00MGR All processes must be stopped to delete cluster mycluster You must shut down the cluster first using stop cluster see Section 3 4 4 The stop cluster Command 3 4 3 The start cluster Command Start cluster cluster name This command starts the cluster named cluster name as shown in this example mcm start cluster mycluster q4 Command result Cluster started successfully 1 row in set 45 37 sec In order for the command to succeed the cluster named in the command must already exist otherwise the command fails with the error Cluster cluster name not defined as shown here mcm list sites 4 4 4 4 Site Pere rosd eese 4 4 4 4 mysite 1862 Local tonfisk flundra grindval haj 4 4 4 4 row in set 1 72 sec mcm gt list clusters mysite Cluster Package mycluster mypackage row in set 1 70 sec
220. to control compilation and installation of the library Activities other than copying distribution and modification are not covered by this License they are outside its scope The act of running a program using the Library is not restricted and output from such a program is covered only if its contents constitute a work based on the Library independent of the use of the Library in a tool for writing it Whether that is true depends on what the Library does and what the program that uses the Library does 1 You may copy and distribute verbatim copies of the Library s complete source code as you receive it in any medium provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty keep intact all the notices that refer to this License and to the absence of any warranty and distribute a copy of this License along with the Library You may charge a fee for the physical act of transferring a copy and you may at your option offer warranty protection in exchange for a fee 2 You may modify your copy or copies of the Library or any portion of it thus forming a work based on the Library and copy and distribute such modifications or work under the terms of Section 1 above provided that you also meet all of these conditions a The modified work must itself be a software library 112 GNU Lesser General Public License Version 2 1 February 1999 b You must ca
221. ues from a MySQL Cluster See Section 3 5 MySQL Cluster Manager Configuration Commands for a definition of the term attribute as it applies in the MySQL Cluster Manager The output includes the following columns Name This column contains the name of the configuration attribute Value This column shows the attribute s current value Process1 This column holds the process type to which the attribute applies This is one of ndb mgma ndbd ndbmt a MySQL Cluster NDB 7 0 and later or mysqld e Id1 This is the process ID of the process to which the attribute applies Process2 For attributes that require specifying two nodes such as those relating to TCP IP connections this column shows the process type of the second node e Id2 For attributes that require specifying two nodes this column shows the process ID for the second node Level This is the attribute process level This value in this column can be Default Process or empty if this column is empty it means that the attribute applies on the instance level Comment This column is used to show whether the attribute is Mandatory Read only Default attribute or user defined in which case the Comment column is empty 72 The get Command By default get returns only those attributes that have been set explicitly either by the MySQL Cluster Manager itself or by the user In other words it shows only attributes that are mandatory including r
222. unsigned 64K N TotalSendBufferMem bytes 256K 4G N wan false N 125 Table C 2 Data Node Configuration Parameters Name Type Units Default Min Value Max Value Restart Type Arbitration Default N ArbitrationTimeout milliseconds 3000 10 4G N BackupDataBufferSizebytes 2M 4G N BackupDataDir path FileSystemPath IN BackupLogBufferSize bytes 2M 4G N BackupMaxWriteSize bytes 1M 2K 4G N BackupMemory bytes 4M 4G N BackupReportFreguerggconds 4G N BackupWriteSize bytes 32K 2K 4G N BatchSizePerLocalSc nteger 64 1 992 N BuildIndexThreads 128 CompressedBackup false N CompressedLCP false N ConnectCheckintervalDelay 1500 4G N CrashOnCorruptedTuple false DataDir path IN DataMemory bytes 80M 1M 1024G N DefaultHashMapSize LDM threads 240 3840 N DictTrace bytes undefined 100 N DiskCheckpointSpeedbytes 10M 1M 4G N DiskCheckpointSpeedbyiestart 100M 1M 4G N DisklOThreadPool threads 8 4G N Diskless true false 1 0 false IS DiskPageBufferMematyytes 64M 4M 1T N DiskSyncSize bytes 4M 32K 4G N ExecuteOnComputer name S ExtraSendBufferMem bytes 32G N FileSystemPath path DataDir IN FileSystemPathDataFiles FileSystemPathDD IN FileSystemPathDD FileSystemPath IN FileSystemPathUndo iles FileSystemPathDD IN FragmentLogFileSize bytes 16M 4M 1G IN HeartbeatlntervalDbApnilliseconds 1500 100 4G N HeartbeatlntervalDbDlmil
223. uration data 69 MySQL Cluster Manager Configuration Commands for configuration variables many but not all of which can be overridden in a Note R Configuration options passed to mysald often have the effect of setting values running MySQL server using a MySQL client application such as mysql MySQL Cluster Manager simplifies this configuration scheme by treating all 3 types of configuration data Server variable or a command line option used with one or more MySQL Cluster binary programs It does this transparently handling all necessary changes in a unified interface For example suppose that you wish to know how much data memory is allocated to the data nodes in a given MySQL Cluster Rather than having to determine that this is controlled using the DataMemory configuration parameter that is written in the config ini file and then reading that file to find the value you merely invoke the MySQL Cluster Manager get command and MySQL Cluster Manager handles reading from the file for you and displays the value without the necessity of opening the file in a separate application such as more or less If you wish to change the amount of data memory allocated to the data nodes you can issue a MySQL Cluster Manager set or reset command MySQL Cluster Manager then writes the desired value to config ini lf as is the case with Dat aMemor y updating a configuration value in a running MySQL Cluster requires a rolling restart to be
224. use the files modified to carry prominent notices stating that you changed the files and the date of any change C You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License d If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility other than as an argument passed when the facility is invoked then you must make a good faith effort to ensure that in the event an application does not supply such function or table the facility still operates and performs whatever part of its purpose remains meaningful For example a function in a library to compute square roots has a purpose that is entirely well defined independent of the application Therefore Subsection 2d requires that any application supplied function or table used by this function must be optional if the application does not supply it the square root function must still compute square roots hese requirements apply to the modified work as a whole If dentifiable sections of that work are not derived from the Library nd can be reasonably considered independent and separate works in hemselves then this License and its terms do not apply to those ections when you distribute them as separate works But when you istribute the same sections as part of a whole which is a work based n the Library the distribution of the whole must be on
225. x Solaris 10 Recent versions of Microsoft Windows MySQL Cluster NDB 7 1 4 and later MySQL Cluster Manager is currently supported for use in the following MySQL Cluster release versions on the platforms shown MySQL Cluster NDB 6 3 beginning with MySQL Cluster NDB 6 3 27a Linux Solaris MySQL Cluster NDB 7 0 beginning with MySQL Cluster NDB 7 0 8a Linux Solaris MySQL Cluster NDB 7 1 beginning with MySQL Cluster NDB 7 1 4 Linux Solaris Windows Operating Platform and MySQL Cluster Version Compatibility MySQL Cluster NDB 7 2 beginning with MySQL Cluster NDB 7 2 4 Linux Solaris Windows Prior to installation you must obtain the correct build of MySQL Cluster Manager for your operating system and hardware platform For Unix platforms MySQL Cluster Manager is delivered as a Unix tar gz archive For Windows platforms an MSI installer file is provided The name of the file varies with the target platform MySQL Cluster Manager 1 1 6 packages that include MySQL Cluster NDB 7 2 4 are also available on all supported platforms available packages with applicable platforma and architectures can be found in in the following table Package OS Platform Architecture Includes MySQL Cluster NDB 7 2 6 mcom 1 1 6 32 Red Hat Linux 5 32 bit Yes cluster 7 2 6 32 linux rhel5 x86 tar gz mcm 1 1 6 32 linux Red Hat Linux 5 32 bit No rhel5 x86 tar gz mcm 1 1
226. y to restart the Cluster under control of MySQL Cluster Manager This requires a system restart that is the cluster must be completely shut down then restarted Important AN Before proceding with this step make certain that the configuration you have set up for the cluster in MySQL Cluster Manager is correct In particular make sure that the node ID and data directory are the same for each node in both the original configuration and the new configuration you have just created using MySQL Cluster Manager Also verify that you have set any attributes that cannot be changed once the cluster has been started for the first time Shutting down the cluster consists of the following two steps 1 Issue an ndb mgm SHUTDOWN command You can do this either in an ndb mgm client session or by invoking ndb mgm from the system shell like this shell ndb mgm e SHUTDOWN Here the quotation marks are optional For more information see Commands in the MySQL Cluster Management Client 2 Stop all mysqld processes that were connected to the cluster To do this issue the following command on each host running an SQL node shell mysqladmin uroot shutdown If the MySQL root user password has been set you can supply it when invoking the command like this shell mysqladmin uroot prootpassword shutdown If more than one mysqld process is running on the same host each process must use a different port In such cases you must invoke m
227. ySQL Cluster Manager because MySQL Cluster Manager s internal representation of the cluster requires them to be One way to surmount this issue is to insert dummy ndbapi entries into the process hosts list used in the create cluster statement The following example illustrates how this can be done Suppose the original cluster has 8 nodes that use the process types the node IDs and hosts shown in the following table Process type Node ID Host ndb mgmd 2 192 168 10 2 ndb mgmd 4 192 168 10 4 ndbd 5 192 168 10 10 ndbd 6 192 168 10 11 ndbd 7 192 168 10 10 ndbd 8 192 168 10 11 mysqld 10 192 168 10 20 mysqld T2 192 168 10 21 Assuming that a package named mypackage has already been registered a cluster named mycluster having the preceding distribution of nodes on hosts can be created in the mcm client like this mcm create cluster P mypackage R ndb_mgmd 192 168 10 2 ndb_mgmd 192 168 10 4 ndbd 192 168 10 10 ndbd 192 168 10 11 ndbd 192 168 10 10 ndbd 192 168 10 11 mysqld 192 168 10 20 mysqld 192 168 10 21 mycluster v v V However the node IDs generated by this statement are the numbers 1 2 3 8 In order to preserve the original numbering we need to account for the numbers 1 3 9 and 11 The following version of the command has been modified such that dummy ndbapi process entries have been inserted into the list of processes on hosts the extra entries
228. you have any questions about the features included in your version of MySQL Cluster Manager refer to your MySQL Cluster Manager license agreement or contact your Oracle sales representative MySQL Cluster Manager MySQL Server and MySQL Cluster features This manual contains certain basic information about MySQL Server and MySQL Cluster however it is not in any way intended as an exhaustive reference for either of these products Current versions of MySQL Cluster compatible with MySQL Cluster Manager are based on versions 6 3 7 0 7 1 and 7 2 of the NDB storage engine these versions of MySQL Cluster are known as MySQL Cluster NDB 6 3 MySQL Cluster NDB 7 0 MySQL Cluster NDB 7 1 and MySQL Cluster NDB 7 2 MySQL Cluster functionality varies between MySQL Cluster releases MySQL Cluster Manager cannot supply or emulate MySQL Cluster features that are not present in the version of the MySQL Cluster software in use For complete information about MySQL Server and MySQL Cluster please refer to the appropriate version of the MySQL Manual See MySQL Cluster NDB 6 1 7 1 for information about MySQL Cluster NDB 6 3 MySQL Cluster NDB 7 0 and MySQL Cluster NDB 7 1 For information about MySQL Cluster NDB 7 2 see MySQL Cluster NDB 7 2 If you do not have the MySQL Server and MySQL Cluster documentation you can obtain it free of charge from the MySQL Documentation Library on the MySQL website For legal information see the Legal
229. ysqladmin separately for each mysqld process specifying the port each time with the port or P option similar to what is shown here 39 Migrating a MySQL Cluster to MySQL Cluster Manager shell mysqladmin uroot P3306 shutdown 110919 12 41 26 mysald safe mysald from pid file usr local mysql data ml pid ended 1 Done mysqld safe port 3306 pid file usr local mysql data ml pid shell mysqladmin uroot P3307 shutdown 110919 12 41 26 mysald safe mysald from pid file usr local mysql data m2 pid ended 1 Done mysqld safe port 3307 pid file usr local mysql data m2 pid See mysqladmin Client for Administering a MySQL Server for more information Once all cluster processes have stopped you can start the cluster using MySQL Cluster Manager Start the MySQL Cluster Manager agent and a MySQL Cluster Manager client session if these are not already running then issue a start cluster command in the MySQL Cluster Manager client substituting the name of the imported cluster for mycluster mcm start cluster mycluster Once the cluster has started successfully the importation process is complete and you should be able from this point onwards to manage the cluster as if you had actually created it using MySQL Cluster Manager Workaround for non sequential node IDs If the node IDs in the existing cluster are not strictly consecutive beginning with 1 this causes problems when trying to import it into M

MySQL™ Cluster Manager 1.1.6 User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents

MySQL&trade; Cluster Manager 1.1.6 User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents

MySQL™ Cluster Manager 1.1.6 User Manual