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

Edit of the mailing list/search archive section 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1234636 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2012-01-22 22:25:50 +00:00
parent 0d61857881
commit d8610080d2
2 changed files with 14 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/docbkx/preface.xml
View File

@ -49,7 +49,7 @@
Distributed Computing, then you are in for Distributed Computing, then you are in for
some interesting times. First off, distributed systems are some interesting times. First off, distributed systems are
hard; making a distributed system hum requires a disparate hard; making a distributed system hum requires a disparate
skillset that needs span systems (hardware and software) and skillset that spans systems (hardware and software) and
networking. Your cluster' operation can hiccup because of any networking. Your cluster' operation can hiccup because of any
of a myriad set of reasons from bugs in HBase itself through misconfigurations of a myriad set of reasons from bugs in HBase itself through misconfigurations
-- misconfiguration of HBase but also operating system misconfigurations -- -- misconfiguration of HBase but also operating system misconfigurations --

20
src/docbkx/troubleshooting.xml
View File

@ -198,17 +198,23 @@ export HBASE_OPTS="-XX:NewSize=64m -XX:MaxNewSize=64m <cms options from above
</section> </section>
<section xml:id="trouble.resources"> <section xml:id="trouble.resources">
<title>Resources</title> <title>Resources</title>
<section xml:id="trouble.resources.lists">
<title>Dist-Lists</title>
<para>Sign up for the <link xlink:href="http://hbase.apache.org/mail-lists.html">HBase Dist-Lists</link> and post a question. 'Dev' is aimed at the
community of developers actually building HBase and for features currently under development, and 'User' for generally used for questions on released
versions of HBase.
</para>
</section>
<section xml:id="trouble.resources.searchhadoop"> <section xml:id="trouble.resources.searchhadoop">
<title>search-hadoop.com</title> <title>search-hadoop.com</title>
<para> <para>
<link xlink:href="http://search-hadoop.com">search-hadoop.com</link> indexes all the mailing lists and is great for historical searches. <link xlink:href="http://search-hadoop.com">search-hadoop.com</link> indexes all the mailing lists and is great for historical searches.
Search here first when you have an issue as its more than likely someone has already had your problem.
</para>
</section>
<section xml:id="trouble.resources.lists">
<title>Mailing Lists</title>
<para>Ask a question on the <link xlink:href="http://hbase.apache.org/mail-lists.html">HBase mailing lists</link>.
The 'dev' mailing list is aimed at the community of developers actually building HBase and for features currently under development, and 'user'
is generally used for questions on released versions of HBase. Before going to the mailing list, make sure your
question has not already been answered by searching the mailing list archives first. Use
<xref linkend="trouble.resources.searchhadoop" />.
Take some time crafting your question<footnote><para>See <link xlink="http://www.mikeash.com/getting_answers.html">Getting Answers</link></para></footnote>; a quality question that includes all context and
exhibits evidence the author has tried to find answers in the manual and out on lists
is more likely to get a prompt response.
</para> </para>
</section> </section>
<section xml:id="trouble.resources.irc"> <section xml:id="trouble.resources.irc">