Graylog Charm

Heap size locked to 1GB

Bug #1807565 reported by Andrea Ieri
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Graylog Charm
Fix Released
High
Haw Loeung

Bug Description

It seems like Graylog is always locked at using no more than 1GB, irrespective of how much memory the hosting machine has at its disposal.
This is a bit tight in some environments, so it would be useful to be able to configure the heap size, with a default being dynamically calculated based on the total available memory.

Related branches

~hloeung/graylog-snap:master
Junien F: Approve
Diff: 15 lines (+4/-0)
1 file modified
graylog-server.sh (+4/-0)
~hloeung/charm-graylog:master
Haw Loeung: Needs Resubmitting
Joel Sing (community): Approve (+1)
Diff: 532 lines (+236/-45)
11 files modified
.gitignore (+7/-3)
Makefile (+5/-10)
config.yaml (+5/-0)
files/check_graylog_health.py (+1/-1)
lib/logextract.py (+7/-7)
reactive/graylog.py (+69/-4)
requirements.txt (+1/-0)
tox.ini (+27/-0)
unit_tests/requirements.txt (+6/-0)
unit_tests/test_graylog.py (+94/-3)
unit_tests/test_logextract.py (+14/-17)
Haw Loeung (hloeung)
Changed in graylog-charm:
status: New → In Progress
assignee: nobody → Haw Loeung (hloeung)
importance: Undecided → High
Haw Loeung (hloeung)
Changed in graylog-charm:
status: In Progress → Fix Committed
Revision history for this message
Haw Loeung (hloeung) wrote :

Changes have landed both to the charm itself and to the snap. An updated snap has been built and is in the candidate channel.

I'll work on building the charm, testing the built charm, and then if all goes well, release both the charm and the snap.

Revision history for this message
Haw Loeung (hloeung) wrote :

Updated charm pushed with missing graylog snap resource and released as graylog-25.

Changed in graylog-charm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.