ImageVerifierCode 换一换
格式:DOCX , 页数:35 ,大小:199.68KB ,
资源ID:2727286      下载积分:3 金币
快捷下载
登录下载
邮箱/手机:
温馨提示:
快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。 如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝    微信支付   
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【https://www.bingdoc.com/d-2727286.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录   QQ登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(mysql安装与主从复制说明文档.docx)为本站会员(b****2)主动上传,冰点文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知冰点文库(发送邮件至service@bingdoc.com或直接QQ联系客服),我们立即给予删除!

mysql安装与主从复制说明文档.docx

1、mysql安装与主从复制说明文档一 Linux下安装mysql数据库1安装netsarangxmanager.exe,使用Xshell连接服务器,Xftp拷贝文件。2拷贝安装文件Xftp把f文件拷贝到/etc 目录下,mysqlrpm拷贝到/root目录下。(附录:f文件内容:datadir = /app/data 为数据库文件目录设定)#BEGIN CONFIG INFO#DESCR: 4GB RAM, InnoDB only, ACID, few connections, heavy queries#TYPE: SYSTEM#END CONFIG INFO# This is a MySQL

2、 example config file for systems with 4GB of memory# running mostly MySQL using InnoDB only tables and performing complex# queries with few connections.# # MySQL programs look for option files in a set of# locations which depend on the deployment platform.# You can copy this option file to one of th

3、ose# locations. For information about these locations, see:# # In this file, you can use all long options that a program supports.# If you want to know which options a program supports, run the program# with the -help option.# More detailed information about the individual options can also be# found

4、 in the manual.# The following options will be read by MySQL client applications.# Note that only client applications shipped by MySQL are guaranteed# to read this section. If you want your own MySQL client program to# honor these values, you need to specify it as an option during the# MySQL client

5、library initialization.#client#password = your_passwordport = 3306socket = /var/lib/mysql/mysql.sock#default-character-set=gbk# * Application-specific options follow here *# The MySQL server#mysqld#skip-grant-tables# generic configuration optionsport = 3306socket = /var/lib/mysql/mysql.sockdatadir =

6、 /app/data# back_log is the number of connections the operating system can keep inlower_case_table_name=1sql_mode=oracleinnodb_file_per_table=1character_set_server=utf8skip-host-cacheskip-name-resolve# the listen queue, before the MySQL connection manager thread has# processed them. If you have a ve

7、ry high connection rate and experience# connection refused errors, you might need to increase this value.# Check your OS documentation for the maximum value of this parameter.# Attempting to set back_log higher than your operating system limit# will have no effect.back_log = 50#skip-grant-tables # D

8、ont listen on a TCP/IP port at all. This can be a security# enhancement, if all processes that need to connect to mysqld run# on the same host. All interaction with mysqld must be made via Unix# sockets or named pipes.# Note that using this option without enabling named pipes on Windows# (via the en

9、able-named-pipe option) will render mysqld useless!#skip-networking# The maximum amount of concurrent sessions the MySQL server will# allow. One of these connections will be reserved for a user with# SUPER privileges to allow the administrator to login even if the# connection limit has been reached.

10、max_connections = 32000slow-query-log# Maximum amount of errors allowed per host. If this limit is reached,# the host will be blocked from connecting to the MySQL server until# FLUSH HOSTS has been run or the server was restarted. Invalid# passwords and other errors during the connect phase result i

11、n# increasing this value. See the Aborted_connects status variable for# global counter.max_connect_errors = 10# The number of open tables for all threads. Increasing this value# increases the number of file descriptors that mysqld requires.# Therefore you have to make sure to set the amount of open

12、files# allowed to at least 4096 in the variable open-files-limit in# section mysqld_safetable_open_cache = 4096# Enable external file level locking. Enabled file locking will have a# negative impact on performance, so only use it in case you have# multiple database instances running on the same file

13、s (note some# restrictions still apply!) or if you use other software relying on# locking MyISAM tables on file level.#external-locking# The maximum size of a query packet the server can handle as well as# maximum query size server can process (Important when working with# large BLOBs). enlarged dyn

14、amically, for each connection.max_allowed_packet = 16M# The size of the cache to hold the SQL statements for the binary log# during a transaction. If you often use big, multi-statement# transactions you can increase this value to get more performance. All# statements from transactions are buffered i

15、n the binary log cache and# are being written to the binary log at once after the COMMIT. If the# transaction is larger than this value, temporary file on disk is used# instead. This buffer is allocated per connection on first update# statement in transactionbinlog_cache_size = 16M # modified by liu

16、gh2012.03.24 14:30#binlog_cache_size = 1M# Maximum allowed size for a single HEAP (in memory) table. This option# is a protection against the accidential creation of a very large HEAP# table which could otherwise use up all memory resources.max_heap_table_size = 512M# Size of the buffer used for doi

17、ng full table scans.# Allocated per thread, if a full scan is needed.read_buffer_size = 2M# When reading rows in sorted order after a sort, the rows are read# through this buffer to avoid disk seeks. You can improve ORDER BY# performance a lot, if set this to a high value.# Allocated per thread, whe

18、n needed.read_rnd_buffer_size = 16M# Sort buffer is used to perform sorts for some ORDER BY and GROUP BY# queries. If sorted data does not fit into the sort buffer, a disk# based merge sort is used instead - See the Sort_merge_passes# status variable. Allocated per thread if sort is needed.sort_buff

19、er_size = 1024M# This buffer is used for the optimization of full JOINs (JOINs without# indexes). Such JOINs are very bad for performance in most cases# anyway, but setting this variable to a large value reduces the# performance impact. See the Select_full_join status variable for a# count of full J

20、OINs. Allocated per thread if full join is foundjoin_buffer_size = 256M# How many threads we should keep in a cache for reuse. When a client# disconnects, the clients threads are put in the cache if there arent# more than thread_cache_size threads from before. This greatly reduces# the amount of thr

21、ead creations needed if you have a lot of new# connections. (Normally this doesnt give a notable performance# improvement if you have a good thread implementation.)thread_cache_size = 1024# This permits the application to give the threads system a hint for the# desired number of threads that should

22、be run at the same time. This# value only makes sense on systems that support the thread_concurrency()# function call (Sun Solaris, for example).# You should try number of CPUs*(2.4) for thread_concurrencythread_concurrency = 48# Query cache is used to cache SELECT results and later return them# wit

23、hout actual executing the same query once again. Having the query# cache enabled may result in significant speed improvements, if your# have a lot of identical queries and rarely changing tables. See the# Qcache_lowmem_prunes status variable to check if the current value# is high enough for your loa

24、d.# Note: In case your tables change very often or if your queries are# textually different every time, the query cache may result in a# slowdown instead of a performance improvement.query_cache_size = 1024M# Only cache result sets that are smaller than this limit. This is to# protect the query cach

25、e of a very large result set overwriting all# other query results.query_cache_limit = 2M# Minimum word length to be indexed by the full text search index.# You might wish to decrease it if you need to search for shorter words.# Note that you need to rebuild your FULLTEXT index, after you have# modif

26、ied this value.ft_min_word_len = 4# If your system supports the memlock() function call, you might want to# enable this option while running MySQL to keep it locked in memory and# to avoid potential swapping out in case of high memory pressure. Good# for performance.#memlock# Table type which is use

27、d by default when creating new tables, if not# specified differently during the CREATE TABLE statement.#default-storage-engine = InnoDB# Thread stack size to use. This amount of memory is always reserved at# connection time. MySQL itself usually needs no more than 64K of# memory, while if you use yo

28、ur own stack hungry UDF functions or your# OS requires more stack for some operations, you might need to set this# to a higher value.thread_stack = 192K# Set the default transaction isolation level. Levels available are:# READ-UNCOMMITTED, READ-COMMITTED, REPEATABLE-READ, SERIALIZABLE transaction_is

29、olation = REPEATABLE-READ# transaction_isolation = READ-COMMITTED# Maximum size for internal (in-memory) temporary tables. If a table# grows larger than this value, it is automatically converted to disk# based table This limitation is for a single table. There can be many# of them.tmp_table_size = 5

30、12M# Enable binary logging. This is required for acting as a MASTER in a# replication configuration. You also need the binary log if you need# the ability to do point in time recovery from your latest backup.log-bin=mysql-bin# binary logging format - mixed recommendedbinlog_format=mixed# If youre us

31、ing replication with chained slaves (A-B-C), you need to# enable this option on server B. It enables logging of updates done by# the slave thread into the slaves binary log.#log_slave_updates# Enable the full query log. Every query (even ones with incorrect# syntax) that the server receives will be logged. This is useful for# debugging, it is usually disabled in production use.#log# Print warnings to the error log file. If you have any problem with# MySQL you should

copyright@ 2008-2023 冰点文库 网站版权所有

经营许可证编号:鄂ICP备19020893号-2