Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0052457Openbravo ERPA. Platformpublic2023-05-16 10:292023-05-16 10:31
Reportergorkaion 
Assigned ToTriage Platform Conn 
PriorityhighSeveritymajorReproducibilityrandom
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerGold
Web browser
ModulesCore
Support ticket64183
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0052457: On cluster environments processing node can be switch even if current node is alive
DescriptionOn a cluster environment with 2 applications nodes.
Node A is handling Import Entries.
Node B does pings every second to check if Node A is alive by checking a database timestamp.

If for some reason Node A is slow updating the database timestamp the node B can take ownership of the Import Entries even if node A is still alive.

The ping is done every 10s and only allows 1 extra second to consider node A down. So in case Node A fails to update the reference timestamp in 11 seconds the nodes are switches.

Since the node A is not really down this causes that some Import Entries are processed in both application nodes.

The handling process should allow more pings to fail before executing the switch of nodes to allow some punctual slowness in node A.
Steps To ReproduceForce node A to delay the reference timestamp update for 12 seconds.
Proposed SolutionIncrement the extra time allow 1 or 2 pings to fail before switching handling nodes.
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 0052445 closed AugustoMauch The margin when checking if we need to replace a cluster instance is too small 
related to defect 0052456 closed caristu Import Entry post process hook not executed when processing node is changed 
related to defect 0052455 closed caristu Import Entry processed twice when processing node is changed 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2023-05-16 10:29gorkaionNew Issue
2023-05-16 10:29gorkaionAssigned To => Triage Platform Conn
2023-05-16 10:29gorkaionOBNetwork customer => Gold
2023-05-16 10:29gorkaionModules => Core
2023-05-16 10:29gorkaionSupport ticket => 64183
2023-05-16 10:29gorkaionTriggers an Emergency Pack => No
2023-05-16 10:30gorkaionRelationship addedrelated to 0052456
2023-05-16 10:30gorkaionRelationship addedrelated to 0052455
2023-05-16 10:31gorkaionRelationship addedduplicate of 0052445
2023-05-16 10:31gorkaionStatusnew => closed
2023-05-16 10:31gorkaionResolutionopen => duplicate

There are no notes attached to this issue.