[MDEV-13480] [Upgrade 10.1.25-MariaDB] Lose index from large table Created: 2017-08-09  Updated: 2017-09-29  Resolved: 2017-09-29

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.1.25
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Toan Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Centos 7 - 64bit


 Description   
  • When i run "yum update", MariaDB upgrade from 10.0.* to 10.1.25
  • TokuDB (5.6 not upgrade)
  • Small Problem:
  • Can't start service mariadb, folder source on "/home/mariadb". I fixed by "ProtectHome: Off"
  • Big Problem:
  • Table engine TokuDB, with large data > 300GB
  • When query select with too slow, i checked indexes of table. it's has indexes (A,B) for select query
  • I explained query, It's normal with indexes
  • BUT query return large rows
  • Example with one query before, after upgrade:
  • Normal (not upgrade): 10000 rows
  • BUT (upgraded): 1000,000 rows
  • Then server slow down.

Please help me.
Many thanks

 Comments   
Comment by Elena Stepanova [ 2017-08-31 ]

"Small problem" is not a bug – yes, home is protected, and if you really want to have a database there, which is not a standard setup, you need to "unprotect" it.

For the "Big problem" – sorry, I don't understand what you are trying to say there.
1000 /1000,000 rows what? Result set? examined? filtered? What does it mean, "query return large rows"?

If you think you have encountered a bug, please try to describe it in some comprehensible way – with configuration files, table structures (SHOW CREATE TABLE and SHOW INDEX output), the problematic query, execution plans, actual result set vs expected result set.
On the other hand, if you are seeking TokuDB tuning advice, please ask the question on public mailing lists.

Generated at Thu Feb 08 08:05:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.