On Mon, Dec 19, 2011 at 6:21 AM, Rustam Aliyev <rus...@code.az> wrote: > The only thing which looks suspicious to me are these errors: > > Dec 18 04:01:28 ec01 object-server ERROR container update failed with > 10.0.1.3:6001/d01 (saving for async update later): Timeout (3s) (txn: > txdf95ad5a10844ee0b74d70d8a7638082) > Dec 18 04:01:28 ec01 object-server ERROR container update failed with > 10.0.1.2:6001/d01 (saving for async update later): Timeout (3s) (txn: > txee2545ba4610430fa3a6a166ca50c574) > Dec 18 04:01:28 ec01 object-server ERROR container update failed with > 10.0.1.8:6001/d01 (saving for async update later): Timeout (3s) (txn: > tx2546b29b15c643ec90a122a753dfddd3)
Yeah, that is likely to be the culprit. Each write is taking at least 3 seconds because it's timing out trying to update the container servers. So you need to debug connectivity from this object server to those IP addresses on port 6001 -- that the IP addresses and port are correct, everything's on the same network, there aren't any firewall rules blocking those connections, that the container servers are running and accepting connections, etc. I'll read through your paste in a bit and see if I notice anything. -- Mike _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp