<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Latha;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks Clay.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Any possibility, this container sharding can be expected in the Queen release ?</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">-kiru</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Clay Gerrard [mailto:<a href="mailto:clay.gerrard@gmail.com">clay.gerrard@gmail.com</a>] <br><b>Sent:</b> Friday, March 09, 2018 12:33 AM<br><b>To:</b> Kirubakaran Kaliannan<br><b>Cc:</b> <a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a><br><b>Subject:</b> Re: [Openstack-operators] swift - 1 Billion object on a single container</span></p></div><p class="MsoNormal"> </p><div><p class="MsoNormal"> </p><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Thu, Mar 8, 2018 at 2:39 AM, Kirubakaran Kaliannan <<a href="mailto:kirubak@zadarastorage.com" target="_blank">kirubak@zadarastorage.com</a>> wrote:</p><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hi All,</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I am seeing lot of threads and discussion on large container issues. We also have a spec (<a href="https://specs.openstack.org/openstack/swift-specs/specs/in_progress/container_sharding.html" target="_blank">https://specs.openstack.org/openstack/swift-specs/specs/in_progress/container_sharding.html</a>) to fix this in the future releases.</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p></div></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Yes, very soon - lots of progress on the feature/deep branch</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><a href="https://review.openstack.org/#/q/status:merged+project:openstack/swift+branch:feature/deep">https://review.openstack.org/#/q/status:merged+project:openstack/swift+branch:feature/deep</a></p></div><div><p class="MsoNormal"> </p></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Do we have any performance number taken on large container or suggestion on alternatives (other than distributing object into multiple containers – which is not possible due to the nature of the application) to improve this performance ?</p></div></div></blockquote><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">you can turn down the container_update_timeout:</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><a href="https://github.com/openstack/swift/blob/master/etc/object-server.conf-sample#L64">https://github.com/openstack/swift/blob/master/etc/object-server.conf-sample#L64</a></p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">-Clay</p></div><div><p class="MsoNormal"> </p></div></div></div></div></div></body></html>