Page History

...

Here are some suggestions for getting the fastest, most helpful solutions to your problems from the community. Be respectful of the fact that people responding to questions on the user's list are volunteering their time to answer your question! Demanding immediate answers or not showing evidence of attempting to diagnose your problem and/or see if it's been discussed elsewhere before posting does not demonstrate respect.

Even if you skip the rest of this page, try to imagine the roles are reversed. That is, you're the expert and someone from the community is asking an equivalent question. Would you, as the person answering the question, have enough information to say anything helpful? Or is the question so vague that there's nothing you can say? Far too often questions are asked that are, essentially, "It doesn't work, how can I fix it?".

...

• The Official Solr Documentation: https://lucene.apache.org/solr/documentation.html
  • In particular, check the Solr Reference Guide for the version of Solr you are using, or check the the live draftGitHub repository of the next version of the guide for the latest updates.
• The Solr Community Wiki: https://wiki.apache.org/solr/ (you are here already)
• Search the users' list archives. Try the nabble searchable archive at: http Official Apache Archives, more recent Apache Lists or the facetable navigation version from Sematext: https://oldsematext.nabble.com/Solr-f14479.html. LucidWorks and Sematext also maintain SOLR-powered archives at: http://find.searchhub.org/ and http://search-lucene.com/. com/opensee/search. *And, of course, web searches (Google, CuilDuckDuckGo, or other favorite web search engine).
  *Be aware of all the advice in the extremely well written: "How to ask questions the smart way"
  • NOTE: this document provides generic advice about asking questions, please do not attempt to contact any email address listed on that doc with your Solr questions.)
    *State the problem you're experiencing in the subject line. This allows readers with knowledge of that topic to focus in on it, or skip it if they're clueless.
    *Details matter. If you ask/state something very vague and simple like "indexing doesn't work", it usually won't be possible for anyone to figure out exactly what's gone wrong and help you.
    *Provide as much relevant context as you can. Remember that your readers have no context for your post. They haven't seen what you have (or haven't) tried. And they most certainly can't see any output. Provide this information. See below for specifics. The points below apply to all.
    *Let your readers know what you've found at the various pages in Admin UI for your collection/core at http://localhost:8983/solr/admin/. Note your local installation's URL may differ. Particularly helpful links on that page, besides the page itself, are "analysis" and "schema browser". Take some time to get familiar with the admin page, it'll provide you a wealth of information.
    *Find your SOLR log file. This will be located in our servlet container's log directory. You really, really, really, really need to find this directory.
    *One surprising thing is that often, by making the extra effort to write a clear and concise statement of the problem, the relevant context, and your attempted solutions, you'll find the solution.
    *Proofread your post, imagining that you are the expert reading it. Is there enough information that you would know what to recommend as a next step?
    *Give back by trying to answer questions that you *do* have knowledge of. You're not only helping the poster, you're allowing those with knowledge of other areas to help with other problems. As a bonus, it's one of the fastest way to learn. If you have an idea but aren't certain, just say so. People on the SOLR list are pretty gentle about correcting misconceptions; they appreciate the fact that you're making the effort to help.
    *Please write as clearly and grammatically as you can. This makes it easier to understand your problem. That said, don't worry if English isn't your first language, just do your best.

...

Other useful information you'd need if you were trying to diagnose this problem if someone * else had submitted it.

Information useful for searching problems

...

• First and foremost, the SOLR admin page and links thereon.
• Luke (google Lucene Luke). This allows you to look at your index in detail.

Links

• Sign up for the user list and send email
• Send a mail now (You have to be registered)
• In a hurry? Try the live IRC chat
• How to unsubscribe