directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kiran Ayyagari <kayyag...@apache.org>
Subject Re: How to set ads-repllogmaxidle other than the default 48 hours
Date Tue, 17 Dec 2013 12:28:55 GMT
On Tue, Dec 17, 2013 at 10:21 AM, Paul Bayliss <prbayliss@me.com> wrote:

> Hi Kiran,
>
> One further piece of information.
>
> I have a keepalive on the actual LDAP connection whilst this is occurring.
> The keep-alive messages are SearchRequests to the DN that I've setup as the
> base DN for the SyncRepl. The keep alives continue despite the SyncRepl
> SearchResults no longer being sent from the directory, So I believe the
> connection to be good, but the SearchEntries from the original SyncRepl
> SearchRequest are not sent after some period of time.
>
> sounds like a bug, can you file a report here
https://issues.apache.org/jira/browse/DIRSERVER

thank you

> Many thanks,
> Paul
>
> On Dec 16, 2013, at 11:40 PM, Paul Bayliss <prbayliss@me.com> wrote:
>
> > Hi Kiran,
> >
> > When a sync replication connection is established an ads-replEventLog
> objectclass entry is created with DN: ads-dsReplicaId=<some
> integer>,ou=consumers, ou=system. The ads-repllogmaxidle value is 172800
> seconds (48 hours). Is there any way to extend this time via configuration,
> to say 1 week?
> >
> > My issue is that I have a sync replication listener established on a DN
> of an entry in my directory. The connection is persistent and set up to
> refresh and persist. On changes to the entry I successfully see
> SearchResults returned to my SyncRepl client. After some period of time
> (I'm estimating 48 hours based on my logs) the SearchResults stop and
> changes to the entry at the DN no longer result in SearchResults to the
> client. In addition, I don't receive any SearchResultDone, so I have no
> indication to retry the SyncReplication connection.  I'm trying to
> establish if the 48 hour default is indeed my problem.
> >
> > Hope this clarifies and you can help!
> > Kind regards,
> > Paul
> >
> > On Dec 16, 2013, at 11:19 PM, Kiran Ayyagari <kayyagari@apache.org>
> wrote:
> >
> >> On Tue, Dec 17, 2013 at 4:57 AM, Paul Bayliss <prbayliss@me.com> wrote:
> >>
> >>> Hi,
> >>>
> >>> Is it possible to set a configuration property that will be used for
> the
> >>> ads-repllogmaxidle timeout that's used for ads-replEventLog entries?
> >>>
> >>> I didn't understand, can you rephrase the question please
> >>
> >>> I'd also like to confirm that I'm correct in my understanding that
> >>> ads-replEventLog is removed when the ads-ReplLastSentCsn time is older
> than
> >>> the the ads-repllogmaxidle value, and that ads-replLastSentCsn is
> updated
> >>> in response to a SearchEntry being delivered to a REFRESH_AND_PERSIST
> >>> replication consumer.
> >>>
> >>> no, it is not dependent on lastSentCSN, instead the server checks if a
> log
> >> is inactive(neither read nor updated)
> >> for more than the max idle time allowed, if yes, then the log will be
> purged
> >>
> >>> Many thanks in advance,
> >>> Paul
> >>
> >>
> >>
> >>
> >> --
> >> Kiran Ayyagari
> >> http://keydap.com
> >
>
>


-- 
Kiran Ayyagari
http://keydap.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message