Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-631

LP:781320 - 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      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.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            davebrady Dave Brady added a comment -

            Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs
            The FederatedX engine is exactly what we wanted for a system we are running.

            This memory leak is really the only issue with it that is hurting us.

            Hopefully an easy solution will be found!

            Show
            davebrady Dave Brady added a comment - Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs The FederatedX engine is exactly what we wanted for a system we are running. This memory leak is really the only issue with it that is hurting us. Hopefully an easy solution will be found!
            Hide
            capttofu CaptTofu added a comment -

            Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs
            I will look into this! I'm glad you find federatedX to be of use!

            Show
            capttofu CaptTofu added a comment - Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs I will look into this! I'm glad you find federatedX to be of use!
            Hide
            capttofu CaptTofu added a comment -

            Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs
            Hi - btw - how big are the result sets you have using your selects? Just wondering for testing and bug reproduction purposes.

            Show
            capttofu CaptTofu added a comment - Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs Hi - btw - how big are the result sets you have using your selects? Just wondering for testing and bug reproduction purposes.
            Hide
            davebrady Dave Brady added a comment -

            Re: [Bug 781320] Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs
            Hi,

            The result sets can be fairly large: 10 GB would not be uncommon (or even
            the smallest).

            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
            > wondering for testing and bug reproduction purposes.
            >
            > –
            > You received this bug notification because you are subscribed to the bug
            > report.
            > https://bugs.launchpad.net/bugs/781320
            >
            > Title:
            > 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs
            >
            > Status in Maria:
            > New
            >
            > Bug 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.
            >
            > To manage notifications about this bug go to:
            > https://bugs.launchpad.net/maria/+bug/781320/+subscriptions
            >


            Dave Brady
            Senior Database Administrator
            Motorola Mobility
            Technical Operations

            Show
            davebrady Dave Brady added a comment - Re: [Bug 781320] Re: 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs Hi, The result sets can be fairly large: 10 GB would not be uncommon (or even the smallest). 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 > wondering for testing and bug reproduction purposes. > > – > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/781320 > > Title: > 5.2.5-99 on CentOS 5.5 x86_64: FederatedX memory leak during SELECTs > > Status in Maria: > New > > Bug 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. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maria/+bug/781320/+subscriptions > – Dave Brady Senior Database Administrator Motorola Mobility Technical Operations
            Hide
            ratzpo Rasmus Johansson added a comment -

            Launchpad bug id: 781320

            Show
            ratzpo Rasmus Johansson added a comment - Launchpad bug id: 781320

              People

              • Assignee:
                Unassigned
                Reporter:
                davebrady Dave Brady
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: