brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark McKenna (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-502) mysql cluster intermittently fails on start as slave not correctly configured
Date Tue, 23 May 2017 09:46:04 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020959#comment-16020959
] 

Mark McKenna commented on BROOKLYN-502:
---------------------------------------

I have observed this behaviour also ... it seems to happen when network conditions aren't
optimal. 

>From looking at the code it is hard to see what is going wrong. This needs further investigation

> mysql cluster intermittently fails on start as slave not correctly configured
> -----------------------------------------------------------------------------
>
>                 Key: BROOKLYN-502
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-502
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Duncan Grant
>            Priority: Minor
>
> Occasionally when starting a mysql cluster with 2 nodes (difficult to replicate but presumably
could happen with more) - slave node goes on fire as it is never healthy.
> This is caused by the mysql command 'SHOW SLAVE STATUS' never returning content.
> There is nothing obvious in the amp log.  First error is the timeout waiting for service
up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message