[STORM-4116] Heartbeats mechanism is affected by Y2038 bug · apache/storm#7897

2024-11-13T09:32:49.000Z

I have a test after year 2038 (ex: 2040) to validate my topology is not affected by Y2038 bug. Context: I have installed storm 2.4.0 on each node of my platform I updated my platform to date 24/04/2040 In the storm nimbus configuration I set the following pacemaker configuration: ###################################### Pacemaker configuration ### ###################################### Cluster state management. PaceMakerStateStorageFactory to use pacemaker instead of Zookeeper. storm.cluster.state.store: "org.apache.storm.cluster.PaceMakerStateStorageFactory" Pacemaker servers and port configuration pacemaker.servers: [" "] pacemaker.port: 6699 Minimal number of thread used to monitor topologies lifecycle pacemaker.base.threads: 10 Maximal number of thread used to monitor topologies lifecycle pacemaker.max.threads: 50 Number of maximum thread for each connected client pacemaker.client.max.threads: 2 Thread client timeout pacemaker.thread.timeout: 10 Childopts for server pacemaker.childopts: "-Xmx4096m" Authentification if needed (Kerberos, etc ...) pacemaker.auth.method: "NONE" pacemaker.kerberos.users: [] Size maximum of message sent by supervisor to pacemaker pacemaker.thrift.message.size.max: 10485760 In the storm supervisor, I put the following one: ###################################### Pacemaker configuration ### ###################################### Cluster state management. PaceMakerStateStorageFactory to use pacemaker instead of Zookeeper. storm.cluster.state.store: "org.apache.storm.cluster.PaceMakerStateStorageFactory" Pacemaker servers and port configuration pacemaker.servers: [" "] pacemaker.port: 6699 I submitted my topology The topology is well submitted on the supervisor node Observations: I checked the from supervisor node and I am able to ping. In the nimbus log, I observed that after a certain time the topology is reassigned because no heartbeat has been received inside Nimbus server from workers. I checked logs and content of sources and I observed that timestamps of heartbeats (time_secs and uptime_secs variables) are set into integer. This issue also been observed on 2.7.0 version. --- Originally reported by alexisdureuil , imported from: Heartbeats mechanism is affected by Y2038 bug status : Open priority : Major resolution : Unresolved imported : 2025-01-24

(5 commentaires) (0 réactions) (1 assigné)Java (6 517 stars) (4 149 forks)batch import

Imported Jira Issuebuggood first issue

Description

Guide contributeur

Stack technique: java
Domaine: backendinfrastructure
Type d'issue: bug
Difficulté: 3
Temps estimé: half day
Statut d'activité: blocked
Clarté: clear
Prérequis: JavaApache Storminteger overflowheartbeat mechanism
Accessibilité débutant: 35
Direction de recherche: Investigate the heartbeat mechanism in Apache Storm source code, focusing on the nimbus and pacemaker components. Identify all integer fields used for timestamps (e.g., time secs, uptime secs) and change their types to long. Verify any thrift schema changes required. Check the issue comments and any linked code for additional context.