Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Proxy Timeout Error when Calling Stored Procedure

Description

Running a stored procedure to pull Mobile data, the HPCC platform times out when returning data. This also results in blocking other procedures due to the timeout, may be due to the procedure continuing to run regardless of the timeout.
This is seen both in wsSQL as a call, and a direct call for the stored procedure within Thor.

-Target cluster = Thor
-Procedures affected = Q_M1 & Q_M2

This is not occurring with other procedures published on the cluster.

Environment

HPCC & wsSQL

Attachments

3

Activity

Rodrigo Pastrana 
June 8, 2016 at 2:51 PM

I'm closing this issue due to inactivity.
Please feel free to re-open if there is still an issue. Thanks.

Brittney Monroe 
May 4, 2016 at 9:32 PM

Rodrigo Pastrana Currently waiting for Al Matthews (RELX) to move the stored procedures to Roxie. I will update once we have that all set. Thank you!

Rodrigo Pastrana 
May 4, 2016 at 8:18 PM

have you been able to move forward with this issue?

Rodrigo Pastrana 
April 25, 2016 at 3:20 PM
(edited)

I ran a few tests on your cluster (RX cluster) and I found a couple of interesting things:
1 - q_m1 seems to run indefinitely when not provided an input parameter - this needs to be addressed by the ECL developer which created the query
2 - q_m1 took 24 secs to execute when provided a parameter value '387933' - this type of delay might not be acceptable, and should be addressed by ECL developer.
3 - Thor is a single threaded component and request should be expected to queue up - q_m1 running for a long time would create a back-log and could cause timet-outs. The cluster doesn't seem well suited for these types of jobs and it might need to have multithors/roxies added to it

How can we get this cluster updated so the stored procedures can be ran on roxie or multithor?

Rodrigo Pastrana 
April 25, 2016 at 12:54 PM

can we transfer this issue to WSSQL?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Priority

Created April 22, 2016 at 6:23 PM
Updated June 8, 2016 at 2:51 PM
Resolved June 8, 2016 at 2:51 PM