MySQL Cluster Administration Tools 0.3.1 (Default branch)


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications High Performance Computing MySQL Cluster Administration Tools 0.3.1 (Default branch)
# 1  
Old 08-28-2008
MySQL Cluster Administration Tools 0.3.1 (Default branch)

The MyCAT project is a toolset for managing MySQL/Linux servers, and could be helpful for anyone managing a network of *nix servers whether running MySQL Cluster, standard replication, or not running MySQL at all. At present, it contains three programs. rcall eases use and administration of groups (clusters) of *nix servers by creating logical groupings and a single location from which to run commands on all servers while entering it only once. It requires only an SSH connection. rep_mon is a replication monitor that notifies if a server is lagging or has encountered any errors. It handles any replication topology easily. binlog_mon monitors disk space used by MySQL binary logs, purging only when disk space is needed. It checks all slaves to ensure that purged files are not still being read by slaves. It has configurable behavior in the event that a slave still needs the oldest file. License: GNU General Public License (GPL) Changes:
Critical bugs were fixed in both binlog_mon and rep_mon. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Learning project ideas - shell, python, UNIX tools, system administration

Hi guys, I am currently working as a system administration engineer, administering telecom applications on linux/unix platforms. I want to learn new things and improve the ones that i have and for this i though to really work on some project or something but i lack of ideas. I want to be... (2 Replies)
Discussion started by: capitanui
2 Replies

2. UNIX for Advanced & Expert Users

System/Network Administration Tools

Sorry for making this post so generic. I'm trying to see if there are tools that exist that look at local network/system configurations and find problems... for example: - NTP server configured that cannot be reached (can cause the system to drift because nobody is alerted to the fact that the... (0 Replies)
Discussion started by: jjinno
0 Replies

3. High Performance Computing

Solaris 10 and OpenSolaris : Web Based Management tools and Sun Cluster installation

Gurus, I have several questions : 1. Does Solaris 10/OpenSolaris has some kind of web based management tools ? Currently I am using WebMin. It worked fine, however I am very curious to use the tools provided by Sun Microsystem. Please advise for package name and how to activate.... (0 Replies)
Discussion started by: Zepiroth
0 Replies

4. SCO

UNIX Command line administration and Tools

Hi Everyone I have a few things i need help with in SCO-UNIXWARE 7.1.4 that the version am running. I am an ex-Debian user and i am finding that UNIXWARE is not the cup of Coffee i like I would like to know it the following are available or are there substitutes a locate command - a... (1 Reply)
Discussion started by: Han.nlo
1 Replies

5. Linux

Free MySQL administration console

Hi all! I am looking for a good FREE front end, that is known to work with MySQL 4.1.8a, suitable for performing administration tasks. I thank you in advance... (1 Reply)
Discussion started by: aitor314
1 Replies
Login or Register to Ask a Question
OPTIONS COMMON TO 
MY(1) MySQL Database System OPTIONS COMMON TO MY(1) NAME
ndb-common-options - MySQL Cluster Common Program Options DESCRIPTION
All MySQL Cluster programs accept the options described in this section, with the following exceptions: o mysqld o ndb_print_backup_file o ndb_print_schema_file o ndb_print_sys_file Users of earlier MySQL Cluster versions should note that some of these options have been changed to make them consistent with one another as well as with mysqld. You can use the --help option with any MySQL Cluster program--with the exception of ndb_print_backup_file, ndb_print_schema_file, and ndb_print_sys_file--to view a list of the options which the program supports. The options in the following table are common to all MySQL Cluster executables (except those noted previously in this section). Table 17.29. Common MySQL Cluster Program Options and Variables: MySQL Cluster NDB 7.2 +------------------------------------+-------------------------------------------------------+-------------------------------------+ |Format | Description | Added / Removed | +------------------------------------+-------------------------------------------------------+-------------------------------------+ | | Display help message and exit | | | --help, | | All MySQL 5.5 based releases | | | | | | --usage, | | | | | | | | -? | | | +------------------------------------+-------------------------------------------------------+-------------------------------------+ | | Set connection string for connecting | | | --ndb- | to ndb_mgmd. Syntax: | All MySQL 5.5 based releases | | connectstring=connectstring, | [nodeid=<id>;][host=]<hostname>[:<port>]. | | | | Overrides entries | | | --connect- | specified in NDB_CONNECTSTRING or | | | string=connectstring, | my.cnf. | | | | | | | -c | | | +------------------------------------+-------------------------------------------------------+-------------------------------------+ | | Set the host (and port, if desired) for connecting to | | | --ndb-mgmd-host=host[:port] | the management | All MySQL 5.5 based releases | | | server | | +------------------------------------+-------------------------------------------------------+-------------------------------------+ | | Set node id for this node | | | --ndb-nodeid=# | | All MySQL 5.5 based releases | +------------------------------------+-------------------------------------------------------+-------------------------------------+ | | Select nodes for transactions in a more optimal way | | | --ndb-optimized-node- | | All MySQL 5.5 based releases | | selection | | | +------------------------------------+-------------------------------------------------------+-------------------------------------+ | | Directory where character sets are | | | --character-sets-dir=path | | All MySQL 5.5 based releases | +------------------------------------+-------------------------------------------------------+-------------------------------------+ | | Enable output from debug calls. Can be used only for | | | --debug=options | versions compiled | All MySQL 5.5 based releases | | | with debugging enabled | | +------------------------------------+-------------------------------------------------------+-------------------------------------+ | | Write core on errors (defaults to TRUE in debug | | | --core-file | builds) | All MySQL 5.5 based releases | +------------------------------------+-------------------------------------------------------+-------------------------------------+ | | Output version information and exit | | | --version, | | All MySQL 5.5 based releases | | | | | | -V | | | +------------------------------------+-------------------------------------------------------+-------------------------------------+ For options specific to individual MySQL Cluster programs, see Section 17.4, "MySQL Cluster Programs". See Section 17.3.4.2, "MySQL Server Options for MySQL Cluster", for mysqld options relating to MySQL Cluster. o --help, --usage, -? +--------------------+-----------+ |Command-Line Format | --help | +--------------------+-----------+ | | --usage | +--------------------+-----------+ | | -? | +--------------------+-----------+ Prints a short list with descriptions of the available command options. o --character-sets-dir=name +--------------------+---------------------------+ |Command-Line Format | --character-sets-dir=path | +--------------------+---------------------------+ | | Permitted Values | | +-----------+---------------+ | | Type | file name | | +-----------+---------------+ | | Default | | +--------------------+-----------+---------------+ Tells the program where to find character set information. o --ndb-connectstring=connect_string, --connect-string=connect_string, -c connect_string +--------------------+-----------------------------------+ |Command-Line Format | --ndb-connectstring=connectstring | +--------------------+-----------------------------------+ | | --connect-string=connectstring | +--------------------+-----------------------------------+ | | -c | +--------------------+-----------------------------------+ | | Permitted Values | | +------------+----------------------+ | | Type | string | | +------------+----------------------+ | | Default | localhost:1186 | +--------------------+------------+----------------------+ This option takes a MySQL Cluster connection string that specifies the management server for the application to connect to, as shown here: shell> ndbd --ndb-connectstring="nodeid=2;host=ndb_mgmd.mysql.com:1186" For more information, see Section 17.3.2.3, "MySQL Cluster Connection Strings". o --core-file +--------------------+-------------------+ |Command-Line Format | --core-file | +--------------------+-------------------+ | | Permitted Values | | +---------+---------+ | | Type | boolean | | +---------+---------+ | | Default | FALSE | +--------------------+---------+---------+ Write a core file if the program dies. The name and location of the core file are system-dependent. (For MySQL Cluster programs nodes running on Linux, the default location is the program's working directory--for a data node, this is the node's DataDir.) For some systems, there may be restrictions or limitations; for example, it might be necessary to execute ulimit -c unlimited before starting the server. Consult your system documentation for detailed information. If MySQL Cluster was built using the --debug option for configure, then --core-file is enabled by default. For regular builds, --core-file is disabled by default. o --debug[=options] +--------------------+----------------------------------------+ |Command-Line Format | --debug=options | +--------------------+----------------------------------------+ | | Permitted Values | | +---------+------------------------------+ | | Type | string | | +---------+------------------------------+ | | Default | d:t:O,/tmp/ndb_restore.trace | +--------------------+---------+------------------------------+ This option can be used only for versions compiled with debugging enabled. It is used to enable output from debug calls in the same manner as for the mysqld process. o --ndb-mgmd-host=host[:port] +--------------------+-----------------------------+ |Command-Line Format | --ndb-mgmd-host=host[:port] | +--------------------+-----------------------------+ |Option-File Format | ndb-mgmd-host | +--------------------+-----------------------------+ | | Permitted Values | | +----------+------------------+ | | Type | string | | +----------+------------------+ | | Default | localhost:1186 | +--------------------+----------+------------------+ Can be used to set the host and port number of a single management server for the program to connect to. If the program requires node IDs or references to multiple management servers (or both) in its connection information, use the --ndb-connectstring option instead. o --ndb-nodeid=# +--------------------+-------------------+ |Command-Line Format | --ndb-nodeid=# | +--------------------+-------------------+ | | Permitted Values | | +---------+---------+ | | Type | numeric | | +---------+---------+ | | Default | 0 | +--------------------+---------+---------+ Sets this node's MySQL Cluster node ID. The range of permitted values depends on the node's type (data, management, or API) and the MySQL Cluster software version. See Section 17.1.6.2, "Limits and Differences of MySQL Cluster from Standard MySQL Limits", for more information. o --ndb-optimized-node-selection +--------------------+--------------------------------+ |Command-Line Format | --ndb-optimized-node-selection | +--------------------+--------------------------------+ | | Permitted Values | | +--------------+-----------------+ | | Type |boolean | | +--------------+-----------------+ | | Default |TRUE | +--------------------+--------------+-----------------+ Optimize selection of nodes for transactions. Enabled by default. o --version, -V +--------------------+-----------+ |Command-Line Format | --version | +--------------------+-----------+ | | -V | +--------------------+-----------+ Prints the MySQL Cluster version number of the executable. The version number is relevant because not all versions can be used together, and the MySQL Cluster startup process verifies that the versions of the binaries being used can co-exist in the same cluster. This is also important when performing an online (rolling) software upgrade or downgrade of MySQL Cluster. See Section 17.5.5, "Performing a Rolling Restart of a MySQL Cluster"), for more information. COPYRIGHT
Copyright (C) 1997, 2014, Oracle and/or its affiliates. All rights reserved. This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This documentation 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 General Public License for more details. You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/. SEE ALSO
For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online at http://dev.mysql.com/doc/. AUTHOR
Oracle Corporation (http://dev.mysql.com/). MySQL 5.5 01/30/2014 OPTIONS COMMON TO MY(1)