[jbossts-issues] [JBoss JIRA] (JBTM-2720) Allow the setting of an initial delay in PeriodRecovery

RH Bugzilla Integration (JIRA) issues at jboss.org
Thu Oct 6 03:30:00 EDT 2016

    [ https://issues.jboss.org/browse/JBTM-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13303277#comment-13303277 ] 

RH Bugzilla Integration commented on JBTM-2720:

Jiří Bílek <jbilek at redhat.com> changed the Status of [bug 1367187|https://bugzilla.redhat.com/show_bug.cgi?id=1367187] from ON_QA to VERIFIED

> Allow the setting of an initial delay in PeriodRecovery
> -------------------------------------------------------
>                 Key: JBTM-2720
>                 URL: https://issues.jboss.org/browse/JBTM-2720
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Recovery
>            Reporter: Matthew Robson
>            Assignee: Tom Jenkinson
>             Fix For: 4.17.35, 5.2.18.Final, 5.3.4.Final
> 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

More information about the jbossts-issues mailing list