Pavel Ivanov piva...@google.com writes:
Kristian Nielsen kniel...@knielsen-hq.org writes:
So perhaps it is better to just say that --replicate-same-server-id does not
apply to GTID mode at all. Instead, in GTID mode, if we receive an event with
our own server_id and smaller seq_no than what
Krisitan,
Did you figure out what would be the best solution here?
Thank you,
Pavel
On Tue, Sep 3, 2013 at 2:05 AM, Kristian Nielsen
kniel...@knielsen-hq.org wrote:
Kristian Nielsen kniel...@knielsen-hq.org writes:
The main problem I see is what should be the default? I suppose we cannot
Pavel Ivanov piva...@google.com writes:
--replicate-same-server-id flag which as I understand (when set to 0)
controls two things:
1) It doesn't allow slave to connect to a master with the same server_id.
2) Slave ignores all binlog events in the replication stream that have
the same
Kristian Nielsen kniel...@knielsen-hq.org writes:
The main problem I see is what should be the default? I suppose we cannot
safely change the default for --replicate-same-server-id. On the other hand,
if users explicitly set --replicate-same-server-id=0, then it really does not
seem correct
Kristian,
Currently MariaDB (as well as MySQL of all previous versions) has a
very big problem related to replicating same server_id. There is
--replicate-same-server-id flag which as I understand (when set to 0)
controls two things:
1) It doesn't allow slave to connect to a master with the same
5 matches
Mail list logo
