Question

INFO Pipeline - Destroying pipeline with reason=FINISHED

  • 30 January 2023
  • 3 replies
  • 32 views
J
Rank

Hi,

 
We created a Pipeline that has a CRON scheduler, and calls multiple other pipelines.
this pipeline had been running fine, but since today anytime we start the pipeline it would immediately complete with Finished Status, on checking the logs the below is 
what we found. Complete log attached
 
DEBUG PipelineConfigurationValidator - Pipeline 'BigDaddyOr1ef6605f-4617-42c3-b8e8-6b178394e717' validation. valid=true, canPreview=true, issuesCount=0
 [stage:] INFO  StandaloneAndClusterRunnerProviderImpl - Pipeline execution mode is: STANDALONE
[runner:] [thread:webserver-29331] [stage:] DEBUG ManagerResource - Status is FINISHED
 [runner:] [thread:webserver-29331] [stage:] DEBUG LogUtil - Logger 'pipeline.BigDaddyOr1ef6605f-4617-42c3-b8e8-6b178394e717.0.state' already exists
2 Attachments

3 replies

Bikram
Rank
Userlevel 5
Badge +1

@Jay_66 

The attached file is not accessible.

can you please try to rerun the job by selecting reset from origin option and check if it ran the job or not.

 

 

1 Attachment
J
Rank

Hi, Reset origin does not help. We figured we have to restart the streamsets server whenever this happens. That is the only way out with the demo version.

Bikram
Rank
Userlevel 5
Badge +1

ok nice to know that it resolve the issue.

Reply


Terms & Conditions