Comments - MariaDB Galera Cluster - Known Limitations

5 years, 10 months ago Daniel Black

I'd suggest writing this up as a bug report. I did a quick look and couldn't see an existing bug report.

5 years, 10 months ago Kuntal Chandra

Thanks for your concern. Though not a bug report but posted the same question to community; didn't get any answer.

This may not be a bug rather a feature how galera cluster works. I did some research and got a work around, which I think is quite logical behavior of Galera. I'd request you to look into this and please let me know your feedback.

5 years, 10 months ago Daniel Black

I think writing blog on various issues you come across instead of reporting them as bugs is incredibly selfish. You serve your ego but don't actually contribute back to the development community that made galera happen. There is no way the developers, that could diagnose this issue, are going to scour the internet and find your description of a bug - there are enough bugs already correctly filed that they are working hard to correct and yours could be one of them.

You're blog comments about auto_inc value isn't relevant as the SQL inserts a specific value into the id column.

I'm not sure the optimistic concurrency control aspect of galera is having an effect here either unless another node is modifying the destination table at the same time.

The SQL that you have is quite valid and isn't documented as a limitation and therefore is a bug. Please enter it as such and help everyone else out.

5 years, 10 months ago Kuntal Chandra

I don't understand your logic behind my selfishness or ego! I wrote the post to explain in detail about the issue and how I overcome that; and I shared it publicly.

But your logic about submitting bug report is completely right. If it's not an intended behavior then it should be fixed. I've created an issue here

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.