[20:59] <thomi> Hello #juju - I have a single lxd controller running on my laptop, with 4 applications (5 units total) running. This morning I find that /usr/lib/juju/mongo3.2/bin/mongod is using 13GB or RAM. This seems excessive to me. Is there something I can do to trim that down?
[21:00] <thomi> I thought perhaps restarting mongod might work, but I don't see a systemd service file for it, so I guess it's managed by jujud itself.
[21:00] <thomi> veebers: perhaps you have any ideas?
[21:04] <veebers> thomi: hey, wow yeah that seems excessive. mongodb is known as something else for systemd I think, juju-mongodb?
[21:05] <thomi> veebers: this should be on my host, or on the bootstrap node?
[21:05] <veebers> thomi: which version of juju are you using?
[21:06] <thomi> 2.0.2-zesty-amd64
[21:06] <veebers> thomi: on the bootstrap node, you're host wouldn't know about mongo (as it's installed in the lxd container)
[21:06] <thomi> I don't see any systemd control files with 'mongo' in their name. Not on the host nor the bootstrap node
[21:06] <veebers> huh
[21:07] <veebers> I might be wrong then, let me check something out
[21:08] <thomi> I might not understand how lxd works, but I don't see 'mongod' in the process list in the container, only on the host
[21:10] <veebers> thomi: you only have a single lxd container?
[21:10] <thomi> no, there's a bunch, bot most of them are for the applications deployed
[21:10] <veebers> thomi: ok, you'll want to be on the controller machine
[21:11] <thomi> I'm not familiar with that terminology. What does 'controller machine' mean, exactly?
[21:12] <thomi> oh! I see now, this has changed from juju1
[21:12] <veebers> thomi: ah right, sorry yes I'm so used to thinking in juju2 terms
[21:12] <thomi> I was assuming that 'juju ssh 0' got me into the bootstrap node, but I guess it doesn't
[21:13] <thomi> So what's the easiest way with juju 2 to ssh into the controller containers?
[21:13] <veebers> thomi: ah right, juju ssh -m controller 0 should so it
[21:13] <thomi> ahh
[21:13] <veebers> you may need juju ssh -m <controller name>:controller 0
[21:14] <veebers> (Each controller has a controller model)
[21:17] <thomi> hmm, ok, thanks. That helped. Thanks!
[21:20] <veebers> thomi: nw, let me know how it goes