[cisco-voip] dbrep timeout

Ed Leatherman ealeatherman at gmail.com
Tue Apr 22 14:40:32 EDT 2014


Thanks guys, I should have spelunked the archive a little bit :)


On Tue, Apr 22, 2014 at 12:01 PM, Brian Meade <bmeade90 at vt.edu> wrote:

> Use the formula on
> https://supportforums.cisco.com/document/52421/troubleshooting-cucm-database-replication-linux-appliance-modelunder "Replication
> Timeout Design Estimation".
>
> If that formula gives you more than 300 seconds, increase the repltimeout.
>
> Brian
>
>
> On Tue, Apr 22, 2014 at 11:26 AM, Ed Leatherman <ealeatherman at gmail.com>wrote:
>
>> Reviewing some docs for upgrading my primary production cluster from 8 to
>> 9.1. What constitutes a "large cluster" wrt to the db replication timeout?
>>
>>
>>    -  Use the utils dbreplication setrepltimeout CLI command to increase
>>    the database replication timeout value when upgrading large clusters so
>>    that more subscriber nodes have sufficient time to request replication.
>>    When the timer expires, the first subscriber node, plus all other
>>    subscriber nodes that requested replication within that time period, begin
>>    a batch data replication with the publisher node. The default database
>>    replication timeout value is 300 (5 minutes). Restore the timeout to the
>>    default value after the entire cluster upgrades and the subscriber nodes
>>    have successfully set up replication. For more information, see the Command
>>    Line Interface Guide for Cisco Unified Communications Solutions.
>>
>>
>> --
>> Ed Leatherman
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>


-- 
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140422/9277c144/attachment.html>


More information about the cisco-voip mailing list