I'm using Nest 5.x as a part of an application to communicate with ES. When my application starts up, the following code is executed
List<Node> nodes = new List<Node>(); nodes.AddRange(config.Nodes.Select(nodeUri => CreateNode(nodeUri))); var connectionPool = new SniffingConnectionPool(nodes); var settings = new ConnectionSettings(connectionPool); settings.DefaultFieldNameInferrer(p => p); Nest.ElasticClient esClient = new Nest.ElasticClient(settings);
If my ES instance (nodeUri) is not up and running, the above code will not throw any exception during the startup, but when I actually try to index a document, then it throws an exception.
Is there any way I can ensure that nodes I'm trying to connect are active during start up itself?