[Hadoop Wiki] Trivial Update of "InvalidJiraIssues" by SteveLoughran

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "InvalidJiraIssues" page has been changed by SteveLoughran:
https://wiki.apache.org/hadoop/InvalidJiraIssues?action=diff&rev1=4&rev2=5

Comment:
consistent title levels

  
  '''These are not bugs in Hadoop -please do not file bugs on JIRA about them'''
  
- Bug reports of the form "I can't get Hadoop to work", are going to be closed as invalid, unless there is clear evidence that the problem exists in an Apache release. 
+ Bug reports of the form "I can't get Hadoop to work", are going to be closed as invalid, unless there is clear evidence that the problem exists in an Apache release.
  
- Which raises another issue. JIRAs cannot be filed against distributions of Hadoop that aren't bundling the Apache releases of Hadoop artifacts. We can't, because we don't all track what those changes are. 
+ Which raises another issue. JIRAs cannot be filed against distributions of Hadoop that aren't bundling the Apache releases of Hadoop artifacts. We can't, because we don't all track what those changes are.
  
- === Read and Understand the Logs ===
+ == Read and Understand the Logs ==
  
- Hadoop, Java Build tools and the operating system all log messages somewhere: to screen, to hadoop service logs, to the OS logs. Learn to read these, rather than just posting them to the user lists and forums and asking for help.  
+ Hadoop, Java Build tools and the operating system all log messages somewhere: to screen, to hadoop service logs, to the OS logs. Learn to read these, rather than just posting them to the user lists and forums and asking for help.
  
   * The log messages do try to be helpful. Sometimes they are only meaningful to people who understand how Hadoop works -but you are going to have to learn that anyway.
   * Some of the log messages include URLs to pages in this wiki. Follow the links -they are there for a reason.
-  * Search engines are a surprisingly useful way of finding out what an error message machines. Before panicking and sending out messages to all known hadoop mailing lists as well as filing critical-level JIRA issues, why not copy the string from the logs and paste into the search dialog of your search engine of choice -and see what comes up. The discussions on the user list archives are always worth reading, as are any references on stack overflow. 
+  * Search engines are a surprisingly useful way of finding out what an error message machines. Before panicking and sending out messages to all known hadoop mailing lists as well as filing critical-level JIRA issues, why not copy the string from the logs and paste into the search dialog of your search engine of choice -and see what comes up. The discussions on the user list archives are always worth reading, as are any references on stack overflow.
  
- '''Finding an answer by searching for it on the web is the fastest way to get help -and log messages are ideal for searching on''' 
+ '''Finding an answer by searching for it on the web is the fastest way to get help -and log messages are ideal for searching on'''
  
  == Ask on User lists ==
  
@@ -38, +38 @@

   * Before asking questions, learn [[http://www.catb.org/~esr/faqs/smart-questions.html|how to ask smart questions]] first. It will explain why a message called "HELP!!!" isn't going to get any
   * Do not ask on the developer lists. Asking the developers for help on configuring your system is like emailing the linux-kernel mailing list for help getting /etc/fstab right. You will be silently ignored.
   * Please don't email people directly. Not only are you unlikely to get any help, it's not a good way to start to build a relationship with people you may need to work with later.
-  
+ 
  == Ask on Vendor Forums and support channels ==
  
  If you are not using out-the-box Apache Hadoop, but instead a commercial derivative, their support process should be where to begin
@@ -70, +70 @@

  
  Do
   1. Use a recent release of Hadoop. Older versions will have old bugs.
-  1. search on the web for the error string.  
+  1. search on the web for the error string.
   1. Ask on the Hadoop User lists and any vendor-specific forums or other support options they offer.
   1. Join or create a local Hadoop User Group -to find nearby people to learn from and solve problems with.
   1. Read [[http://www.catb.org/~esr/faqs/smart-questions.html|how to ask good smart questions]] before asking bad ones.
  
- Don't. 
+ Don't.
   1. File JIRA issues on problems you have trying to get your own code to compile or run.
   1. File JIRA issues on problems you have starting up your cluster, unless someone on the -user lists says "this is really a bug".
   1. Ask questions about using Hadoop on the developer lists. You will be deliberately ignored.