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=9&rev2=10 Comment: Update text and insert video links - This page tries to explain why some issues on the Apache Hadoop JIRA categories get closed as'invalid'. + = Invalid JIRA Issues = + This page tries to explain why some issues on the Apache JIRA get closed as 'invalid'. + - The JIRA server at https://issues.apache.org/jira/ is used for two things + The [[https://issues.apache.org/jira/|Apache JIRA server]] is used for two things 1. discussing and co-ordinating feature development of Apache Hadoop. We welcome people who want to get involved with this. - 1. reporting fixing bugs in the code + 1. reporting and fixing bugs in the code What it is not is ''a way of people reporting their "I couldn't get Hadoop to work" problems''. @@ -21, +23 @@ 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 Big Data Stacks that aren't bundling the Apache releases of Hadoop artefacts. We can't, because we don't all track what those changes are. + + Here's a video on how to file good and bag bugs: + + * [[http://youtu.be/NaJlRk5aTRQ|Help! My Hadoop doesn't work!]] + * [[http://www.slideshare.net/steve_l/2014-0110-reporting-a-bug |Accompanying slides]] + + Please look at the video and understand why your JIRA was closed with a reference to this page. Then follow some of the suggestions below to help debug your cluster. == 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''' - == Ask on User lists == + == Ask on the User Mailing Lists == + * The [[http://hadoop.apache.org/general_lists.html#User|hadoop-user]] mailing list is the place at Apache where discussions on installation and configuration problems should take pace. * 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 == + == 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 + If you are not using out-the-box Apache Hadoop, but instead a commercial Bug Data Stack, their support process should be your starting point * If you have any installation issues -the vendors are the only place to expect help. * These [[http://wiki.apache.org/hadoop/Distributions%20and%20Commercial%20Support|vendors]] provide their own mailing lists and forums. Please try there. * They also provide (paid) support in some form or other. If Hadoop is critical for your organisation, and you aren't willing or able to learn to be self-sufficient, then you need to consider these. + * Any closed source parts of their stack cannot be addressed via ASF mailing lists or bug trackers. == Read the source, books and online articles == + - * There are a number of quality [[Books|Books on Hadoop]]. These are worthwhile investment. + * There are a number of quality [[Books|Books on Hadoop]]. These are worthwhile investments. * There's lots of online articles -though you should seek recent articles that cover the version of Hadoop you are using. * The source is all there [[http://svn.apache.org/viewvc/hadoop/common/trunk/|for you to explore]]. The source is ideal when you are really trying to understand the logs. Some IDEs (example: IntelliJ IDEA) will take a stack trace and work out the source tree, and you can search for all or part of an error string to find out its origin too. Debugging your own problems is a pragmatic way to learn your way round that source tree -just make sure you have the exact version of the source that you are running, so the stack traces match your source. == Keep your version of Hadoop current == + Finally: the development and testing goes on Hadoop 2.2+, with some maintenance of branch 1, with Hadoop 1.2.1 being the latest (as of December 2013). If you have a problem with an older version of Hadoop: upgrade. If you aren't prepared to upgrade, you can't expect any help at all. Returning to JIRA, it may seem unfair for the developers not to care about your "critical" issue and close it as invalid, despite the fact they are clearly the experts in Hadoop internals. However they -we- are busy trying to build the future of Hadoop, ''the operating system for data''. Most of the people working on this are being paid to do so, either from companies whose business is built around selling supported Hadoop-based products, or from people who use in production internally. None of these people have the time to help you -because if they did help everyone with a problem, they'd never get anything done.
