Opened 6 years ago

Closed 3 years ago

#98 closed defect (fixed)

Transient transfer failed errors upon write transaction

Reported by: beccati@… Owned by:
Priority: trivial Milestone: Future
Component: server Version: 8.2
Keywords: Cc:
Complexity: Very Hard

Description

While performing data ingestion tests I've detected a possibly bogus error condition that presents before a write transaction but signas a generic transfer failed instead.

I have a script that performs data load of several files and retries upon error every 30 seconds, here follows the output indicating the issue:

output is: ERROR - rimport::main, l. 1200: Exception: Transfer Failed
output is: ERROR - rimport::main, l. 1200: RasManager? Error: Write transaction in progress, please retry again later.
output is: ERROR - rimport::main, l. 1200: RasManager? Error: Write transaction in progress, please retry again later.

At fourth attempt data is loaded.

I suggest finding a way to have the first occurrence of the error to detect the write transaction, giving consistent messages to the error cause, if it is the write transaction as it would seem

Change History (4)

comment:1 Changed 6 years ago by dmisev

It seems like a problem in the client, rimport, not in the server?

comment:2 Changed 6 years ago by beccati@…

I think transfer failed is an error raised by the server since we detected it also with rasql sometimes. I think rasimport only reports back the server side error.

comment:3 Changed 5 years ago by pbaumann

  • Milestone set to Future
  • Priority changed from minor to trivial

comment:4 Changed 3 years ago by dmisev

  • Complexity set to Very Hard
  • Resolution set to fixed
  • Status changed from new to closed

Fixed by now, by catching segfaults in the server and terminating gracefully.

Note: See TracTickets for help on using tickets.