Hi Team,
my customer is observing such strange behaviour:
- If Vertica_node_A1 goes down, AD integration does not move anywhere else. You cannot connect database with AD account in 15 minutes. After 15 min (or what ever the cycletime is), AD integrations is done through Vertica_node_A1
- Customer tested with his tester with loadbalancing on (with his own AD account, takes 1 session/1 s), when other servers were rebooted, He could still get connections to all other nodes. However when rebooting Vertica_node_A1 , also all the other servers connection got the same error message (could not connect anywhere)
What is strange AD integration started to work from A2 after 15 minutes even though A1 was still down (seen from ldap_link_events).
** ->Question <-**
How to configure VERTICA, that AD is moving to another server at the same time, when A1 is getting down ? Otherwise the users are not able to login before AD will be moved into A2
I havent seen any parameter - that would be related to this:LDAPLinkSearchTimeout = 10 (sec), but it is not related to this....
- LDAPLinkRetryNumber = 10
Cheers
M
