The only person with any access to slave virtual server is me.
So, nobody affected slave for sure 100%.
30.11.2016 17:43, Pavel Ivanov пишет:
What was the table schema in the beginning, before it became different
on master and slave? If it was with the default value then maybe
someone with SUPE
How long can it take for a node to sync during a rejoin? Is there
environmental variable for that?
Thanks,
-V
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mari
Woops, sorry, I missed the GLOBAL word :)
Federico
Mer 30/11/16, Ian Gilfillan ha scritto:
Oggetto: Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
A: maria-discuss@lists.launchpad.net
Data: Mercoledì 30 novembre 2016, 15:13
On 30/1
What was the table schema in the beginning, before it became different
on master and slave? If it was with the default value then maybe
someone with SUPER privilege executed on the slave "ALTER TABLE
Message193 CHANGE COLUMN LastUpdated timestamp NOT NULL". If it was
without the default value then
On 30/11/2016 15:13, Federico Razzoli wrote:
This always shows the global value:
SHOW VARIABLES LIKE ...
This always shows the current session value:
SHOW SESSION VARIABLES LIKE ...
This is not correct. SHOW VARIABLES shows the session value:
SET GLOBAL wait_timeout=601;
SET SESSION wait_time
I understand that. I don't understand how it happened that table schema
on slave is not the same
as on master. Any idea?
29.11.2016 19:42, Pavel Ivanov пишет:
You really need to make schema of this table to be the same on the
master and on the slave. The value of LastUpdated is getting out of
s
This always shows the global value:
SHOW VARIABLES LIKE ...
This always shows the current session value:
SHOW SESSION VARIABLES LIKE ...
Global value is read from the files when the server starts, and later can be
changed with SET GLOBAL var = val.
Session value is copied from global value when
7 matches
Mail list logo
