Opened 19 months ago

Closed 9 days ago

Last modified 9 days ago

#1152 closed defect (fixed)

wcst_import concurrent will have error in petascope

Reported by: bphamhuu Owned by: bphamhuu
Priority: major Milestone: 9.5
Component: petascope Version: development
Keywords: Cc: vmerticariu, dmisev
Complexity: Medium

Description

@Alex: I don't know about this behavior (e.g allow to many users run wcst_import to server at same time). However, it will have error (in rasnet) from both terminals which run wcst_import simultaneously.

   <ows:ExceptionText>java.lang.RuntimeException : The client with client ID b58d51f0-c56e-4abb-bdbd-7d8041e71859 does not exist.</ows:ExceptionText>
    </ows:Exception>

or

  <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>java.util.NoSuchElementException : null</ows:ExceptionText>

you can close if it is invalid.

See log file below. Thanks.

Attachments (3)

log.tar.gz (8.9 MB) - added by bphamhuu 19 months ago.
log_1.tar.gz (5.1 MB) - added by bphamhuu 19 months ago.
log error
test_wcst_concurent.tar.gz (1.4 KB) - added by bphamhuu 11 months ago.

Change History (16)

Changed 19 months ago by bphamhuu

comment:1 Changed 19 months ago by mdumitru

  • Cc atoader gmerticariu added

There was a patch which fixed the NoSuchElementException? today. Maybe try updating first and report back. We should determine what causes the client id error.

comment:2 Changed 19 months ago by bphamhuu

@Alex: btw, I could not find error in petascope.log as now it is full with log like this. Do you think should remove and put to other file (e.g gprc.log) ?

[18:18:50] DEBUG NettyClientTransport@71: 
----------------INBOUND--------------------
DATA: streamId=15, padding=0, endStream=false, length=5, bytes=0000000000
------------------------------------
[18:18:50] DEBUG NettyClientTransport@71: 
----------------INBOUND--------------------
HEADERS: streamId=15, headers=DefaultHttp2Headers[grpc-status: 0], padding=0, endStream=true
------------------------------------

comment:3 Changed 19 months ago by mdumitru

Yes, please open a ticket on this.

Changed 19 months ago by bphamhuu

log error

comment:4 Changed 19 months ago by bphamhuu

@Alex: I've pulled and reinstall Rasdaman again, the error still appears when use wcst_import.sh to import coverage

here is the log http://rasdaman.org/attachment/ticket/1152/log_1.tar.gz, thanks.

    <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>java.util.NoSuchElementException : null</ows:ExceptionText>
    </ows:Exception>

comment:5 Changed 19 months ago by bphamhuu

  • Priority changed from minor to major

comment:6 Changed 19 months ago by bphamhuu

I can see one case that can make this error is when coverage_id starts with number like this "coverage_id": "1_xxxx", but in the logs above it is normal name like cov_number_*.

Do you think wcst_import.sh should check coverage_id is valid also?

comment:7 Changed 19 months ago by atoader

I've also come across the error this morning. We are investigating.

Changed 11 months ago by bphamhuu

comment:8 Changed 11 months ago by bphamhuu

  • Cc vmerticariu dmisev added; atoader gmerticariu removed
  • Milestone changed from 9.2 to 10.0

To reproduce this problem, run 3 scripts in http://rasdaman.org/attachment/ticket/1152/test_wcst_concurent.tar.gz on 3 terminal at the same time. It will show that, the progress will fail soon after few imported coverage, error from wcst_import can be see here http://pastebin.com/SA9xru5R

This functionality is useful if user wants to import multiple different coverages to Petascope in batch mode (instead of 1 sequence), but it depend on what Petascope can handle and it is not urgent.

comment:9 Changed 10 days ago by bphamhuu

  • Cc mdumitru removed
  • Milestone changed from 10.0 to 9.5

I will test this ticket tomorrow with new Petascope, and then, if it is safe enough then can close it.

comment:10 Changed 10 days ago by bphamhuu

  • Owner set to bphamhuu
  • Status changed from new to assigned

comment:11 Changed 9 days ago by bphamhuu

  • Resolution set to fixed
  • Status changed from assigned to closed

The script can run to the end of the loop without problems, so close ticket.

comment:12 Changed 9 days ago by dmisev

can you attach the script?

comment:13 Changed 9 days ago by dmisev

a ok, I guess it's this one: attachment:test_wcst_concurent.tar.gz

Note: See TracTickets for help on using tickets.