Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Cloudera Community

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Who agreed with this solution

avatar
Vamsee author-rank
Cloudera Employee

Created ‎09-25-2013 11:15 AM

Hi @shota

 

We will help you figure out the problem! 🙂

 

FYI,  if you are using CM; you needn't install any Solr packages manually. CM does the complete setup for you.

 

From what i understand from your previous comment, you installed some solr packages manually and just to make sure we are on right setup, executing "$ ps -elf | grep solr" should result in listing only one solr process running in your system.

 

Once you have confirmed this, you can try refreshing the entire service.. (Assuming you have no stored data in Solr)

  • Stop the Solr service from CM
  • Restart the ZooKeeper service from CM
  • Issue this command "$ solrctl init --force"
  • Start the Solr service back from CM

Now you can try creating some collections.. 

 

-Vamsee

 

View solution in original post

23,761
1
Who agreed with this solution