The article mentions 23:59:60 implying the correction happens at the end of the day, but I imagine a correction would be less disturbing by sitting on 12:00:00 AM for the extra second given the disturbance can be washed over the following minutes. But the question, which time zone? Perhaps UTC -12:00
The article doesn’t correctly explain “32-bit” Unix issue. A 32-bit number can easily take us into the next millennium (0..4,294,967,295). The issue concerns the signed 32-bit number which we know is limited to the max value of 2147483647 (-2147483648..2147483647)
Good points regarding replication and minute granularity. Another reason why likely better to hold on the initial second of the hour at UTC -12:00.
Good question. I can't really recall. I think it's UTC, which for me would be -5 or -6 depending upon the time of the year. Most computers use UTC internally these days, even though most folk don't know that. It is one of the reason they ask for your timezone when installing the OS. The time that you see is calculated from the offset.NIST.gov has a lot of time-related information on their site. They might have more info about when changes are supposed to occur
I have computers that I support that I actually configure as UTC since they are in multiple time zones, and I want the log file time/date stamps to be in sync when troubleshooting.