Please Review : Decreasing MAX Replication Retry time

[Divya Ravikumar]

Hi All,

I need to reduce the max Replication retry time for my customer requirement  I have raised
a enhancement request with fedora(Ticket 525).

As an immediate fix I have reduced the value of  PROTOCOL_BACKOFF_MAXIMUM variable in
repl5_prot_private.h from 300 seconds to 15 seconds.

I find no impact other the max retry time limit getting reduced to 15 seconds(which is my
actual requirement) .

Does anyone see any potential flaw happening in replication due to this change.

Thanks in advance.

Regards,
Divya.R

[Rich Megginson]

On 11/16/2012 05:39 AM, Divya Ravikumar wrote:
>  converted from rtf
>  Hi All,
>  I need to reduce the max Replication retry time for my customer 
>  requirement 
What is the requirement?

>  I have raised a enhancement request with fedora(Ticket 525).
>  As an immediate fix I have reduced the value of  
>  PROTOCOL_BACKOFF_MAXIMUM variable in repl5_prot_private.h from 300 
>  seconds to 15 seconds.
>  I find no impact other the max retry time limit getting reduced to 15 
>  seconds(which is my actual requirement) .
>  Does anyone see any potential flaw happening in replication due to 
>  this change.
>  Thanks in advance.
>  Regards,
>  Divya.R
>
>
>  --
>  389-devel mailing list
>  389-devel(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/389-devel

[Divya Ravikumar]

Hi Rich,
The requirement is to minimize the replication retry time to minimum so that even if one
of the masters in the community  goes down and comes up after one hour, replication
happens immediately without manual intervention.


Thanks,
Divya.R

From: Rich Megginson [mailto:[e-mail]]
Sent: Friday, November 16, 2012 8:11 PM
To: 389 Directory server developer discussion.
Cc: Divya Ravikumar
Subject: Re: [389-devel] Please Review : Decreasing MAX Replication Retry time

On 11/16/2012 05:39 AM, Divya Ravikumar wrote:
converted from rtf
Hi All,

I need to reduce the max Replication retry time for my customer requirement

What is the requirement?


I have raised a enhancement request with fedora(Ticket 525).

As an immediate fix I have reduced the value of  PROTOCOL_BACKOFF_MAXIMUM variable in
repl5_prot_private.h from 300 seconds to 15 seconds.

I find no impact other the max retry time limit getting reduced to 15 seconds(which is my
actual requirement) .

Does anyone see any potential flaw happening in replication due to this change.

Thanks in advance.

Regards,
Divya.R





--

389-devel mailing list

[e-mail]<mailto:[e-mail]>

https://admin.fedoraproject.org/mailman/listinfo/389-devel

[Rich Megginson]

On 11/18/2012 11:40 PM, Divya Ravikumar wrote:
>  Hi Rich,
>
>  The requirement is to minimize the replication retry time to minimum 
>  so that even if one of the masters in the community  goes down and 
>  comes up after one hour, replication happens immediately without 
>  manual intervention.
>  
The default 5 minutes is too long?

>  Thanks,
>
>  Divya.R
>
>  *From:*Rich Megginson [mailto:[e-mail]]
>  *Sent:* Friday, November 16, 2012 8:11 PM
>  *To:* 389 Directory server developer discussion.
>  *Cc:* Divya Ravikumar
>  *Subject:* Re: [389-devel] Please Review : Decreasing MAX Replication 
>  Retry time
>
>  On 11/16/2012 05:39 AM, Divya Ravikumar wrote:
>
>  converted from rtf
>
>  Hi All,
>
>  I need to reduce the max Replication retry time for my customer 
>  requirement
>
>
>  What is the requirement?
>
>
>  I have raised a enhancement request with fedora(Ticket 525).
>
>  As an immediate fix I have reduced the value of  
>  PROTOCOL_BACKOFF_MAXIMUM variable in repl5_prot_private.h from 300 
>  seconds to 15 seconds.
>
>  I find no impact other the max retry time limit getting reduced to 15 
>  seconds(which is my actual requirement) .
>
>  Does anyone see any potential flaw happening in replication due to 
>  this change.
>
>  Thanks in advance.
>
>  Regards,
>
>  Divya.R
>
>
>
>
>  --
>  389-devel mailing list
>  389-devel(a)lists.fedoraproject.org  <mailto:[e-mail]>
>  https://admin.fedoraproject.org/mailman/listinfo/389-devel
>