-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
I've seen that the service, in some instances doesn't even start translating:
Submitted: 223 documents, 417188 bytes.
09:47:48.0863709 Status: NotStarted In progress: 0 Success: 0 Fail: 0
09:47:50.7703304 Status: NotStarted In progress: 0 Success: 0 Fail: 0
From this, it doesn't print anything else
The heartbeat still works though:
Translation Request submitted. Status: NotStarted
4.5524552 START - Translation service request with SAS token. StatusID: *************
5.7596823 Http status: 200 OK
5.7618146 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
6.979743 Http status: 200 OK
6.9816031 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
8.1819809 Http status: 200 OK
8.183962 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
9.385535 Http status: 200 OK
9.3875677 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
10.5896654 Http status: 200 OK
10.5915891 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
11.8077684 Http status: 200 OK
11.809774 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
13.0188996 Http status: 200 OK
13.0210184 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
14.2335563 Http status: 200 OK
14.2354616 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
15.4479572 Http status: 200 OK
15.4498513 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
16.6604599 Http status: 200 OK
16.6623357 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
The thread 0x67d4 has exited with code 0 (0x0).
The thread 0xa1d0 has exited with code 0 (0x0).
The thread 0x77f4 has exited with code 0 (0x0).
The thread 0xa694 has exited with code 0 (0x0).
17.8749834 Http status: 200 OK
The thread 0xaac8 has exited with code 0 (0x0).
The thread 0x38d0 has exited with code 0 (0x0).
17.879706 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
The thread 0x5ea4 has exited with code 0 (0x0).
The thread 0x9af8 has exited with code 0 (0x0).
The thread 0x98d8 has exited with code 0 (0x0).
The thread 0x4458 has exited with code 0 (0x0).
The thread 0x5f20 has exited with code 0 (0x0).
The thread 0x376c has exited with code 0 (0x0).
The thread 0x3374 has exited with code 0 (0x0).
The thread 0x45f4 has exited with code 0 (0x0).
The thread 0x68dc has exited with code 0 (0x0).
The thread 0x2370 has exited with code 0 (0x0).
The thread 0x5d0c has exited with code 0 (0x0).
The thread 0x1998 has exited with code 0 (0x0).
The thread 0x38bc has exited with code 0 (0x0).
The thread 0x5488 has exited with code 0 (0x0).
The thread 0x1e1c has exited with code 0 (0x0).
The thread 0x56d4 has exited with code 0 (0x0).
19.0858959 Http status: 200 OK
19.0873632 Service status: 23/06/2023 10:06:49 +00:00 NotStarted
The thread 0x813c has exited with code 0 (0x0).
20.3029608 Http status: 200 OK
....
This happens consistently when I'm trying to translate a high number of documents (200 for instance), but for lower amounts with the exact same settings (storage strings, token, glossaries, etc.) it works well.
If I check in Azure, the three blob containers have been created (glossary, target and source) and have all the files there. So it seams that for some reason the translator just doesn't start. Any ideas why this might happen??
Metadata
Metadata
Assignees
Labels
No labels