Is there a way to execute individual commands with FailFast behavior?

I have some logic using the RedLock algorithm to fire commands against multiple servers and recover if some servers are down. I recently updated from 2.2.4 to 2.7.17, and some of my tests are failing because the redis client now takes much longer to return when the server is disconnected. Switching the multiplexer to use BacklogPolicy.FailFast fixes this, but in general I want the new policy, just not for these particular operations where I want to fail quickly.

Is there a recommended way to achieve this? Should I be calling IDatabase.IsConnected() before every fail fast request and bailing if that returns false or is that going to hurt performance/have different semantics? If there's no way to achieve this, would it make sense to add a CommandFlags option to support it?

The way I simulate a downed server in my tests is as follows:

• Launch a Redis process
• Connect to it via a multiplexer
• Grab an IDatabase instance off the multiplexer
• Kill the Redis process with multiplexer.GetServer(...).Shutdown(ShutdownMode.Never);

Thanks for creating and maintaining this great library!

Start with the BacklogPolicy.FailFast behavior, IDatabase.IsConnected(), and CommandFlags, then review the reported Redis shutdown reproduction. Determine whether per-command fail-fast behavior is supported or needs an API change, and document the recommended approach or the decision on adding a CommandFlags option.