Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-11477 book.xml has Docbook validity issues (again) (Misty Stanley-Jones)

This commit is contained in:
Jonathan M Hsieh 2014-07-09 18:08:19 -07:00
parent eafa9f6c1f
commit f59804a855
2 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/main/docbkx/configuration.xml
View File

@ -1303,7 +1303,7 @@ index e70ebc6..96f8c27 100644
</section> </section>
</section> </section>
<section <section
xml:id="hbase.regionserver.handler.count"> xml:id="hbase.regionserver.handler.count-description">
<title><varname>hbase.regionserver.handler.count</varname></title> <title><varname>hbase.regionserver.handler.count</varname></title>
<para> This setting defines the number of threads that are kept open to answer incoming <para> This setting defines the number of threads that are kept open to answer incoming
requests to user tables. The rule of thumb is to keep this number low when the payload per requests to user tables. The rule of thumb is to keep this number low when the payload per

19
src/main/docbkx/developer.xml
View File

@ -1020,17 +1020,20 @@ As you can see from the log, ChaosMonkey started the default PeriodicRandomActio
The various properties that can be configured and their default values can be found listed in the The various properties that can be configured and their default values can be found listed in the
<classname>org.apache.hadoop.hbase.chaos.factories.MonkeyConstants</classname> class. <classname>org.apache.hadoop.hbase.chaos.factories.MonkeyConstants</classname> class.
If any chaos monkey configuration is missing from the property file, then the default values are assumed. If any chaos monkey configuration is missing from the property file, then the default values are assumed.
For example: For example:</para>
<console><prompt>$</prompt> <userinput>bin/hbase org.apache.hadoop.hbase.IntegrationTestIngest -m slowDeterministic -monkeyProps monkey.properties</userinput></console> <programlisting>
The above command will start the integration tests and chaos monkey passing the properties file <filename>monkey.properties</filename>. $<userinput>bin/hbase org.apache.hadoop.hbase.IntegrationTestIngest -m slowDeterministic -monkeyProps monkey.properties</userinput>
Here is an example chaos monkey file: </programlisting>
<programlisting>sdm.action1.period=120000 <para>The above command will start the integration tests and chaos monkey passing the properties file <filename>monkey.properties</filename>.
Here is an example chaos monkey file:</para>
<programlisting>
sdm.action1.period=120000
sdm.action2.period=40000 sdm.action2.period=40000
move.regions.sleep.time=80000 move.regions.sleep.time=80000
move.regions.max.time=1000000 move.regions.max.time=1000000
move.regions.sleep.time=80000 move.regions.sleep.time=80000
batch.restart.rs.ratio=0.4f</programlisting> batch.restart.rs.ratio=0.4f
</para> </programlisting>
</section> </section>
</section> </section>
</section> <!-- tests --> </section> <!-- tests -->
@ -1635,7 +1638,7 @@ If a committer wishes to improve an unacceptable patch, then it should first be
<listitem><para>Include the Jira issue id in the commit message, along with a short description of the change and the name of the contributor if it is not you. <listitem><para>Include the Jira issue id in the commit message, along with a short description of the change and the name of the contributor if it is not you.
Be sure to get the issue id right, as this causes Jira to link to the change in Subversion (use the issue's &quot;All&quot; tab to see these). </para></listitem> Be sure to get the issue id right, as this causes Jira to link to the change in Subversion (use the issue's &quot;All&quot; tab to see these). </para></listitem>
<listitem><para>Resolve the issue as fixed, thanking the contributor. <listitem><para>Resolve the issue as fixed, thanking the contributor.
Always set the &quot;Fix Version&quot; at this point, but please only set a single fix version, the earliest release in which the change will appear. </para></listitem></orderedlist><para><anchor id="Documentation"/> </para> Always set the &quot;Fix Version&quot; at this point, but please only set a single fix version, the earliest release in which the change will appear. </para></listitem></orderedlist>
<section xml:id="committer.amending.author"> <section xml:id="committer.amending.author">
<title>Add Amending-Author when a conflict cherrypick backporting</title> <title>Add Amending-Author when a conflict cherrypick backporting</title>