Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-6711

Isolate the cause of memory leak in Sidekiq jobs

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • SaaS
    • System
    • None
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Undefined

      For years operations people team are seeing uncontrollable increase of memory consumption in sidekiq and frontend servers. API servers are not affected.

      We suppose that this has to do with template rendering, especially in liquid.

      The current task is to separate Sidekiq jobs in different group queues.

      The first group is composed of Job processing template rendering and the other group the other tasks.

       

      Operations people team agrees on creating 2 pool of sidekiq jobs servers as described above.

       

      System people team will configure the code and the deployments to run those sidekiq jobs inside the correct pool.

       

      Basically we have:

       

       

      Job purpose Servers
      • sidekiq email
      • sidekiq pdf generation
      		 Pool 1
      • other jobs
      		 Pool 2

       

       

       

       

          1.
          		 Operations to create new servers for SaaS system-services Sub-task Closed Major Unassigned
          2.
          		 Separate queues for mailer and rendering template jobs Sub-task Closed Major Unassigned

              Unassigned Unassigned
              hramihaj Hery Ramihajamalala (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: