On 18/06/2013, at 2:23 PM, Jon Eisenstein wrote:
>
> On Jun 18, 2013, at 12:12 AM, Andrew Beekhof wrote:
>
>>
>> On 18/06/2013, at 1:46 PM, Jon Eisenstein wrote:
>>
>>>
>>> On Jun 17, 2013, at 11:31 PM, Andrew Beekhof wrote:
>>>
On 18/06/2013, at 7:19 AM, Jon Eisenstein wrot
On Jun 18, 2013, at 12:12 AM, Andrew Beekhof wrote:
>
> On 18/06/2013, at 1:46 PM, Jon Eisenstein wrote:
>
>>
>> On Jun 17, 2013, at 11:31 PM, Andrew Beekhof wrote:
>>
>>>
>>> On 18/06/2013, at 7:19 AM, Jon Eisenstein wrote:
>>>
tl;dr summary: On EC2, we can't reuse IP addresses, a
On 18/06/2013, at 1:46 PM, Jon Eisenstein wrote:
>
> On Jun 17, 2013, at 11:31 PM, Andrew Beekhof wrote:
>
>>
>> On 18/06/2013, at 7:19 AM, Jon Eisenstein wrote:
>>
>>> tl;dr summary: On EC2, we can't reuse IP addresses, and we need a reliable,
>>> scriptable procedure for replacing a dea
On Jun 17, 2013, at 11:31 PM, Andrew Beekhof wrote:
>
> On 18/06/2013, at 7:19 AM, Jon Eisenstein wrote:
>
>> tl;dr summary: On EC2, we can't reuse IP addresses, and we need a reliable,
>> scriptable procedure for replacing a dead (guaranteed no longer running)
>> server with another one wi
On 18/06/2013, at 7:19 AM, Jon Eisenstein wrote:
> tl;dr summary: On EC2, we can't reuse IP addresses, and we need a reliable,
> scriptable procedure for replacing a dead (guaranteed no longer running)
> server with another one without needing to take the remaining cluster members
> down.
Th
tl;dr summary: On EC2, we can't reuse IP addresses, and we need a reliable,
scriptable procedure for replacing a dead (guaranteed no longer running) server
with another one without needing to take the remaining cluster members down.
I'm trying to build a Pacemaker solution using Percona Replica
