directory-fortress mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yudhi Karunia Surtan <yudh...@apache.org>
Subject Re: Supporting LDAP HA client
Date Tue, 17 Apr 2018 15:42:57 GMT
Ok shawn..
I think it is possible to use keyedpool too, because it able act as
arbiter. Let me finish this thing and update u once after it finished.

On Tue, Apr 17, 2018, 22:18 Shawn McKinney <smckinney@apache.org> wrote:

>
> > On Apr 16, 2018, at 1:02 PM, Yudhi Karunia Surtan <yudhiks@apache.org>
> wrote:
> >
> > My idea is a bit different with ldaptive implementation which they mostly
> > do the check before giving the connection. For fortress or ldap-api i
> > propose that the the client need to understand which node is healthy and
> > give only the health one or thrown exception if all bad.
>
> Agreed
>
> >
> > On Apr 16, 2018, at 1:02 PM, Yudhi Karunia Surtan <yudhiks@apache.org>
> wrote:
> >
> > I still don't know how big the changes will be but i think better if I
> try
> > to put it on the code first and later all of you can give a feedback
> about
> > it. It might changes the current LdapConnectionProvider class.
>
> That sounds like a good plan to me.
>
> >
> > On Apr 16, 2018, at 1:02 PM, Yudhi Karunia Surtan <yudhiks@apache.org>
> wrote:
> >
> > Do you have an idea how should ldap health check should be?
> > Is that necessary to use bind command or something like telnet should
> work?
>
> I’d think the health check’s purpose is to make sure that server is
> responding in as lightweight a way as possible.  Bind is too heavy.
> Telnet’s a possibility, but this is something we’ll vet with on the dev’prs
> list.  For your experiment, anything will work knowing it may change later.
>
> Thanks,
> Shawn
>
>
>
>

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