Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-57712

Let primary node execute "per cluster" scheduled jobs keeping other nodes standby on DC

XMLWordPrintable

    • 0
    • 3
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      Administrator cannot know the "per cluster" scheduled jobs are executed at which node in Data Center.

      Suggested Solution

      • Add an option to configure primary node to execute "per cluster" jobs.

      Why this is important

      • Because the log of scheduled job execution will be dispersed to all nodes without primary-secondary configuration.
      • To prevent the "Clean Journal Entries" job to recreate index snapshot on a node that has broken index. (Administer your Data Center search index)

      Workaround

      Login to the expected node and run the scheduled job manually.

            [CONFSERVER-57712] Let primary node execute "per cluster" scheduled jobs keeping other nodes standby on DC

            No work has yet been logged on this issue.

              Unassigned Unassigned
              nmukai Nobuyuki Mukai
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: