On 2015/3/7 0:10, Eric Blake wrote:
On 02/25/2015 12:04 AM, zhanghailiang wrote:
+++ b/qmp-commands.hx
@@ -753,6 +753,25 @@ Example:
EQMP
{
+.name = "colo_lost_heartbeat",
...but documented incorrectly (this should use '-' to match the command
name in the .json file,
On 02/25/2015 12:04 AM, zhanghailiang wrote:
>>> +++ b/qmp-commands.hx
>>> @@ -753,6 +753,25 @@ Example:
>>> EQMP
>>>
>>> {
>>> +.name = "colo_lost_heartbeat",
>>
>> ...but documented incorrectly (this should use '-' to match the command
>> name in the .json file, not '_')
>>
On 02/25/2015 03:04 PM, zhanghailiang wrote:
> On 2015/2/17 7:47, Eric Blake wrote:
>> On 02/11/2015 08:17 PM, zhanghailiang wrote:
>>> We leave users to use whatever heartbeat solution they want, if the
>>> heartbeat
>>> is lost, or other errors they detect, they can use command
>>> 'colo_lost_he
在 02/25/2015 03:04 PM, zhanghailiang 写道:
On 2015/2/17 7:47, Eric Blake wrote:
On 02/11/2015 08:17 PM, zhanghailiang wrote:
We leave users to use whatever heartbeat solution they want, if the heartbeat
is lost, or other errors they detect, they can use command
'colo_lost_heartbeat' to tell COL
On 2015/2/17 7:47, Eric Blake wrote:
On 02/11/2015 08:17 PM, zhanghailiang wrote:
We leave users to use whatever heartbeat solution they want, if the heartbeat
is lost, or other errors they detect, they can use command
'colo_lost_heartbeat' to tell COLO to do failover, COLO will do operations
ac
On 02/11/2015 08:17 PM, zhanghailiang wrote:
> We leave users to use whatever heartbeat solution they want, if the heartbeat
> is lost, or other errors they detect, they can use command
> 'colo_lost_heartbeat' to tell COLO to do failover, COLO will do operations
> accordingly.
>
> For example,
> I
We leave users to use whatever heartbeat solution they want, if the heartbeat
is lost, or other errors they detect, they can use command
'colo_lost_heartbeat' to tell COLO to do failover, COLO will do operations
accordingly.
For example,
If send the command to PVM, Primary will exit COLO mode, and
