syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SYNCOPE-1103) Option to disable Quartz instances across cluster
Date Tue, 06 Jun 2017 13:07:18 GMT


ASF subversion and git services commented on SYNCOPE-1103:

Commit 67ecbea39eb9d54f73ab6fcd79fdbe57de399e3b in syncope's branch refs/heads/2_0_X from
[;h=67ecbea ]

[SYNCOPE-1103] Option to put Quartz scheduler in standby, from

> Option to disable Quartz instances across cluster
> -------------------------------------------------
>                 Key: SYNCOPE-1103
>                 URL:
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 1.2.11, 2.0.4, 2.1.0
> The only considered aspect, when configuring Syncope for [high-availability|],
is related to OpenJPA's remote commit provider, at least according to the current documentation.
> However, another component is relevant within this regard, e.g. the Quartz scheduler,
which is currently simply setup by default for [clustering|].
> With such configuration, all cluster nodes are equally selectable for processing jobs;
it would be nice, though, to gain some control over this aspect, e.g. to be able to restrict
the nodes where jobs can run.
> For example, one can have 3 Syncope core nodes configured with OpenJPA remote commit
provider, and set 2 of them for processing REST requests, leaving the third dedicated for
running jobs (e.g. Pull).

This message was sent by Atlassian JIRA

View raw message