You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Duncan Grant (JIRA)" <ji...@apache.org> on 2017/05/11 10:39:04 UTC

[jira] [Created] (BROOKLYN-502) mysql cluster intermittently fails on start as slave not correctly configured

Duncan Grant created BROOKLYN-502:
-------------------------------------

             Summary: 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)