Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-12524

Manual schedule execution produces fake run records

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • rel-4-6-1
    • rel-4-9-0
    • Server
    • Security Level: Users (General product issues)
    • 1
    • UNDECIDED
    • Hide

      1) have a two-node cluster

      2) have a graph running over 30 s

      3) define a schedule to the graph above, configure the schedule not to persist the run record
      4) 'Run now' the schedule for several times

      5) for runs delegated to other cluster nodes, run record is persisted in N/A state - the execution history considers such jobs as running and displays 'Kill' actions, but the jobs cannot be killed. Moreover, these run records do not have log files.

      Show
      1) have a two-node cluster 2) have a graph running over 30 s 3) define a schedule to the graph above, configure the schedule not to persist the run record 4) 'Run now' the schedule for several times 5) for runs delegated to other cluster nodes, run record is persisted in N/A state - the execution history considers such jobs as running and displays 'Kill' actions, but the jobs cannot be killed. Moreover, these run records do not have log files.
    • Green Sprint 61
    • 2018010310000137

    Attachments

      Activity

        People

          michalicaj Jano Michalica (Inactive)
          michalicaj Jano Michalica (Inactive)
          Votes:
          0 Vote for this issue
          Watchers:
          3 Start watching this issue

          Dates

            Created:
            Updated:
            Resolved: