TCP reset issue

it does have a self-ip address on that subnet.

 

 

but furthermore, we believe we have the issue being isolated to the health monitor, which needs more than the defaults.

 

 

from the application's manual:

 

Use scripting for load balancers. For example, you can use

 

http://[host]:[port]/admin?op=ping on the load balancer to check

 

whether the Dgraph process is running on this port. If it is not running,

 

the load balancer fails over to another port, and directs queries to the

 

MDEX Engine that is currently available.

 

 

so what we are doing is creating monitors for the individual pool members. no monitors are to be applied at the pool-level or node-level.

 

 

the application is endeca.... if anyone's ever played with that running behind an LTM, let me know.

 

 

Thanks!