syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (SYNCOPE-1103) Option to disable Quartz instances across cluster
Date Tue, 06 Jun 2017 13:07:18 GMT

     [ https://issues.apache.org/jira/browse/SYNCOPE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Francesco Chicchiriccò resolved SYNCOPE-1103.
---------------------------------------------
    Resolution: Fixed

> Option to disable Quartz instances across cluster
> -------------------------------------------------
>
>                 Key: SYNCOPE-1103
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1103
>             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|https://syncope.apache.org/docs/reference-guide.html#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|http://www.quartz-scheduler.org/documentation/quartz-2.2.x/configuration/ConfigJDBCJobStoreClustering.html].
> 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
(v6.3.15#6346)

Mime
View raw message