[Graviton] Instances in the 'OutOfService' state

I'm trying to get a production ready Stardog cluster up and running in AWS. I have successfully peered my VPC to the one Graviton creates and can communicate with the cluster from our application. When I look at the 3 auto scale groups that get created, they all say that the instances are healthy. When I go to the load balancer though, it typically will say that 1 of the 3 instances is actually in the 'InService' state.

If I alter the health checks of the ASGs to also include the ELB health checks, I end up just getting them all to tear down and redeploy fresh boxes in an endless loop as the ELB health check never pass. Is there a way to fix this?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.