[jira] [Commented] (AMQ-2414) JDBC datastore locking does not work when using MYSQL cluster

["SuoNayi (Commented) (JIRA)" <ji...@apache.org>]

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

SuoNayi commented on AMQ-2414:
------------------------------

Other tow problems when testing with ndbcluster.
1)No distributed table locks support yet, so it's impossible to set up a master/slave broker for HA with ndbcluster.
2)Low performance and from time to time producer is suspended and resumes to send messages for several minutes.
                
> JDBC datastore locking does not work when using MYSQL cluster
> -------------------------------------------------------------
>
>                 Key: AMQ-2414
>                 URL: https://issues.apache.org/jira/browse/AMQ-2414
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.3.0
>            Reporter: Alexander Fisher
>             Fix For: 5.6.0
>
>         Attachments: mysql-cluster-locking-r818849.patch
>
>
> JDBC Master/Slave doesn't work properly for mysql cluster when the master and slave brokers are using different MYSQL frontends as would be required in a HA setup.  The code currently locks the database using a TABLE lock which are not cluster wide in mysql.
> http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-multiple-nodes.html
> The default code path uses a SELECT FOR UPDATE to get a lock.  This is supported in mysql cluster.
> The attached patch works for me.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira