Datahub Manages response from single file

Creation date: 13/03/2023 16:18    Updated: 13/03/2023 16:18   #datahubsetting #return
Question:

< [GDEC] Order Creation Slowness in Create Order API>

Affected Environment:

PROD

Affected warehouse:

GDEC-01, GDEC-02

Screenshots of error messages:



Time when issue occurred:

01:22 AM onwards, March 3, 2023

Affected module:

Shipment Order

Detailed description of issue:

OMS reported that they are not able to push orders to Honeywell and are experiencing timeout errors. On some occasions the orders are being pushed but since around 12:00AM today, the response of the create order endpoint is very slow, creating a bottleneck of pending orders in OMS.


First level investigation/troubleshooting taken:

The following troubleshooting steps were taken:

1. GDEC Tech team tried to ping the create order endpoint and the response is around 40 seconds

2. OMS checked their logs and are getting order creation errors due to timeout (Screenshot above)

3. GDEC server admin checked server utilization and are below high level

a. 36% utilization backend

b. 6% front end

c. 14% RDS


Case replication in original warehouse:

User unable to replicate in test environment.


Answer:

There is a special setting for processing the return status from middleware when it is not in header detail format.
Flux has advise to setup certain file accordingly to make the processing faster.
Do refer to below setting for single file transmission.

 Set in parameter 7: 1 20
Number of processing threads = 20
Number of records processed per thread = 1

Click clear cache.


 Technical team advise:

There is a place in amazon settings can increase the timeout.
Our technical team advise increase till 5 minutes.

Files