0040747: Unnecessary wait in Import Entry Manager is causing lag in the processing of import entries even if resources are available

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0040747

Openbravo ERP

A. Platform

public

2019-05-02 13:43

2019-11-12 15:45

Reporter

marvintm

Assigned To

alostale

Priority

high

Severity

critical

Reproducibility

sometimes

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

Fixed in Version

3.0PR19Q3

Merge Request Status

Review Assigned To

caristu

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0040747: Unnecessary wait in Import Entry Manager is causing lag in the processing of import entries even if resources are available

Description

Currently the main Import Entry Manager thread is moved to sleep for an amount of time that depends on how many import entries were processed, every time the pending import entries are checked.

This is causing the mechanism to not optimally use the resources. The reason seems to be that the wait time is too big, and this means that the executor threads all finish their current tasks, and then need for this time to be finished for the main Import Entry Manager thread to look for more import entries to assign to them.

The consequence for the user is that when there is a very high amount of activity in the system, Import Entry Manager initially picks a big amount of import entries to be processed. These import entries are then processed as fast as the system can, taking into account the configuration and hardware, but even if this finishes very fast, the whole system needs to wait for this arbitrary time to end before looking for more work, and in the meantime if the activity of the system is high, more import entries arrive, and the end result is that import entry queue can grow a lot depending on the request the system receives, while the system itself is spending most of the time idle.

Steps To Reproduce

Generate a big amount of import entry requests, and verify that the import entries get accumulated, while the system spends a significant amount of time idle without processing them.

Proposed Solution

This wait time needs to be reconsidered, but at the same time the change that we do here needs to be properly validated to ensure that it doesn't affect the stability of the system.

Additional Information

Tags

No tags attached.

Relationships

related to	feature request	0037853		closed	alostale	ImportEntryManager.reportsStatus only does long time avg, useless to see any short term changes
related to	defect	0041978		closed	alostale	Import Entry data types without sequence should be sumbitted in last place