Bug #33250 | SELECT * FROM really_big_federated_table eats lots of virtual memory (OOM) | ||
---|---|---|---|
Submitted: | 14 Dec 2007 17:17 | Modified: | 21 Dec 2009 5:00 |
Reporter: | Michael Bacarella | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Federated storage engine | Severity: | S2 (Serious) |
Version: | mysql-5.1.22-rc | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | 5.1, crash, federated, OOM, swap |
[14 Dec 2007 17:17]
Michael Bacarella
[17 Dec 2007 14:09]
Susanne Ebrecht
The crash occurs because of too less RAM. Do I understand this right?
[17 Dec 2007 17:20]
Michael Bacarella
Yes. If you have tables that are hundreds of gigabytes in size, you must have hundreds of gigabytes of RAM (or swap space) if you want to use federated tables.
[4 Apr 2012 15:45]
K Vargo
Yes, we're seeing this too... 5.1.62. I can't tell, but it appears as though this isn't being worked on? I agree that the FEDERATED engine should handle the FEDERATED content in a more sane manner than filling up all available memory.