blocks|key|2883989|text|新版本的MySQL+WorkBench具有更改特定超时的选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2883990|对于我来说，它位于编辑→首选项→SQL编辑器→数据库管理系统连接读取超时(秒)下:+600|2883991|已将该值更改为6000。|2883992|此外，取消选中限制行，因为每次我想要搜索整个数据集时都会添加限制，这会让人感到厌烦。|2883993|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

New versions of MySQL WorkBench have an option to change specific timeouts.

For me it was under Edit → Preferences → SQL Editor → DBMS connection read time out (in seconds): 600

Changed the value to 6000.

Also unchecked limit rows as putting a limit in every time I want to search the whole data set gets tiresome.

blocks|key|230376|text|如果您的查询包含blob数据，则可以通过应用my.ini+change+as+proposed+in+this+answer来解决此问题|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|230377|[mysqld]
max_allowed_packet=16M|code-block|syntax|javascript|230378|默认情况下为1M+(允许的最大值为1024M)。如果提供的值不是1024K的倍数，它将自动四舍五入为1024K的最接近的倍数。|230379|虽然引用的线程是关于MySQL错误2006的，但将max_allowed_packet从1M设置为16M确实修复了2013年运行长查询时出现的错误。|230380|对于WAMP用户:您可以在[wampmysqld]部分找到该标志。|230381|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/9479681/985852^0|M|6|10|Q|0|0|0|0|P|I|0|D|C|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|15|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

If your query has blob data, this issue can be fixed by applying a <code>my.ini</code> change <a href="https://stackoverflow.com/a/9479681/985852">as proposed in this answer</a>:

<pre><code>[mysqld]
max_allowed_packet=16M
</code></pre>

By default, this will be 1M (the allowed maximum value is 1024M). If the supplied value is not a multiple of 1024K, it will automatically be rounded to the nearest multiple of 1024K.

While the referenced thread is about the MySQL error 2006, setting the <code>max_allowed_packet</code> from 1M to 16M did fix the 2013 error that showed up for me when running a long query.

For WAMP users: you'll find the flag in the <code>[wampmysqld]</code> section.

blocks|key|227992|text|使用命令行选项net_read_timeout+/+wait_timeout和合适的值(以秒为单位)启动DB服务器-例如：--net_read_timeout=100。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|227993|有关参考，请参阅here和here。|227994|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.mysql.com/doc/refman/5.0/en/gone-away.html|1|http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_wait_timeout^0|7|G|Q|C|1P|M|0|8|4|0|D|4|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]|$9|12|A|13|1|14]]|E|$]]|$1|H|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

Start the DB server with the comandline option <code>net_read_timeout</code> / <code>wait_timeout</code> and a suitable value (in seconds) - for example: <code>--net_read_timeout=100</code>.

For reference see <a href="http://dev.mysql.com/doc/refman/5.0/en/gone-away.html">here</a> and <a href="http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_wait_timeout">here</a>.

blocks|key|3098001|text|将以下内容添加到/etc/mysql/cnf文件中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3098002|innodb_buffer_pool_size+=+64M|code-block|syntax|javascript|3098003|示例：|3098004|key_buffer++++++++++++++=+16M
max_allowed_packet++++++=+16M
thread_stack++++++++++++=+192K
thread_cache_size+++++++=+8
innodb_buffer_pool_size+=+64M|3098005|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Add the following into /etc/mysql/cnf file:

<pre><code>innodb_buffer_pool_size = 64M
</code></pre>

example:

<pre><code>key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
innodb_buffer_pool_size = 64M
</code></pre>

blocks|key|225178|text|SET+@@local.net_read_timeout=360;|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|225179|警告:当您在远程连接中应用它时，以下内容将不起作用：|unstyled|225180|SET+@@global.net_read_timeout=360;|225181|编辑：+360是秒数|offset|length|style|BOLD|225182|entityMap^0|0|0|0|0|3|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$B|C]]|$1|I|3|J|5|F|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|F|7|W|8|@]|9|@]|A|$]]]|P|$]]

<pre><code>SET @@local.net_read_timeout=360;
</code></pre>
Warning: The following will not work when you are applying it in remote connection:
<pre><code>SET @@global.net_read_timeout=360;
</code></pre>
Edit: 360 is the number of seconds

blocks|key|228657|text|您应该将mysql配置文件中的'interactive_timeout‘和'wait_timeout’属性设置为所需的值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|228658|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You should set the 'interactive_timeout' and 'wait_timeout' properties in the mysql config file to the values you need.

blocks|key|230510|text|此错误消息可能有三个原因|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230511|230512|通常这表示网络连接出现问题，如果出现此错误，则应检查网络状况。当作为一个或多个查询的一部分发送数百万行时，“during+query”表单会发生。|ordered-list-item|230513|更少见的是，当客户端尝试初始连接到服务器|230514|时，也会发生此错误|230515|有关更多详细信息+read+>>，请访问|offset|length|230516|blockquote|230517|230518|230519|原因2：|230520|SET+GLOBAL+interactive_timeout=60;|code-block|syntax|javascript|230521|从默认的30秒到60秒或更长|230522|原因3：|230523|SET+GLOBAL+connect_timeout=60;|230524|entityMap|0|LINK|mutability|MUTABLE|url|https://dev.mysql.com/doc/refman/5.7/en/error-lost-connection.html^0|0|0|0|0|0|8|8|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1E|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1F|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1G|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1H|8|@]|9|@$L|1I|M|1J|1|1K]]|A|$]]|$1|N|3|-4|5|O|7|1L|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1O|8|@]|9|@]|A|$]]|$1|T|3|U|5|V|7|1P|8|@]|9|@]|A|$W|X]]|$1|Y|3|Z|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1R|8|@]|9|@]|A|$]]|$1|12|3|13|5|V|7|1S|8|@]|9|@]|A|$W|X]]|$1|14|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B]]]]

There are three likely causes for this error message

<ol>
<li>Usually it indicates network connectivity trouble and you should check the condition of your network if this error occurs frequently</li>
<li>Sometimes the “during query” form happens when millions of rows are being sent as part of one or more queries.</li>
<li>More rarely, it can happen when the client is attempting the initial connection to the server</li>
</ol>

<blockquote>
 For more detail <a href="https://dev.mysql.com/doc/refman/5.7/en/error-lost-connection.html" rel="noreferrer"> read >></a>
</blockquote>

Cause 2 : 

<pre><code>SET GLOBAL interactive_timeout=60;
</code></pre>

from its default of 30 seconds to 60 seconds or longer

Cause 3 :

<pre><code>SET GLOBAL connect_timeout=60;
</code></pre>

blocks|key|229016|text|在我的例子中，将连接超时间隔设置为6000或更高的值不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|229017|我只是做了工作台说我能做的事。|229018|229019|查询从DBMS.Set+0返回数据以跳过读取超时所需的最长时间。|blockquote|229020|229021|229022|在Mac偏好设置->+SQL编辑器->中，转到MySQL+Session+->，将连接读取超时间隔设置为0。|229023|而且它是有效的|229024|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|S|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|O|$]]

In my case, setting the connection timeout interval to 6000 or something higher didn't work. 

I just did what the workbench says I can do.

<blockquote>
 The maximum amount of time the query can take to return data from the DBMS.Set 0 to skip the read timeout.
</blockquote>

On Mac 
Preferences -> SQL Editor -> Go to MySQL Session -> set connection read timeout interval to 0.

And it works

blocks|key|228029|text|只需执行MySQL升级，将重新构建innoDB引擎，并重新构建MySQL正常运行所需的许多表，如performance_schema、information_schema等。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|228030|从您的shell发出以下命令：|228031|sudo+mysql_upgrade+-u+root+-p|code-block|syntax|javascript|228032|entityMap^0|1C|I|1V|I|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Just perform a MySQL upgrade that will re-build innoDB engine along with rebuilding of many tables required for proper functioning of MySQL such as <code>performance_schema</code>, <code>information_schema</code>, etc.

Issue the below command from your shell:

<pre><code>sudo mysql_upgrade -u root -p
</code></pre>

blocks|key|2884035|text|我知道它很旧，但在mac上|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884036|1.+Control-click+your+connection+and+choose+Connection+Properties.
2.+Under+Advanced+tab,+set+the+Socket+Timeout+(sec)+to+a+larger+value.|code-block|syntax|javascript|2884037|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I know its old but on mac 

<pre><code>1. Control-click your connection and choose Connection Properties.
2. Under Advanced tab, set the Socket Timeout (sec) to a larger value.
</code></pre>

blocks|key|2884081|text|如果你在恢复一个大的转储文件的过程中遇到了这个问题，并且可以排除这个问题与网络有关(例如，在本地主机上执行)，那么我的解决方案可能会有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884082|我的mysqldump中至少有一个插入语句太大，mysql无法计算。您可以通过在mysql-cli中输入show+variables+like+"net_buffer_length";来查看此变量。您有三种可能性：|offset|length|style|CODE|2884083|2884084|增加mysql内的转储这将需要服务器重新启动|unordered-list-item|2884085|使用--skip-extended-insert创建转储->，每次插入使用一行虽然这些转储读取起来要好得多这不适合大于1+1GB的大转储，因为它往往非常慢|2884086|使用扩展插入创建转储(这是默认设置)但限制net-buffer_length例如使用--net-buffer_length+NR_OF_BYTES+NR_OF_BYTES小于服务器的net_buffer_length+->我认为这是最好的解决方案，尽管速度较慢，但不需要重新启动服务器。|2884087|2884088|我使用了以下mysqldump命令：mysqldump+--skip-comments+--set-charset+--default-character-set=utf8+--single-transaction+--net-buffer_length+4096+DBX+>+dumpfile|2884089|entityMap^0|0|1G|14|0|0|0|2|M|0|16|V|0|0|I|3L|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|N|3|O|5|K|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$]]

If you experience this problem during the restore of a big dump-file and can rule out the problem that it has anything to do with network (e.g. execution on localhost) than my solution could be helpful.

My mysqldump held at least one INSERT that was too big for mysql to compute. You can view this variable by typing <code>show variables like "net_buffer_length";</code> inside your mysql-cli.
You have three possibilities:

<ul>
<li>increase net_buffer_length inside mysql -> this would need a server restart</li>
<li>create dump with <code>--skip-extended-insert</code>, per insert one line is used -> although these dumps are much nicer to read this is not suitable for big dumps > 1GB because it tends to be very slow</li>
<li>create dump with extended inserts (which is the default) but limit the net-buffer_length e.g. with <code>--net-buffer_length NR_OF_BYTES</code> where NR_OF_BYTES is smaller than the server's net_buffer_length -> I think this is the best solution, although slower no server restart is needed.</li>
</ul>

I used following mysqldump command:
 <code>mysqldump --skip-comments --set-charset --default-character-set=utf8 --single-transaction --net-buffer_length 4096 DBX &gt; dumpfile</code>

blocks|key|3097953|text|请尝试取消选中编辑SQL首选项→→查询中的限制行数|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3097954|因为您应该将mysql配置文件中的'interactive_timeout‘和'wait_timeout’属性设置为所需的值。|3097955|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Try please to uncheck limit rows in in Edit → Preferences →SQL Queries 

because You should set the 'interactive_timeout' and 'wait_timeout' properties in the mysql config file to the values you need.

blocks|key|3098077|text|在“编辑”->“首选项”->“SQL编辑器”->“MySQL会话”中更改“读取超时”时间|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3098078|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Change "read time out" time in Edit->Preferences->SQL editor->MySQL session

blocks|key|225463|text|有时候你的SQL-Server会死锁，这个问题我已经遇到过100次了。您可以重新启动计算机/笔记本电脑来重新启动服务器(简单的方法)，或者您可以转到任务管理器>服务>您的服务器名称(对我来说，它是MySQL785之类的)。然后右键单击>重新启动。请尝试再次执行查询。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|225464|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Sometimes your SQL-Server gets into deadlocks, I've been in to this problem like 100 times. You can either restart your computer/laptop to restart server (easy way) OR you can go to task-manager&gt;services&gt;YOUR-SERVER-NAME(for me , it was MySQL785 something like this). And right-click &gt; restart.
Try executing query again.

blocks|key|228790|text|我在加载.csv文件时也遇到了同样的问题。已将文件转换为.sql。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|228791|使用下面的命令，我设法解决了这个问题。|228792|mysql+-u+<user>+-p+-D+<DB+name>+<+file.sql|code-block|syntax|javascript|228793|希望这能有所帮助。|228794|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I got the same issue when loading a .csv file.
Converted the file to .sql.

Using below command I manage to work around this issue.

<pre><code>mysql -u &lt;user&gt; -p -D &lt;DB name&gt; &lt; file.sql
</code></pre>

Hope this would help.

blocks|key|230532|text|如果这里的所有其他解决方案都失败了，请检查syslog+(/var/log/syslog或类似的)，看看在查询过程中服务器是否耗尽了内存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230533|在未配置交换文件的情况下，将innodb_buffer_pool_size设置为离物理内存太近时出现此问题。MySQL+recommends+for+a+database+specific+server+setting+innodb_buffer_pool_size+at+a+max+of+around+80%25+of+physical+memory，我将其设置为90%25左右，内核正在杀死mysql进程。将innodb_buffer_pool_size回调到80%25左右，这解决了问题。|offset|length|230534|entityMap|0|LINK|mutability|MUTABLE|url|https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_buffer_pool_size^0|0|1I|3D|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

If all the other solutions here fail - check your syslog (/var/log/syslog or similar) to see if your server is running out of memory during the query.

Had this issue when innodb_buffer_pool_size was set too close to physical memory without a swapfile configured. <a href="https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_buffer_pool_size" rel="nofollow noreferrer">MySQL recommends for a database specific server setting innodb_buffer_pool_size at a max of around 80% of physical memory</a>, I had it set to around 90%, the kernel was killing the mysql process. Moved innodb_buffer_pool_size back down to around 80% and that fixed the issue.

blocks|key|2884488|text|转到工作台编辑数据库首选项→→编辑器→数据库连接读取超时:最多3000。错误不再出现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884489|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Go to Workbench Edit → Preferences → SQL Editor → DBMS connections read time out : Up to 3000.
The error no longer occurred.

blocks|key|230526|text|我也面临着同样的问题。我相信当你有更大的表的外键时就会发生这种情况(这需要时间)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230527|我尝试在不使用外键声明的情况下再次运行create+table语句，发现它是有效的。|230528|然后，在创建表之后，我使用ALTER+table+query添加了外键约束。|230529|希望这能帮助到一些人。|230530|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I faced this same issue. I believe it happens when you have foreign keys to larger tables (which takes time).

I tried to run the create table statement again without the foreign key declarations and found it worked. 

Then after creating the table, I added the foreign key constrains using ALTER TABLE query.

Hope this will help someone.

blocks|key|228145|text|这发生在我身上，因为我的innodb_buffer_pool_size被设置为大于服务器上可用的内存大小。由于这一点，事情被中断了，它发出了这个错误。修复方法是使用正确的innodb_buffer_pool_size设置更新my.cnf。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|228146|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This happened to me because my innodb_buffer_pool_size was set to be larger than the RAM size available on the server. Things were getting interrupted because of this and it issues this error. The fix is to update my.cnf with the correct setting for innodb_buffer_pool_size.

blocks|key|2884352|text|请转至：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884353|编辑SQL首选项->+->编辑器|2884354|在这里，您可以看到"MySQL+Session“组中的三个字段，您现在可以在其中设置新的连接间隔(以秒为单位)。|2884355|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Go to:

Edit -> Preferences -> SQL Editor

In there you can see three fields in the "MySQL Session" group, where you can now set the new connection intervals (in seconds).

blocks|key|230578|text|原来我们的防火墙规则阻止了我与MYSQL的连接。在取消允许连接的防火墙策略之后，我能够成功地导入模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230579|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Turns out our firewall rule was blocking my connection to MYSQL. After the firewall policy is lifted to allow the connection i was able to import the schema successfully.

blocks|key|3098341|text|我也有同样的问题--但对我来说，解决方案是一个权限过于严格的数据库用户。我必须在mysql表上允许Execute功能。在允许之后，我再也不会断开连接|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3098342|entityMap^0|14|5|1D|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I had the same problem - but for me the solution was a DB user with too strict permissions.
I had to allow the <code>Execute</code> ability on the <code>mysql</code> table. After allowing that I had no dropping connections anymore

blocks|key|3098366|text|首先检查索引是否到位。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3098367|SELECT+*
FROM+INFORMATION_SCHEMA.STATISTICS
WHERE+TABLE_SCHEMA+=+'<schema>'|code-block|syntax|javascript|3098368|entityMap^0|4|2|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Check if the indexes are in place first.

<pre><code>SELECT *
FROM INFORMATION_SCHEMA.STATISTICS
WHERE TABLE_SCHEMA = '&lt;schema&gt;'
</code></pre>

blocks|key|2884439|text|我在运行一个存储过程时遇到了这个问题--它在数据库的一个表中创建了很多行。我可以看到错误发生在时间跨过30秒的边界之后。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884440|我尝试了其他答案中的所有建议。然而，我相信其中一些是有帮助的--对我来说，真正让它工作的是从工作台切换到SequelPro。|2884441|我猜这是我在Workbench中找不到的一些客户端连接。也许这对其他人也有帮助？|2884442|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I ran into this while running a stored proc- which was creating lots of rows into a table in the database.
I could see the error come right after the time crossed the 30 sec boundary.

I tried all the suggestions in the other answers. I am sure some of it helped , however- what really made it work for me was switching to SequelPro from Workbench.

I am guessing it was some client side connection that I could not spot in Workbench.
Maybe this will help someone else as well ?

blocks|key|3098407|text|如果您使用的是SQL+wrench，您可以尝试使用索引，通过将索引添加到表中，要添加索引，请单击表上的扳手(扳手)符号，它将打开表的设置，在下面，单击索引视图，键入索引名称并将类型设置为索引，在索引列中，选择表中的主列。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3098408|对其他表上的其他主键执行相同的步骤。|3098409|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you are using SQL Work Bench, you can try using Indexing, by adding an index to your tables, to add an index, click on the wrench(spanner) symbol on the table, it should open up the setup for the table, below, click on the index view, type an index name and set the type to index, In the index columns, select the primary column in your table.

Do the same step for other primary keys on other tables.

blocks|key|225408|text|对于那些使用SSH连接到他们的MySQL数据库的人，这里似乎缺少一个答案。你需要勾选两个地方，而不是其他答案建议的1：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|225409|工作台编辑SQL首选项→→编辑器→DBMS|225410|工作台编辑→首选项→SSH→超时|225411|我的默认SSH超时设置得非常低，这导致了一些(但显然不是全部)超时问题。之后，不要忘记重新启动MySQL工作台！|225412|最后，联系你的数据库管理员，让他们通过my.conf+%2B+mysql重启来增加mysql中的wait_timeout和interactive_timeout属性，或者在重启mysql不可行的情况下进行全局设置，这可能是值得的。|225413|希望这能有所帮助！|225414|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

There seems to be an answer missing here for those using SSH to connect to their MySQL database. You need to check two places not 1 as suggested by other answers:

Workbench Edit → Preferences → SQL Editor → DBMS

Workbench Edit → Preferences → SSH → Timeouts

My default SSH Timeouts were set very low and causing some (but apparently not all) of my timeout issues. After, don't forget to restart MySQL Workbench!

Last, it may be worth contacting your DB Admin and asking them to increase wait_timeout &amp; interactive_timeout properties in mysql itself via my.conf + mysql restart or doing a global set if restarting mysql is not an option.

Hope this helps!

blocks|key|228295|text|要遵循并确保以下三件事：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|228296|多个查询是否显示丢失的查询您在simultaneously?中使用set+connection?|228297|how？|unordered-list-item|228298|
|228299|如何删除%2B更新查询simultaneously？|228300|228301|答案：|228302|228303|始终尝试删除定义器，因为MySQL创建了自己的定义器，并且如果涉及多个表进行更新，则尝试执行单个查询，因为有时多个查询会在顶部显示丢失的connection|ordered-list-item|228304|Always设置值，但如果其条件不涉及设置值，则在DELETE之后执行。如果对不同的表执行了这两个操作，|228305|将首先使用DELETE，然后使用UPDATE+|228306|228307|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|12|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|16|8|@]|9|@]|A|$]]|$1|R|3|S|5|Q|7|17|8|@]|9|@]|A|$]]|$1|T|3|U|5|Q|7|18|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

Three things to be followed and make sure:

<ol>
<li>Whether multiple queries show lost connection?</li>
<li>how you use set query in MySQL?</li>
<li>how delete + update query simultaneously?</li>
</ol>

Answers:

<ol>
<li>Always try to remove definer as MySQL creates its own definer and if multiple tables involved for updation try to make a single query as sometimes multiple query shows lost connection</li>
<li>Always SET value at the top but after DELETE if its condition doesn't involve SET value.</li>
<li>Use DELETE FIRST THEN UPDATE IF BOTH OF THEM OPERATIONS ARE PERFORMED ON DIFFERENT TABLES</li>
</ol>

blocks|key|230696|text|我有这个错误信息是由于升级Mysql后的一个问题。在我尝试执行任何查询后，错误立即出现|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230697|检查路径/var/log/mysql中的mysql错误日志文件(linux)|offset|length|style|CODE|230698|在我的例子中，将Mysql所有者重新分配到Mysql系统文件夹对我很有效|230699|chown+-R+mysql:mysql+/var/lib/mysql|code-block|syntax|javascript|230700|entityMap^0|0|4|E|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|V|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I had this error message due to a problem after of upgrade Mysql. The error appeared immediately after I tried to do any query
Check mysql error log files in path <code>/var/log/mysql</code> (linux)
In my case reassigning Mysql owner to the Mysql system folder worked for me
<pre><code>chown -R mysql:mysql /var/lib/mysql
</code></pre>

blocks|key|2884687|text|首先建立连接，然后选择您的数据库use+dbname，然后选择源哑source+C:\dumpfile.sql。完成后，\q|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2884688|entityMap^0|G|A|X|M|1O|2|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

Establish connection first
<code>mysql --host=host.com --port=3306 -u username -p</code>
then select your db <code>use dbname</code>
then source dumb <code>source C:\dumpfile.sql</code>.
After it's done <code>\q</code>

blocks|key|230714|text|我的观察是-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230715|当您同时运行MySQL工作台和终端并在终端中运行时，您需要-|230716|SET+AUTOCOMMIT+=+0;|offset|length|style|CODE|230717|或|230718|START+TRANSACTION;|230719|那么你通常会面临这样的问题。|230720|即使在那之后-|230721|SET+AUTOCOMMIT+=+1;|230722|230723|COMMIT;|230724|问题依然存在。|230725|您需要从终端和MYSQL工作台注销，然后重新登录，否则将重新启动。|230726|entityMap^0|0|0|0|J|0|0|0|I|0|0|0|0|J|0|0|0|7|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@$F|15|G|16|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@$F|19|G|1A|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1C|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1D|8|@$F|1E|G|1F|H|I]]|9|@]|A|$]]|$1|T|3|K|5|6|7|1G|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1H|8|@$F|1I|G|1J|H|I]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1L|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|11|$]]

My observation -
when you run MySQL Workbench and terminal together and in terminal you do -
<code>SET AUTOCOMMIT = 0;</code>
OR
<code>START TRANSACTION;</code>
Then you usually face this kind of problem.
And even after -
<code>SET AUTOCOMMIT = 1;</code>
OR
<code>COMMIT;</code>
The problems persists.
You need to logout from both terminal and MYSQL workbench and then login again or else do a reboot.

blocks|key|228754|text|检查关于|type|unstyled|depth|inlineStyleRanges|entityRanges|data|228755|OOM+on+/var/log/messages+,
modify+innodb_buffer_pool_size+value+;+when+load+data+,+use+50%25+of+os+mem+;+|code-block|syntax|javascript|228756|希望这能有所帮助|228757|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

check about 

<pre><code>OOM on /var/log/messages ,
modify innodb_buffer_pool_size value ; when load data , use 50% of os mem ; 
</code></pre>

Hope this helps

blocks|key|230477|text|这通常意味着您“与当前版本的MySQL服务器不兼容”，请参阅mysql_upgrade。我遇到了同样的问题，不得不简单地运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230478|mysql_upgrade+--password文档指出，“每次升级MySQL时都应执行mysql_upgrade”。|230479|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

This usually means that you have "incompatibilities with the current version of MySQL Server", see mysql_upgrade. I ran into this same issue and simply had to run:

mysql_upgrade --password
The documentation states that, "mysql_upgrade should be executed each time you upgrade MySQL".

I got the Error Code: 2013. Lost connection to MySQL server during query error when I tried to add an index to a table using MySQL Workbench. 
I noticed also that it appears whenever I run long query. 

Is there away to increase the timeout value?

Error Code: 2013. Lost connection to MySQL server during query

数据库管理系统

数据库管理

日志文件

SQL数据库

数据库

服务器

防火墙

MySQL

我得到了错误代码: 2013。当我尝试使用MySQL工作台向表中添加索引时，在查询期间丢失与MySQL服务器的连接时出现错误。我还注意到，每当我运行长查询时，它都会出现。是否有办法增加超时值？

问错误码: 2013。查询过程中失去与MySQL服务器的连接
EN

回答 32

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误码: 2013。查询过程中失去与MySQL服务器的连接EN

回答 32

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误码: 2013。查询过程中失去与MySQL服务器的连接
EN