The data size is about 200 GB. I would have noticed increase on writes. No
backup activity is running (actually I don't do conventional backups).
Any theories?
Thank you for your interest.
Kind regards,
--
Luis Motta Campos
On 23 Oct 2011, at 14:06, Tyler Poland tpol...@engineyard.com wrote:
Claudio,
Thank you for your interest.
I will wait for the issue to happen again and will see what kind of information
I can get back with strace. This is indeed something I didn't think of trying
yet.
I'll keep you people posted on this.
Much appreciated on the new approaches and fresh
Thank you for sharing your experience, Howard.
As those are replica servers, I don't care much about losing a second worth of
data in case of power failure. I believe the data centre has double independent
power sources, and my hardware man assured me if the power goes down at the
data centre
Fellow DBAs and MySQL Users
[apologies for eventual duplicates - I've posted this to
percona-discuss...@googlegroups.com also]
I've been hunting an issue with my database cluster for several months now
without much success. Maybe I'm overlooking something here.
I've been observing the
Luis,
How large is your database? Have you checked for an increase in write
activity on the master leading up to this? Are you running a backup against
the replica?
Thank you,
Tyler
Sent from my Droid Bionic
On Oct 23, 2011 5:40 AM, Luis Motta Campos luismottacam...@yahoo.co.uk
wrote:
Fellow
Luis,
Very hard to tackle.
In my experience, excluding external(to mysql) bottlenecks, like hardware,
o.s. etc, 'suspects' are the shared resources 'guarded' by unique mutexes,
like on the query cache or key cache.
Since you do not use MySQL it cannot be the key cache. Since you use percona
the
: 5.1.51 Database Replica Slows Down Suddenly, Lags For Days, and
Recovers Without Intervention
Luis,
Very hard to tackle.
In my experience, excluding external(to mysql) bottlenecks, like hardware,
o.s. etc, 'suspects' are the shared resources 'guarded' by unique mutexes,
like on the query cache
