[MDEV-631] LP:781320 - 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs Created: 2011-05-11 Updated: 2014-03-03 Resolved: 2014-03-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Dave Brady (Inactive) | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | Launchpad | ||
| Attachments: |
|
| Description |
|
We use the FederatedX engine exclusively for SELECTs. Local (MyISAM) tables are populated with INSERT INTO ... SELECT FROM <Federated table>. Aggregation and other querying is done against the local tables. Memory is almost always being leaked by the SELECTs. Successive queries usually cause unallocated RAM to be consumed, instead of reusing that which had been already allocated by mysqld. The box eventually starts to page, at which point the instance needs to be restarted. |
| Comments |
| Comment by Dave Brady (Inactive) [ 2011-05-11 ] |
|
Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs This memory leak is really the only issue with it that is hurting us. Hopefully an easy solution will be found! |
| Comment by CaptTofu (Inactive) [ 2011-09-08 ] |
|
Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs |
| Comment by CaptTofu (Inactive) [ 2011-09-08 ] |
|
Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs |
| Comment by Dave Brady (Inactive) [ 2011-09-08 ] |
|
Re: [Bug 781320] Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs The result sets can be fairly large: 10 GB would not be uncommon (or even On Thu, Sep 8, 2011 at 9:26 AM, CaptTofu <patg@patg.net> wrote: > Hi - btw - how big are the result sets you have using your selects? Just – |
| Comment by Rasmus Johansson (Inactive) [ 2011-09-08 ] |
|
Launchpad bug id: 781320 |