Hi!
Sasha == Sasha Pachev [EMAIL PROTECTED] writes:
Sasha On Thursday 07 March 2002 12:42 am, Jeremy Zawodny wrote:
My 4.0.2 slave has run through about 14 million queries and it's going
well.
Sasha Good news
Do you have any feel for how much slower a debugging version of MySQL
is
On Thursday 07 March 2002 12:42 am, Jeremy Zawodny wrote:
My 4.0.2 slave has run through about 14 million queries and it's going
well.
Good news
Do you have any feel for how much slower a debugging version of MySQL
is compared to a normal version? ?I ask because my replication
heartbeat
On Thu, Mar 07, 2002 at 09:57:54AM -0700, Sasha Pachev wrote:
On Thursday 07 March 2002 12:42 am, Jeremy Zawodny wrote:
Do you have any feel for how much slower a debugging version of
MySQL is compared to a normal version? ?I ask because my
replication heartbeat monitor has noticed this
On Tue, Mar 05, 2002 at 12:13:25PM -0800, Jeremy Zawodny wrote:
On Tue, Mar 05, 2002 at 09:19:35AM -0700, Sasha Pachev wrote:
On Tuesday 05 March 2002 01:17 am, Jeremy Zawodny wrote:
When the machine is pounding away on updates (over 300/sec), it can
take a long time to get a response to
On Sat, Mar 02, 2002 at 09:57:58PM -0800, Jeremy Zawodny wrote:
Murphy's law strikes! Just a few hours ago I blasted the relay logs
on my 4.0.2 slave. It ran out of disk space!
I'll rsync the slave and build a fresh MySQL from the bitkeeper tree
and let you know.
Sasha,
I re-synced my
On Tuesday 05 March 2002 01:17 am, Jeremy Zawodny wrote:
When the machine is pounding away on updates (over 300/sec), it can
take a long time to get a response to SHOW SLAVE STATUS. ?I get one,
but it can take between 5 and 30 seconds:
My first inclination was to blame FreeBSD threads, but
On Tue, Mar 05, 2002 at 09:19:35AM -0700, Sasha Pachev wrote:
On Tuesday 05 March 2002 01:17 am, Jeremy Zawodny wrote:
When the machine is pounding away on updates (over 300/sec), it can
take a long time to get a response to SHOW SLAVE STATUS. ?I get one,
but it can take between 5 and 30
On Monday 11 February 2002 01:01 pm, Jeremy Zawodny wrote:
Okay, I've hit a bug. ?It happened after the slave had replicated
about 5,397,000 queries.
Jeremy:
I have finally gotten around to this and I think I've found the bug. At
least, on a different system where I could repeat it before my
On Sat, Mar 02, 2002 at 10:32:39PM -0700, Sasha Pachev wrote:
On Monday 11 February 2002 01:01 pm, Jeremy Zawodny wrote:
Okay, I've hit a bug. ?It happened after the slave had replicated
about 5,397,000 queries.
Jeremy:
I have finally gotten around to this and I think I've found the
On Sat, Feb 09, 2002 at 09:41:25PM -0700, Sasha Pachev wrote:
* Monitor your slave to make sure it does not crash ( watch error log for
stack trace messages), slave keeps running ( check with SHOW SLAVE STATUS),
and data is consistent.
* If there are problems, I will need the
On Monday 11 February 2002 12:55 pm, Jeremy Zawodny wrote:
The slave hit a duplicate key error and died. ?The IO thread appears
to still be running, but the SQL thread is not. ?When I try to do a
SLAVE START on the slave, the command never returns to the mysql
prompt.
Jeremy:
First, do
11 matches
Mail list logo
