juju 1.17.0 + mysql / HP > 2G
Jason Robinson
mail at jasonrobinson.me
Thu Dec 19 20:32:15 UTC 2013
Hi,
> I and the CI use machines with 2G memory. This is about as small as
anyone will use mysql for. Juju's memory usage has changed quite a
bit. We have seen the mysql state errors change from rare or very
common.
How much more memory does a server running MySQL with Juju use compared
to a vanilla Ubuntu server running MySQL?
I'm kind of worried hearing "2G is small" - I maintain production
servers with less memory for small sites. Especially as Juju encourages
running a single service on a single machine - running more small
machines and less large ones seems to me a thing it encourages.
Thanks :)
Br,
Jason
On 19/12/13 19:42, Curtis Hovey-Canonical wrote:
> I think I have sussed the HP mysql errors that have plagues the 1.17.0
> development cycle.
>
> I and the CI use machines with 2G memory. This is about as small as
> anyone will use mysql for. Juju's memory usage has changed quite a
> bit. We have seen the mysql state errors change from rare or very
> common.
>
> So I think https://bugs.launchpad.net/juju-core/+bug/1255242
> (upgrade-juju and bootstrap on HP cloud broken in devel) is really
> about mysql + juju.
>
> For now, I have changed CI to use more RAM. If the next few CI runs
> don't see the error, I will consider this issue a mysql problem.
> However we might have a user problem because "juju deploy mysql" is
> less likely to "just work" on HP cloud.
>
More information about the Juju-dev
mailing list