Try
mysql -u root -h 127.0.0.1 -p
And if that doesn't work
mysql -u root -h -p
On Sep 1, 2013, at 4:59 AM, "John Smith" wrote:
> __mysql_exceptions,OperationalError (2003 "Can't connect to MySQL server on
> 'localhost' (10061)")
>
> My question: How do I change from localhost to 124.0.0.1?
You could write to an InnoDB frontend with master/master replication at
each site, and slave off the local InnoDB server to your local cluster
at each site.
Would make your writes limited by your InnoDB server performance and
remote replication speed, but reads would run at cluster speeds and
On 06/12/2012 05:10 AM, Johan De Meersman wrote:
- Original Message -
From: "Claudio Nanni"
" Print out warnings such as Aborted connection... to the error log."
the dots are not telling if they comprise Aborted clients as well.
Hah, how's that for selective blindness. Totally missed t
One cause of heavy replication lag we noticed was due to a misbehaving
application blasting updates (and commits) onto the master InnoDB tables from
multiple clients. Since slave replication is single-threaded, it couldn't keep
up I/O-wise, while the master seemed to show reasonably low load thr
r -e "slave start"
fi
done
Not pretty, but should do the job with more sanity checks, with the
caveat that sometimes Seconds_Behind_Master can return some interesting
values
Howard Hart
Ooma, Inc.
ewen fortune wrote:
Hi Shain,
If you are using InnoDB its possible to patch to a
