Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0052455Openbravo ERPA. Platformpublic2023-05-16 09:452023-05-22 11:46
Reportergorkaion 
Assigned Tocaristu 
PriorityhighSeveritymajorReproducibilityrandom
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tocaristu
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0052455: Import Entry processed twice when processing node is changed
DescriptionOn a clustered environment with 2 application nodes.

If the node handling import entries is changed from node A to node B while node A is still processing Import Entries.

When the node B start processing it searches import entries and queue some that are also queued and to be processed in node A.

These Import Entries are processed in both nodes. When the Import Entry is 1st processed by node B and later in node A.

The Import Entry processed in node B ends with success.

The Import Entry processed in node A can fail generating a false error or duplicating a processing.

In case of POS requests like Order Loader the process generates a Error While Importing with an OutdatedDateException.
In case of a Integration request the process might send again the same data to the external system generating a duplicate.
Steps To ReproduceRough steps:
- Build a cluster environment with node A and B.
- Generate some Import Entries.
- When all Import Entries are queued in node A switch to node B.
- node B queue all the Import Entries again.
- Make the processing in node A slower so a Import Entry is processed first in node B
- Check that this import entry is processed again in node A with unpredictable results.
Proposed Solution- Before starting to process an Import Entry check the status of the Import Entry to avoid processing again a Import Entry that it is not in Initial status anymore.

- Additionally consider to add a delay time when the handling node is switch before starting to search for new Import Entries to allow the node A to process queues entries.
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 0048454 closed caristu When a node is demoted as cluster node IE can be processed twice under some circumstances 
related to defect 0052457 closed Triage Platform Conn On cluster environments processing node can be switch even if current node is alive 
related to 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 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2023-05-16 09:45gorkaionNew Issue
2023-05-16 09:45gorkaionAssigned To => Triage Platform Conn
2023-05-16 09:45gorkaionModules => Core
2023-05-16 09:45gorkaionTriggers an Emergency Pack => No
2023-05-16 10:17gorkaionIssue cloned0052456
2023-05-16 10:17gorkaionRelationship addedrelated to 0052456
2023-05-16 10:30gorkaionRelationship addedrelated to 0052457
2023-05-16 10:31gorkaionRelationship addedrelated to 0052445
2023-05-18 14:33ngarciaIssue Monitored: ngarcia
2023-05-18 17:09adrianromeroAssigned ToTriage Platform Conn => caristu
2023-05-19 11:36caristuRelationship addedrelated to 0048454
2023-05-22 11:45caristuRelationship deletedrelated to 0048454
2023-05-22 11:46caristuRelationship addedduplicate of 0048454
2023-05-22 11:46caristuReview Assigned To => caristu
2023-05-22 11:46caristuStatusnew => closed
2023-05-22 11:46caristuResolutionopen => duplicate

There are no notes attached to this issue.