Re: mysql V 8.0.12 and mysqdump

2019-02-14 Thread Walter Harms



> Halaasz Saandor  hat am 9. Februar 2019 um 10:01 geschrieben:
> 
> 
> 2019/02/08 10:32 ... Walter Harms:
> > Hello list,
> > i run into an unexpected problem with mysqldump:
> > 
> > mysqldump --version
> > mysqldump  Ver 8.0.12 for Linux on x86_64 (MySQL Community Server - GPL)
> > 
> > 
> > when i try it results in:
> > mysqldump: Error: 'Lost connection to MySQL server during query' when trying
> > to
> > dump tablespaces
> > mysqldump: Couldn't execute 'SHOW VARIABLES LIKE 'ndbinfo\_version'': MySQL
> > server has gone away (2006)
> 
> I regulary hav this problem with the command-line client (mysql.exe) and 
> when I asked R H gave this answer (and with the command-line client it 
> is much less imporant):
> 
>  Forwarded Message 


I found a solution with this (to set for mysqld in my.cnf):
wait_timeout = 31536000

It sets the time out very high and mysqldump can now complet the query.

personaly i would say this is not a propper solution as it does not solve
the problem of an sql statement taking 15min to complet.

re,
 wh

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



Re: mysql V 8.0.12 and mysqdump

2019-02-09 Thread Walter Harms



> Halaasz Saandor  hat am 9. Februar 2019 um 10:01 geschrieben:
> 
> 
> 2019/02/08 10:32 ... Walter Harms:
> > Hello list,
> > i run into an unexpected problem with mysqldump:
> > 
> > mysqldump --version
> > mysqldump  Ver 8.0.12 for Linux on x86_64 (MySQL Community Server - GPL)
> > 
> > 
> > when i try it results in:
> > mysqldump: Error: 'Lost connection to MySQL server during query' when trying
> > to
> > dump tablespaces
> > mysqldump: Couldn't execute 'SHOW VARIABLES LIKE 'ndbinfo\_version'': MySQL
> > server has gone away (2006)
> 
> I regulary hav this problem with the command-line client (mysql.exe) and 
> when I asked R H gave this answer (and with the command-line client it 
> is much less imporant):
> 
>  Forwarded Message 
> Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during 
> query
> Date: Mon, 06 Jan 2014 17:07:45 +0100
> From: Reindl Harald 
> 
> 
> Am 06.01.2014 15:36, schrieb h...@tbbs.net:
>  > Now that I installed 5.6.14 on our Vista machine, when using "mysql" 
> I often see that error-message, which under 5.5.8 I never saw. What is 
> going on?
> 
> what about look in the servers logfiles
> most likely "max_allowed_packet" laughable low
> 

I do not thing so,
it is onvoius that the sql statement i postet is rediciusly slow, causing
mysqldump to terminate the connection. What anoys me most is the fact that
the result is empty. So i could remove it from the code, but i have no idea
about the consequences.

NTL i will try max_allowed_packet and see what will happen.

re,
 wh

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



Re: mysql V 8.0.12 and mysqdump

2019-02-09 Thread Halaasz Saandor

2019/02/08 10:32 ... Walter Harms:

Hello list,
i run into an unexpected problem with mysqldump:

mysqldump --version
mysqldump  Ver 8.0.12 for Linux on x86_64 (MySQL Community Server - GPL)


when i try it results in:
mysqldump: Error: 'Lost connection to MySQL server during query' when trying to
dump tablespaces
mysqldump: Couldn't execute 'SHOW VARIABLES LIKE 'ndbinfo\_version'': MySQL
server has gone away (2006)


I regulary hav this problem with the command-line client (mysql.exe) and 
when I asked R H gave this answer (and with the command-line client it 
is much less imporant):


 Forwarded Message 
Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during 
query

Date: Mon, 06 Jan 2014 17:07:45 +0100
From: Reindl Harald 


Am 06.01.2014 15:36, schrieb h...@tbbs.net:
> Now that I installed 5.6.14 on our Vista machine, when using "mysql" 
I often see that error-message, which under 5.5.8 I never saw. What is 
going on?


what about look in the servers logfiles
most likely "max_allowed_packet" laughable low

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



mysql V 8.0.12 and mysqdump

2019-02-08 Thread Walter Harms
Hello list,
i run into an unexpected problem with mysqldump:

mysqldump --version
mysqldump  Ver 8.0.12 for Linux on x86_64 (MySQL Community Server - GPL)


when i try it results in:
mysqldump: Error: 'Lost connection to MySQL server during query' when trying to
dump tablespaces
mysqldump: Couldn't execute 'SHOW VARIABLES LIKE 'ndbinfo\_version'': MySQL
server has gone away (2006)


I seems it get stuck in this query:

 explain SELECT LOGFILE_GROUP_NAME, FILE_NAME, TOTAL_EXTENTS, INITIAL_SIZE,
ENGINE, EXTRA FROM INFORMATION_SCHEMA.FILES WHERE FILE
_TYPE = 'UNDO LOG' AND FILE_NAME IS NOT NULL AND LOGFILE_GROUP_NAME IS NOT NULL
AND LOGFILE_GROUP_NAME IN (SELECT DISTINCT LOGFILE_GROUP
_NAME FROM INFORMATION_SCHEMA.FILES WHERE FILE_TYPE = 'DATAFILE' AND
TABLESPACE_NAME IN (SELECT DISTINCT TABLESPACE_NAME FROM INFORMATIO
N_SCHEMA.PARTITIONS WHERE TABLE_SCHEMA IN ('kpc'))) GROUP BY LOGFILE_GROUP_NAME,
FILE_NAME, ENGINE, TOTAL_EXTENTS, INITIAL_SIZE ORDER BY
 LOGFILE_GROUP_NAME;
++-+-+++-+-+-+--
+---+--+---+
| id | select_type | table   | partitions | type   | possible_keys   |
key | key_len | ref  
| rows  | filtered | Extra
|
++-+-+++-+-+-+--
+---+--+---+
|  1 | SIMPLE  | cat | NULL   | index  | PRIMARY |
name| 194 | NULL 
| 1 |   100.00 | Using index; Using temporary; Using filesort; Start
temporary |
|  1 | SIMPLE  | sch | NULL   | eq_ref | PRIMARY,catalog_id  |
catalog_id  | 202 | mysql.cat.id,const   
| 1 |   100.00 | Using index
  |
|  1 | SIMPLE  | tbl | NULL   | ref| schema_id   |
schema_id   | 8   | mysql.sch.id 
|78 |   100.00 | Using where
  |
|  1 | SIMPLE  | part| NULL   | ref| table_id,table_id_2 |
table_id| 8   | mysql.tbl.id 
|   597 |10.00 | Using where
  |
|  1 | SIMPLE  | part_ts | NULL   | eq_ref | PRIMARY |
PRIMARY | 8   | mysql.part.tablespace_id 
| 1 |   100.00 | NULL
 |
|  1 | SIMPLE  | ts  | NULL   | ALL| PRIMARY |
NULL| NULL| NULL 
| 12605 |   100.00 | Using join buffer (Block Nested Loop)
|
|  1 | SIMPLE  | tsf | NULL   | ref| tablespace_id   |
tablespace_id   | 8   | mysql.ts.id  
| 1 |   100.00 | Using where
  |
|  1 | SIMPLE  | sub_part| NULL   | ref| parent_partition_id |
parent_partition_id | 9   | mysql.part.id
| 13152 |   100.00 | NULL
 |
|  1 | SIMPLE  | sub_part_ts | NULL   | eq_ref | PRIMARY |
PRIMARY | 8   | mysql.sub_part.tablespace
_id | 1 |   100.00 | Using where
  |
|  1 | SIMPLE  | ts  | NULL   | eq_ref | PRIMARY,name|
name| 779 | func 
| 1 |   100.00 | Using where
  |
|  1 | SIMPLE  | tsf | NULL   | ref| tablespace_id   |
tablespace_id   | 8   | mysql.ts.id  
| 1 |   100.00 | Using where; End temporary
   |
++-+-+++-+-+-+--
+---+--+---+

The probelm seems to happen only when i dump the whole database, single tables
are ok.

re,
 wh

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql