Open Stack

Thanks, John. I appreciate your response.


On Mon, Feb 10, 2014 at 12:50 PM, John Dickinson <me at not.mn> wrote:

> Moving your container servers to SSDs is the fastest way to get better
> performance out of them.
>
> Although there have been many discussions about how to do internal
> container sharding, I'm not aware of any current ongoing work there
> (although I'd love to see someone work on it).
>
> --John
>
>
>
>
> On Feb 10, 2014, at 12:32 PM, Stephen Wood <smwood4 at gmail.com> wrote:
>
> > We've been having issues with our container servers timing out and
> simply returning a 404. The container servers themselves are on busy disks
> that aren't particularly overloaded, but are definitely under load.
> >
> > The messages look like the following:
> > Feb 10 20:22:19 proxy01 swift ERROR with Container server
> storage01:6001/slot-11 re: Trying to GET
> /v1/AUTH_swift/very_busy_container: Timeout (10s) (txn:
> tx6b921c72e5524589839fe-0052f934e7
> >
> > I realize this container has too many keys, but unfortunately I cannot
> shard it for now because we need to keep parity with S3 (which does
> internal bucket sharding).
> >
> > What are the best ways to tackle busy container servers timing out?
> Should I increase the node timeout, or begin creating separate container
> servers that are running on SSDs? Is there any serious drawback to increase
> the node timeout?
> >
> > Also, has there been any update on internal container sharding? This
> feature would make S3 migrations much easier.
> >
> > Any advice would be very helpful. Thank you.
> >
> > --
> > Stephen Wood
> > www.heystephenwood.com
> > _______________________________________________
> > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to     : openstack at lists.openstack.org
> > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Stephen Wood
www.heystephenwood.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140210/44b26b99/attachment.html>