Docs
You are looking at preliminary documentation for a future release. Not what you want? See the current release documentation.
Elasticsearch.Net and NEST: the .NET clients [master] » Client Concepts - Elasticsearch.Net » Request Timeouts
«  Disabling sniffing and pinging on a request basis     Connect Timeouts  »

Request Timeoutsedit

While you can specify Request time out globally you can override this per request too

we set up a 10 node cluster with a global time out of 20 seconds. Each call on a node takes 10 seconds. So we can only try this call on 2 nodes before the max request time out kills the client call.

var audit = new Auditor(() => Framework.Cluster
    .Nodes(10)
    .ClientCalls(r => r.FailAlways().Takes(TimeSpan.FromSeconds(10)))
    .ClientCalls(r => r.OnPort(9209).SucceedAlways())
    .StaticConnectionPool()
    .Settings(s => s.DisablePing().RequestTimeout(TimeSpan.FromSeconds(20)))
);

On the second request we specify a request timeout override to 80 seconds We should now see more nodes being tried.

audit = await audit.TraceCalls(
    new ClientCall {
        { BadResponse, 9200 },
        { BadResponse, 9201 },
        { MaxTimeoutReached }
    },
new ClientCall(r => r.RequestTimeout(TimeSpan.FromSeconds(80)))
    {
        { BadResponse, 9203 },
        { BadResponse, 9204 },
        { BadResponse, 9205 },
        { BadResponse, 9206 },
        { BadResponse, 9207 },
        { BadResponse, 9208 },
        { HealthyResponse, 9209 },
    }
);
«  Disabling sniffing and pinging on a request basis     Connect Timeouts  »