[MDEV-20894] Gtid Position difference between MariaDB version Created: 2019-10-24 Updated: 2019-11-05 Resolved: 2019-11-05 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | 10.2.27, 10.1.41 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Ragul | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Rhel 7 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Hi, On analyzing, I could see a weird behavior during MariaDB Installation with the below my.cnf. I tried to reproduce the scenario as simple as possible by a shell script mariaTest.sh [mysqld] from where I could see the difference in the output of gtid_positions in v10.2.18 where first 3 positions are null while in v10.2.27 it has 0-1-1. As part of my analysis, I could see the above difference only after adding "log-bin=binary-log." properties in my cnf file. while without the property I could not see the above difference. Can you please clarify the above behavior? Why the position get affected after adding "log-bin" ? |
| Comments |
| Comment by Ragul [ 2019-10-31 ] |
|
Can anyone help with this issue? |
| Comment by Elena Stepanova [ 2019-11-05 ] |
|
MariaDB JIRA is a bug tracking system. If you believe you have encountered a bug, please report it as such, indicating observed behavior vs expected behavior, explanation why you consider the actual behavior to be incorrect, and a test case to reproduce the problem. To seek advice about configuring your instance or general information about server behavior, please try documentation, public resources and community mailing lists. You might also want to consider acquiring a support contract. If you already have one, please submit a support ticket. |