The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-15. For the latest, interactive version please visit https://mariadb.com/kb/.

spider High Availability Setup, after crash one node,the other can't be update from spider on crash node table.

I test high availability setup,and has questions below:

 PARTITION pt1 COMMENT = 'srv "backend1 backend2_rpl",  mbk "2", mkd "2", msi "49161", link_status "0 0"',
 PARTITION pt2 COMMENT = 'srv "backend2 backend1_rpl",  mbk "2", mkd "2", msi "49161", link_status "0 0" '

then pt1 host crash,spider host can dml use pt2 host. but I can dml server backend2,only can insert/delete server backend2_rpl table,can't update backend2_rpl table only.

I test this on mariadb 10.0.23 and 10.1.23,the same result. what's the reason? thanks.

Answer Answered by Ian Gilfillan in this comment.

I suggest reporting this as a bug.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.