Hello Cyril,
Le 16/09/2014 18:54, Cyril Bonté a écrit :
> Hi,
>
> Le 16/09/2014 15:52, Hoggins! a écrit :
> > (...)
>>> defaults
>>> timeout connect 5000
>>> timeout server 5
>>> timeout client 5
>>> (...)
>>> If I issue the same command after a few seconds, here
Hi,
Le 16/09/2014 15:52, Hoggins! a écrit :
> (...)
defaults
timeout connect 5000
timeout server 5
timeout client 5
(...)
If I issue the same command after a few seconds, here is what I get :
MariaDB [(none)]> show variables like '%wsrep_node_name%';
ERROR 200
On Tue, Sep 16, 2014 at 3:52 PM, Hoggins! wrote:
> Wow. First post, first mistake, I hit the button twice after having
> corrected.
> Sorry, *this* is the current config I have problems with.
>
> Le 16/09/2014 15:48, Hoggins! a écrit :
>> Hello list,
>>
>> This is my first post. I checked a bit on
Wow. First post, first mistake, I hit the button twice after having
corrected.
Sorry, *this* is the current config I have problems with.
Le 16/09/2014 15:48, Hoggins! a écrit :
> Hello list,
>
> This is my first post. I checked a bit online to find a solution to my
> problem, but it seems that not
Hello list,
This is my first post. I checked a bit online to find a solution to my
problem, but it seems that not many people are having the same issues.
I use a very simple loadbalancing between two synchronized (Galera)
MariaDB nodes. Here is the HAProxy config file :
SNIP --
Hello list,
This is my first post. I checked a bit online to find a solution to my
problem, but it seems that not many people are having the same issues.
I use a very simple loadbalancing between two synchronized (Galera)
MariaDB nodes. Here is the HAProxy config file :
SNIP --
6 matches
Mail list logo