Rasql_Coverage is not deleted when rasserver is ingesting big collection

[Bang Pham Huu]

When ingesting a big file by wcst_import and all the rasserver are processing. One send a request to delete a collection by WCS

http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=DeleteCoverage&coverageId=test_wms_3857

then the request from Petascope can delete the coverage metadata in petascopedb, but the rasql query will not be run (I think due to server are busy and somehow it forget this request). In the end, the collection in rasdaman still exists.

rasql -q 'select c from RAS_COLLECTIONNAMES as c' --out string
Result object 2: test_wms_3857

and because petascopedb was removed this coverageId, so the request to delete in WCS will have error
​http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=DeleteCoverage&coverageId=test_wms_3857
This XML file does not appear to have any style information associated with it. The document tree is shown below.

<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" version="2.0.1" xsi:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd">
<ows:Exception exceptionCode="NoSuchCoverage">
<ows:ExceptionText>test_wms_3857</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>

[Bang Pham Huu]

the error when running a rasql meanwhile ingesting big collection happens with rasql

rasql -q 'drop collection test_wms_3857' --user rasadmin --passwd rasadmin
rasql: rasdaman query tool v1.0, rasdaman v9.3.2.
opening database RASBASE at localhost:7001...ok
Executing update query...ok
rasdaman error 206: Serialisable exception r_Ebase_dbms: error in base DBMS.
aborting transaction...ok
E0119 16:22:11.200736291   11143 tcp_client_posix.c:171]     failed to connect to 'ipv6:[fe80::225:64ff:fe9b:ad58]:7003': socket error: connection refused
E0119 16:22:11.200891948   11143 tcp_client_posix.c:171]     failed to connect to 'ipv4:10.70.11.202:7003': socket error: connection refused
E0119 16:22:11.200968677   11143 tcp_client_posix.c:171]     failed to connect to 'ipv4:192.168.122.1:7003': socket error: connection refused
E0119 16:22:12.201353679   11143 tcp_client_posix.c:171]     failed to connect to 'ipv6:[fe80::225:64ff:fe9b:ad58]:7003': socket error: connection refused
E0119 16:22:12.201402132   11143 tcp_client_posix.c:171]     failed to connect to 'ipv4:10.70.11.202:7003': socket error: connection refused
E0119 16:22:12.201426859   11143 tcp_client_posix.c:171]     failed to connect to 'ipv4:192.168.122.1:7003': socket error: connection refused
E0119 16:22:13.649848364   11143 tcp_client_posix.c:189]     failed to connect to 'ipv4:192.168.122.1:7003': timeout occurred
E0119 16:22:13.649951420   11143 tcp_client_posix.c:189]     failed to connect to 'ipv4:10.70.11.202:7003': timeout occurred