-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
3
-
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
Support reference count | Original: 2 | New: 3 |
Support reference count | Original: 1 | New: 2 |
UIS | Original: 1 | New: 0 |
UIS | New: 1 |
Workflow | Original: JAC Suggestion Workflow 4 [ 3574202 ] | New: JAC Suggestion Workflow 3 [ 4335772 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3183827 ] | New: JAC Suggestion Workflow 4 [ 3574202 ] |
Workflow | Original: JAC Suggestion Workflow [ 3078490 ] | New: JAC Suggestion Workflow 2 [ 3183827 ] |
Support reference count | New: 1 |
Description |
Original:
h3. Problem Definition
Administrator cannot know the "per cluster" [scheduled jobs|https://confluence.atlassian.com/doc/scheduled-jobs-96567525.html] are executed in which node in Data Center. h3. Suggested Solution * Add an option to configure primary node to execute "per cluster" jobs. h3. 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 in a node that has broken index. ([Administer your Data Center search index|https://confluence.atlassian.com/doc/administer-your-data-center-search-index-879956107.html]) h3. Workaround Login to the expected node and run the scheduled job manually. |
New:
h3. Problem Definition
Administrator cannot know the "per cluster" [scheduled jobs|https://confluence.atlassian.com/doc/scheduled-jobs-96567525.html] are executed at which node in Data Center. h3. Suggested Solution * Add an option to configure primary node to execute "per cluster" jobs. h3. 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|https://confluence.atlassian.com/doc/administer-your-data-center-search-index-879956107.html]) h3. Workaround Login to the expected node and run the scheduled job manually. |