Greenplum Streaming Server(GPSS) jobs stop and do not restart

Products

• VMware Tanzu Data Intelligence
• VMware Tanzu Data Suite
• VMware Tanzu Data Suite
• VMware Tanzu Greenplum
• VMware Tanzu Greenplum / Gemfire

Issue/Introduction

When a job has a "schedule" defined like the example below, it may stop and not automatically start again.

sources:
   - rabbitmq:
      server: ....
    
      properties:
         eof.when.idle: 1500

option:
   schedule:
      max_retries: -1
      retry_interval: 10000ms
      auto_stop_restart_interval: 1s
      running_duration: 5m
      max_restart_times: -1

Cause

When a job completes with SUCCESS status due to source EOF (for example when "eof.when.idle" is triggered), the schedule-based restart mechanism is NOT automatically triggered. The job will need to be started using "gpsscli start <jobname>".

The restart mechanism is only triggered when the "running_duration" time is reached and "auto_stop_restart_interval" is set.

Resolution

To have the job run periodically use the "running_duration" and "auto_stop_restart_interval" settings.