Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Jan 2019 04:20:22 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 234838] ena drop-outs on 12.0-RELEASE
Message-ID:  <bug-234838-227-9U7CSmokY8@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-234838-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-234838-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234838

--- Comment #2 from Leif Pedersen <leif@ofWilsonCreek.com> ---
Of course! Thanks for looking!

It's our standby MySQL database, so there's a light but steady stream of
network IO for the DB replication. Its filesystems are ZFS. Once an hour, s=
ix
other machines (developer sandboxes) pull the latest ZFS snapshot of the DB=
 (in
parallel) so our developers can clone any recent hourly snapshot for testin=
g.
These messages happen about three times per day at the top of the hour when
this hourly pull would be running. They happen sometimes at other odd times:
once on Jan 4, and once on Dec 19, looking at logs going back to Dec 12. So=
 it
probably isn't just the 6 concurrent `zfs send`s that cause it.

Also at the top of the hour, it runs a mysqldump cron which takes ~10 minut=
es.
That has nothing to do with the network; just full disclosure that it incre=
ases
CPU load significantly.

There are batch jobs that send a lot of transactions through the DB replica=
tion
stream, but they don't seem to correlate. I think those cause only minimal
network IO but high CPU & disk load.

The machine doesn't do anything else.

Hopefully that's a helpful idea of the work load. It's the only machine I've
upgraded to 12. Our other machines are running 11.1. This one is my canary;=
 I
dare not upgrade the more important machines with this symptom.

Also, occasionally it will panic with the message "Fatal double fault" and =
no
backtrace. I can get you more on that if you want. Sometimes this panic hap=
pens
when the machine is booting, before it has even configured the network.
Related? I dunno. Just giving you anything that might be useful.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234838-227-9U7CSmokY8>