On 5 Aug 2016, at 9:24, Mark Wadham wrote:
> Can anyone explain this? http://pastebin.com/Zctaj8BE
Nevermind, got it answered in the irc channel :)
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.
Can anyone explain this? http://pastebin.com/Zctaj8BE
TL;DR index sizes seem to differ drastically in size depending on how
you request them.
Thanks,
Mark
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.laun
Hi,
MariaDB 10.1.16 with a 3-node galera cluster.
We had 187GB free disk space and had the gcache set to 800GB. We
started firing write traffic at the cluster and then began testing the
process of performing DDL on a single node in RSU mode. Our command was
a single ALTER TABLE statement th
On 21 Jul 2016, at 9:39, Mark Wadham wrote:
Confirmed this
Oh wait, it seems that if we do:
SET wsrep_OSU_method='RSU';
(with GLOBAL omitted) then it sort of works. The node doesn't desync
immediately but as soon as we execute some DDL it does desync, and then
immediately r
On 21 Jul 2016, at 9:05, Mark Wadham wrote:
I don't think this was the case during our testing, but I'll test it
again anyway. If I understand RSU mode correctly all it does is
ensure that DDL statements aren't replicated to the other nodes.
AFAIK it won't stop the w
Hi Nirbhay,
As discussed on IRC #mariadb, you do not really need to take the node
off
cluster (3).
Just set wsrep_osu_method's session value to RSU and perform the
schema
change.
With RSU mode enabled, the node automatically desyncs itself from the
cluster before
executing any DDL,and thus ot
On 20 Jul 2016, at 16:34, Mark Wadham wrote:
3. Testing whether regular IST is affected, ie IST that should occur
normally without switching to RSU mode or dropping a node out of the
cluster.
Will reply again when we've tested this.
Haven't tested this yet, but we just tested t
1. Switching node 0 back to TOI mode before rejoining the cluster,
although I can't really see how this would make a difference.
Made no difference.
2. Upgrading to MariaDB 10.1.16 which was released a couple of days
ago.
Also made no difference, the issue is still reproducable.
3. Testing
Hi,
We have a repeatable failure to initiate IST with MariaDB 10.1.14 after
performing a schema upgrade on a single node in RSU mode. The error
condition is when there is a delete query in the format:
delete from where id >=
on the non-RSU cluster nodes while the node is disconnected from
9 matches
Mail list logo
