2015-06-25 14:02 GMT+02:00 wagnerbianchi.com :
> Some additional information here, just my 2 cents.
>
> (...)
>
> Just checking in: using two servers in replication, idle servers, on the
> slave side I configured globally the slave_net_timeout=1 and log_warnings=2,
> as I'm using 5.6 for these test
Some additional information here, just my 2 cents.
The system variables slave_net_timeout will controls over the time the
slave server will be waiting for new data dumped form master's binlog. If
no interaction or inactivity is greater than slave_net_timeout, the
reconnection will be made. Here is
2015-06-22 13:45 GMT+02:00 Ben RUBSON :
> 2015-06-19 12:08 GMT+02:00 Ben RUBSON :
>>
>> 2015-06-18 22:52 GMT+02:00 shawn l.green :
>>>
>>> On 6/18/2015 2:10 PM, Ben RUBSON wrote:
Hello,
In order for the slave to quickly show a communication issue between
the master and
2015-06-19 12:08 GMT+02:00 Ben RUBSON :
>
> 2015-06-18 22:52 GMT+02:00 shawn l.green :
>>
>> On 6/18/2015 2:10 PM, Ben RUBSON wrote:
>>>
>>> Hello,
>>>
>>> In order for the slave to quickly show a communication issue between
>>> the master and the slave, I set slave_net_timeout to 10.
>>> "show sla
2015-06-18 22:52 GMT+02:00 shawn l.green :
>
> On 6/18/2015 2:10 PM, Ben RUBSON wrote:
>>
>> Hello,
>>
>> In order for the slave to quickly show a communication issue between
>> the master and the slave, I set slave_net_timeout to 10.
>> "show slave status" then quickly updates, perfect.
>>
>> I wo
On 6/18/2015 2:10 PM, Ben RUBSON wrote:
Hello,
In order for the slave to quickly show a communication issue between
the master and the slave, I set slave_net_timeout to 10.
"show slave status" then quickly updates, perfect.
I would also like the master to quickly show when the slave is no mor
