Description:
------------
If you have 2 or more Gearman servers, when one goes down 
the client failover doesn't work and you get the following 
error:

 gearman_connection_flush:lost connection to server (32).

I have additional observations about this:

1)  The order in which you add servers determines which 
server is ignored.  It appears that the server that must not 
go down is the last of 2 servers.
2)  Try this:   if you addServer() A and then B servers, 
then shut down gearmand on server A everything works fine.  
Shut down gearmand on server B and you get the error.

Others have reported this bug here:

https://answers.launchpad.net/gearmand/+question/112134

Reproduce code:
---------------
$gearman->addServer('192.168.0.1');
$gearman->addServer('192.168.0.2');
$job_handle[]= $gearman->doBackground("do_code", serialize($data));
if ($gearman->returnCode() != GEARMAN_SUCCESS) {
  $error = $gearman->error();
}

Expected result:
----------------
When you take down either server, the client should failover 
to sending jobs to the other server.  This is only true as 
long as you take down only the first server added by 
addServer().





Actual result:
--------------
In the sample code, if you take down gearman on 192.168.0.1 
the doBackground call will continue to succeed. If you only 
take down 192.168.0.2 then you will get : 

gearman_connection_flush:lost connection to server (32)