flushing a bucket seems to try to trigger autofailover

Scenario: Set up a three node cluster. Turn on autofailover at 30 seconds. Load a bucket with a moderate amount of data. Enable flush for the bucket. Do the bucket flush.

Expected behavior: bucket flush happens with no complaints.
Observed behavior: complaints in the log about trying to failover, but failing to do so because more than one node is 'down'

Event Module Code Server Node Time
Could not auto-failover node ('ns_1@192.168.1.204'). There was at least another node down.
auto_failover003 ns_1@192.168.1.201 23:42:43 - Thu Mar 20, 2014
Could not auto-failover node ('ns_1@192.168.1.201'). There was at least another node down.
auto_failover003 ns_1@192.168.1.201 23:42:43 - Thu Mar 20, 2014
Could not auto-failover node ('ns_1@192.168.1.200'). There was at least another node down.
auto_failover003 ns_1@192.168.1.201 23:42:43 - Thu Mar 20, 2014
Flushing bucket "named" from node 'ns_1@192.168.1.201' ns_orchestrator000 ns_1@192.168.1.201 23:42:25 - Thu Mar 20, 2014