openstack/openstack-manuals
Code Issues Proposed changes

Merge "Use swift-swift-swift-constraints.xml"

Browse Source
This commit is contained in:
Jenkins 2013-09-23 13:46:45 +00:00 committed by Gerrit Code Review
commit 23897392c9
2 changed files with 55 additions and 96 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

57
doc/common/tables/swift-swift-swift-constraints.xml
View File

@ -15,38 +15,71 @@
</thead>
<tbody>
<tr>
<td>max_file_size=5368709122</td><td>No help text available for this option</td>
<td>max_file_size=5368709122</td>
<td>The largest normal object that can be
saved in the cluster. This is also the
limit on the size of each segment of a
large object when using the large object
manifest support. This value is set in
bytes. Setting it to lower than 1MiB will
cause some tests to fail. It is STRONGLY
recommended to leave this value at the
default (5 * 2**30 + 2).</td>
</tr>
<tr>
<td>max_meta_name_length=128</td><td>No help text available for this option</td>
<td>max_meta_name_length=128</td>
<td>The maximum number of bytes in the utf8
encoding of the name portion of a metadata
header.</td>
</tr>
<tr>
<td>max_meta_value_length=256</td><td>No help text available for this option</td>
<td>max_meta_value_length=256</td>
<td>The max number of bytes in the utf8
encoding of a metadata value.</td>
</tr>
<tr>
<td>max_meta_count=90</td><td>No help text available for this option</td>
<td>max_meta_count=90</td>
<td>The maximum number of metadata keys that can
be stored on a single account, container,
or object.</td>
</tr>
<tr>
<td>max_meta_overall_size=4096</td><td>No help text available for this option</td>
<td>max_meta_overall_size=4096</td>
<td>The maximum number of bytes in the utf8
encoding of the metadata (keys +
values).</td>
</tr>
<tr>
<td>max_header_size=8192</td><td>No help text available for this option</td>
<td>max_header_size=8192</td>
<td>The maximum number of bytes in the utf8
encoding of each header.</td>
</tr>
<tr>
<td>max_object_name_length=1024</td><td>No help text available for this option</td>
<td>max_object_name_length=1024</td>
<td>The maximum number of bytes in the utf8
encoding of an object name.</td>
</tr>
<tr>
<td>container_listing_limit=10000</td><td>No help text available for this option</td>
<td>container_listing_limit=10000</td>
<td>The default (and maximum) number of items
returned for a container listing
request.</td>
</tr>
<tr>
<td>account_listing_limit=10000</td><td>No help text available for this option</td>
<td>account_listing_limit=10000</td>
<td>The default (and maximum) number of items
returned for an account listing request.</td>
</tr>
<tr>
<td>max_account_name_length=256</td><td>No help text available for this option</td>
<td>max_account_name_length=256</td>
<td>The maximum number of bytes in the utf8
encoding of an account name.</td>
</tr>
<tr>
<td>max_container_name_length=256</td><td>No help text available for this option</td>
<td>max_container_name_length=256</td>
<td>The maximum number of bytes in the utf8
encoding of a container name.</td>
</tr>
</tbody>
</table>
</para>
</para>

94
doc/config-reference/object-storage/section_object-storage-features.xml
View File

@ -162,95 +162,21 @@
</section>
<section xml:id="object-storage-constraints">
<title>Constraints</title>
<para>The <literal>swift-constraints</literal> section in
<filename>swift.conf</filename> allows modification
of internal limits within swift. These are advanced
features for tuning the performance of the cluster and
should be altered with caution.</para>
<table rules="all">
<caption>Configuration options for swift-constraints
in swift.conf</caption>
<tbody>
<tr>
<td>Option</td>
<td>Default</td>
<td>Description</td>
</tr>
<tr>
<td>max_file_size</td>
<td>5368709122</td>
<td>the largest "normal" object that can be
saved in the cluster. This is also the
limit on the size of each segment of a
"large" object when using the large object
manifest support. This value is set in
bytes. Setting it to lower than 1MiB will
cause some tests to fail. It is STRONGLY
recommended to leave this value at the
default (5 * 2**30 + 2).</td>
</tr>
<tr>
<td>max_meta_name_length</td>
<td>128</td>
<td>the max number of bytes in the utf8
encoding of the name portion of a metadata
header.</td>
</tr>
<tr>
<td>max_meta_value_lenth</td>
<td>256</td>
<td>the max number of bytes in the utf8
encoding of a metadata value</td>
</tr>
<tr>
<td>max_meta_count</td>
<td>90</td>
<td>the max number of metadata keys that can
be stored on a single account, container,
or object</td>
</tr>
<tr>
<td>max_meta_overall_size</td>
<td>4096</td>
<td>the max number of bytes in the utf8
encoding of the metadata (keys +
values)</td>
</tr>
<tr>
<td>max_object_name_length</td>
<td>1024</td>
<td>the max number of bytes in the utf8
encoding of an object name</td>
</tr>
<tr>
<td>container_listing_limit</td>
<td>10000</td>
<td>the default (and max) number of items
returned for a container listing
request</td>
</tr>
<tr>
<td>max_account_name_length</td>
<td>256</td>
<td>the max number of bytes in the utf8
encoding of an account name</td>
</tr>
<tr>
<td>max_container_name_length</td>
<td>256</td>
<td>the max number of bytes in the utf8
encoding of a container name</td>
</tr>
</tbody>
</table>
<para>To change the OpenStack Object Storage internal
limits, update the values in the
<literal>swift-constraints</literal> section in the
<filename>swift.conf</filename> file. Use caution when you
update these values because they affect the performance in
the entire cluster.</para>
<xi:include href="../../common/tables/swift-swift-swift-constraints.xml"/>
</section>
<section xml:id="object-storage-dispersion">
<title>Cluster Health</title>
<para>There is a
<para>Use the
<literal>swift-dispersion-report</literal> tool
for measuring overall cluster health. This is
accomplished by checking if a set of deliberately
to measure overall cluster health. This tool checks
if a set of deliberately
distributed containers and objects are currently in
their proper places within the cluster. For instance,
a common deployment has three replicas of each object.