Creating a table that contains a timestamp can make nodes inconsistent
Description
Environment
AFFECTED CS IDs
Smart Checklist
Activity
Jira Bot December 24, 2020 at 2:56 AM
Hello ,
It's been 52 days since this issue went into Incomplete and we haven't heard
from you on this.
At this point, our policy is to Close this issue, to keep things from getting
too cluttered. If you have more information about this issue and wish to
reopen it, please reply with a comment containing "jira-bot=reopen".
Jira Bot December 16, 2020 at 1:57 AM
Hello ,
It's jira-bot again. Your bug report is important to us, but we haven't heard
from you since the previous notification. If we don't hear from you on
this in 7 days, the issue will be automatically closed.
Jira Bot December 1, 2020 at 1:57 AM
Hello ,
I'm jira-bot, Percona's automated helper script. Your bug report is important
to us but we've been unable to reproduce it, and asked you for more
information. If we haven't heard from you on this in 3 more weeks, the issue
will be automatically closed.
Lalit Choudhary October 28, 2020 at 9:30 AM
Not reproduciable with the latest version of PXC.
Testcase:
Details
Details
Assignee
Reporter
Jaime SicamAffects versions
Priority
MediumSmart Checklist
Open Smart Checklist
Smart Checklist
If time_zone session variable is not applied when CREATE TABLE is replicated to other nodes , then it's possible that the table will not be created on the other nodes due to invalid timestamp range.
To reproduce:
As you can see above, the table is created. However, on the error logs on other nodes, you can see that table creation failed due to invalid timestamp range:
As soon as you insert a row on the first node, the other two nodes will die due to node inconsistency and the cluster will break: