Results 1 to 2 of 2

Thread: Memory leak spare shinken-arbiter?

  1. #1
    Junior Member
    Join Date
    Feb 2015
    Posts
    2

    Memory leak spare shinken-arbiter?

    We're running Shinken in a fairly large environment in a distributed setup. We have a master arbiter and a spare arbiter on another host. When doing a fresh start of the spare arbiter it consumes about 4.6GB of memory.

    However, after each shinken reload on the primary arbiter the spare arbiter takes an extra 1 GiB. So after a couple of reloads on the master host, the spare host runs out of memory because the extra claimed GB's by the spare arbiter are never released.

    In short:
    • Initial startup of spare arbiter takes 4.6GiB of memory
    • Each reload issued on the master arbiter causes the spare arbiter to claim another 1GiB or memory
    • This extra memory is never released, causing the spare arbiter host to run out of memory eventually


    Is there any known issue which may cause this behaviour? We're running Shinken version 2.0.3.

  2. #2
    Junior Member
    Join Date
    Feb 2015
    Posts
    2
    Some more info on the subject: https://github.com/naparuba/shinken/issues/1506

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •