Open Stack

On Jul 2, 2013, at 1:49 AM, "Rosa, Andrea (HP Cloud Services)" <andrea.rosa at hp.com> wrote:

> Hi Vish,
> 
>> Were other commands working on the compute node? It seems much more
>> likely that the node had a hung connection to rabbit. If you are not using tcp
>> keepalives, a network hiccup (or failover) can cause half open connections
>> where the server thinks the connection is still active so it sends the message
>> but the compute node never receives it.
> 
> The compute nodes is fine, messages are delivered and when I send a new delete for the same instance, I can see the message received by the compute node.
> As I said I don't see that very often, it's a rare case but I'd like to know if the hanging lock could be an explanation.

Definitely seems like a possibility given your explanation, but I haven't seen it happen myself.

Vish

> 
>>> PS: As you are on this topic I submitted a fix to complete the 
>>> "pending" deletion when the compute service starts, it would be great 
>>> if you can have a look at it: https://review.openstack.org/33265
> 
> Regards
> --
> Andrea Rosa
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev