On 11-11-12 03:56 PM, Michael Marrotte wrote:
An N+1 or N+X topology might be good for that cascading scenario...
Find a sweet spot for the evict date.
If slave are lagging too much, scale and tune.
Hi,
That's plainly not always possible since MySQL replication is single
threaded. That's
On 11-11-12 02:51 PM, Florian Haas wrote:
Hi Yves and Michael,
On 2011-11-12 19:22, Yves Trudeau wrote:
lol... How many large databases have you managed? Once evicted, MySQL
will be restarted by Pacemaker so all the caches will be cold.
If I may say so, before you start laughing at people on
An N+1 or N+X topology might be good for that cascading scenario... Find a
sweet spot for the evict date. If slave are lagging too much, scale and
tune.
I haven't read Yves' patch, but I'll check it out. I just saw that he was
looking for slave to work with VIP and suggested a couple ways I've
On 2011-11-12 21:32, ge...@riseup.net wrote:
>> We're all aware that this log verbosity is an issue that affects many
>> users, however pushing down the logging priority of all those messages
>> is not really an option -- as they are highly valuable in failure
>> analyses or postmortems.
>
> Ok, b
> No you're not getting debug messages. You're seeing tons of info and
> notice messages, and all of Corosync, Pacemaker, and DRBD produce lots
> of them.
Didn't know this, just saw [debug] in all these messages.
> We're all aware that this log verbosity is an issue that affects many
> users, how
On 2011-11-12 16:46, ge...@riseup.net wrote:
> Anyone?
>
>> Hello,
>>
>> I've got tons of debug messages in my logfiles, and therefore would like
>> to disable debug messages, and only receive errors etc.
No you're not getting debug messages. You're seeing tons of info and
notice messages, and al
Hi Yves and Michael,
On 2011-11-12 19:22, Yves Trudeau wrote:
> lol... How many large databases have you managed? Once evicted, MySQL
> will be restarted by Pacemaker so all the caches will be cold.
If I may say so, before you start laughing at people on the list, it may
be a good idea to actual
lol... How many large databases have you managed? Once evicted, MySQL
will be restarted by Pacemaker so all the caches will be cold. On a
128GB db server with an InnoDB buffer pool of >100 GB, warming the cache
takes hours and during that time the db is much slower. Since the slave
has been
Why's evicted terrible? It optional and simply removes the slave node from the
cluster if it's lagging too far behind the master. The collocation IP can
float to another slave in the cluster or go offline. I thought that's what
you're looking for. I can post a config if you're interested.
S
Hi,
Setting evict_outdated_slaves is terrible but then how do you remove
the read VIPs from slaves that are outdated. If there is a way to do
it, tell me :) I am always open to do things in a simpler way. This
solution works without evicting outdated slaves. The current mysql RA
does b
Anyone?
> Hello,
>
> I've got tons of debug messages in my logfiles, and therefore would like
> to disable debug messages, and only receive errors etc.
>
> So I tried to achieve this - with no success.
> The relevant part of my corosync.conf is looking like:
>
> logging {
> fileline: off
Are you using evict_outdated_slaves?
If set to true, any slave which is more than max_slave_lag seconds
behind the master has its MySQL instance shut down. If this parameter
is set to false in a primitive or clone resource, it is simply
ignored. If set to false in a master/slave resource, then e
Il 12/11/2011 11:26, Stefan Hornburg (Racke) ha scritto:
On 11/11/2011 01:43 PM, Raoul Bhatia [IPAX] wrote:
hi!
as i'm quote familiar with the pure-ftpd script, i'm stepping into
this conversation.
On 2011-11-10 18:40, Mailing List SVR wrote:
1) I have this primitive:
primitive ftp_service o
13 matches
Mail list logo
