You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Thanks to #605, when the client now faces 404 error, the pipeline is halted as expected.
But when the source LDES stream is recovered, manually resume the pipeline by API call, the pipeline doesn't continue consuming the LDES stream.
http://ldes-server:8080/bearb/timebased-50 is not available for moment => UPDATED status for pipeline 'bear-b-pipeline-client' to HALTED as expected
3.http://ldes-server:8080/bearb/timebased-50 is back online
4. Call API http://localhost:8082/admin/api/v1/pipeline/bear-b-pipeline-client/resume to resume the pipeline
Current behavior
In the trace of LDIO we can see the pipeline is recovered, but it doesn't restart to consume the LDES stream.
Expected behavior
The pipeline is recovered and continue consuming the stream http://ldes-server:8080/bearb/timebased-50.
If resuming the pipeline doesn't' resume the function, there is no need to resume it..
The text was updated successfully, but these errors were encountered:
A little investigation shows that the task that is responsible for everything in the ExecutorService is considered finished after an exception is thrown, which is not the case when the client is paused manually. So a way to "restart" the process(es) responsible in the client in a clean way needs to be found and implemented
Versions
ldes/ldi-orchestrator:2.6.0-SNAPSHOT
Describe the bug
Thanks to #605, when the client now faces 404 error, the pipeline is halted as expected.
But when the source
LDES
stream is recovered, manually resume the pipeline by API call, the pipeline doesn't continue consuming theLDES
stream.To Reproduce
http://ldes-server:8080/bearb/timebased-50
is not available for moment => UPDATED status for pipeline 'bear-b-pipeline-client' to HALTED as expected3.
http://ldes-server:8080/bearb/timebased-50
is back online4. Call API
http://localhost:8082/admin/api/v1/pipeline/bear-b-pipeline-client/resume
to resume the pipelineCurrent behavior
In the trace of LDIO we can see the pipeline is recovered, but it doesn't restart to consume the LDES stream.
Expected behavior
The pipeline is recovered and continue consuming the stream
http://ldes-server:8080/bearb/timebased-50
.If resuming the pipeline doesn't' resume the function, there is no need to resume it..
The text was updated successfully, but these errors were encountered: