[ec2] swap?

[Darren Govoni]

I'll post the results later today.

basically I am running the following from 3 separate ssh sessions.

- free -m -s 3
- top
- tail -f /var/log/messages

I figure once the instance freezes, the output from those on my desktop
will also be frozen and provide some clues.

Darren

On Sun, 2009-07-26 at 10:52 -0700, Jeremy Edberg wrote:
> If you get any further results, please make sure to share them.  I too
> am actively trying to pin down this bug, as it has crashed three of my
> instances at this point, usually at the most inopportune times.
> 
> Although, in my case, a reboot has been able to save the instance.
> 
> Jeremy
> 
> On Sun, Jul 26, 2009 at 10:44, Darren Govoni<darren at ontrenet.com> wrote:
> > Hey guys,
> >   Good points. I use the high-cpu deployment which only has 7GB. I
> > wonder if there will be a configuration of high-cpu with more than 7GB.
> >
> > The problem I am running into may be related to the other posted issue
> > here when instances freeze.
> >
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/276476
> >
> > Basically, all of my instances will freeze up after some time running
> > where they are reading/writing AWS services heavily as well as local
> > disk. I was concerned if its related to no virtual memory swap.
> >
> > Right now I am running a test with some output on memory,cpu and tail
> > -f /var/log/messages to see what the condition is when it freezes.
> >
> > once it freezes I cannot even reboot it. Its gone forever.
> >
> > Darren
> >
> > On Sun, 2009-07-26 at 21:55 +1200, Robert Coup wrote:
> >> On Sun, Jul 26, 2009 at 11:33 AM, Eric Hammond
> >> <ehammond at thinksome.com> wrote:
> >>
> >>         In my own production servers I prefer to run with plenty of
> >>         memory and
> >>         no swap.
> >>
> >>
> >> Likewise, certainly I don't run production machines with any more than
> >> 256MB of swap, most have none. Reason being is once all the RAM is
> >> consumed a process has gone haywire and needs to die. The more swap
> >> there is the longer the time until the OOM-killer steps in. Until then
> >> everything on the box grinds to a halt, new connections just hang,
> >> there's no way to log in (15mins+ to a shell), etc. With no swap, the
> >> out-of-memory killer steps up immediately and kills off the hungry
> >> process. I'd much rather such an errant process dies (and is restarted
> >> by monitoring) than the box grind to a halt.
> >>
> >>
> >> Note this is a bit different from lots of processes (eg. apache
> >> workers) slowly growing over time until there's no memory left. We
> >> watch out for that via monitoring as well.
> >>
> >>
> >> Rob :)
> >
> >
> > --
> > Ec2 mailing list
> > Ec2 at lists.ubuntu.com
> > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ec2
> >