[jbossts-issues] [JBoss JIRA] (JBTM-2632) Allow the setting of an initial delay in PeriodRecovery
Tom Jenkinson (JIRA)
issues at jboss.org
Thu Mar 3 16:33:00 EST 2016
[ https://issues.jboss.org/browse/JBTM-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Jenkinson moved JBEAP-3667 to JBTM-2632:
--------------------------------------------
Project: JBoss Transaction Manager (was: JBoss Enterprise Application Platform)
Key: JBTM-2632 (was: JBEAP-3667)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Recovery
(was: Transactions)
Target Release: (was: 7.backlog.GA)
Affects Version/s: (was: 7.backlog.GA)
> Allow the setting of an initial delay in PeriodRecovery
> -------------------------------------------------------
>
> Key: JBTM-2632
> URL: https://issues.jboss.org/browse/JBTM-2632
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Recovery
> Reporter: Matthew Robson
> Assignee: Tom Jenkinson
>
> Currently Periodic Recovery kicks off at the same interval on every server. As a domain mode cluster grows in size, this leads to significant contention in the DB, especially for RAC implementations. Completion time goes from milliseconds with 1 server to 20+ seconds with 20+ servers.
> In an effort to avoid this, an offset the initial start of Periodic Recovery could be provided for the nodes in the cluster.
> Periodic Recovery currently leverages 2 properties:
> <system-properties>
> <property name="RecoveryEnvironmentBean.periodicRecoveryPeriod" value="120"/>
> <property name="RecoveryEnvironmentBean.recoveryBackoffPeriod" value="10"/>
> </system-properties>
> The proposal would be to add a 3rd property, 'RecoveryEnvironmentBean.periodicRecoveryInitilizationOffset' which, when set, would be used for each node. If not set, it would default to current behavior.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbossts-issues
mailing list