Transient transfer failed errors upon write transaction

[beccati@…]

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

[Dimitar Misev]

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

[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.

[Dimitar Misev]

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