You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In a microk8s kubernetes implementation of Jira Data Center, I was receiving cluster replication failure errors (Index replication for cluster node jira-data-center-0 is behind by
14000 seconds.) with an offset that was identical to the timezone (EDT which is UTC -4). With research, I discovered this is due to a Jira Data Center timezone of UTC and a database timezone of EDT (this is documented in the Knowledge base: https://confluence.atlassian.com/jirakb/cluster-index-replication-health-check-reports-delay-when-the-database-is-in-a-different-timezone-than-jira-1051984214.html#:~:text=When%20the%20database%20is%20in%20a%20server%20with%20a%20different,seconds%20as%20the%20timezone%20offset.)
Setting the timezone at the node level and the pod level did not resolve the issue.
I resolved the issue by modifying my values.yaml to include the JVM directive in the additionalJvmArgs section.