Skip to main content

Quick Tutorial - Setup a Solr instance

Before we start installing Solr instance on any machine, we should be clear on few concepts.

  • What is Solr?
    • Solr is Apache's product and a fast open-source Java search server.
  • Why we need it?
    • Solr enables you to easily create search engine for websites, databases and files.
  • How can we install it?
    Option 1(for Windows machines) - 
      1. Extract the downloaded Solr package and copy it on C or D drive
      2. Please make sure latest version of Java is installed on machine.
      3. You can start Solr instance by below command:
        java -jar start.jar

      4. By default, Solr will run on port 8983. However you can change it ../etc/Jetty.xml file. Look for <set name="port"><SystemProperty name="jetty.port" default="8983"></set> and change it.
      5. You can keep the below command in .bet file and run it automatically.
        C:\solr-6.1.0\bin\solr" restart -h localhost -p 8984
        Option 2(for Mac machines)
        > brew install solr
        Once installed, it should start solr on default port 8983.


        Option 3 (using docker images) - 
         > docker pull solr         
        Once docker image is pulled, 
        > docker run -p 8983:8983 solr:latest        
        This should start solr on your local machine and accessible on http://localhost:8983/solr

  • Common issue of Solr and how to solve it?
    When you start creating collections in Solr, you may face this issue on Solr.
    new_core: org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Could not load conf for core new_core: Error loading solr config from /var/solr/data/new_core/conf/solrconfig.xml
    Copy the folder '
    /opt/solr/server/solr/configsets/_default/conf' and paste it in '/var/solr/data/new_core/' folder. Once copied, now create the collection with same name('new_core' in this case) and change schema value from 'schema.xml' to 'managed-schema'. It should create collection successfully.

 Please feel free to send email for any help.


    Popular posts from this blog

    Cannot alter the login 'sa', because it does not exist or you do not have permission.

    Working on projects, it can happen that 'sa' account gets locked. If it is on local machine OR development boxes, onus would be on you to fix it. If scripts and SQL steps are not working, this might help you fixing the issue. Steps to unlock 'sa' account and resetting the password. 1. Open SQL Server Configuration Manager 2. Select SQL Server Services -> 'SQL Server' service. 3. Right click on 'SQL Server' service and click on "Startup Parameters". For 2008, server "Startup Parameters" are inside Advanced tab.   4. Add '-m' in startup parameters as shown above and click on 'Add'. This will put SQL server into 'Single User Mode' and local admin will have 'Super User' rights. For 2008, server you have to add ':-m' in the last of the existing query. 5. Save the settings and Restart the service. 6. Now open the SQL Server Management Studio and connect to database using 'Windows A

    Could not load file or assembly 'Microsoft.Web.Infrastructure'

    Could not load file or assembly 'Microsoft.Web.Infrastructure, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. What 'Micorosoft.Web.Infrastructure' does? This dll lets HTTP modules register at run time. Solution to above problem: Copy 'Micorosoft.Web.Infrastructure' dll in bin folder of your project and this problem should be resolved. If you have .Net framework installed on machine, this dll should be present on it. You can search for this dll and copy it in your active project folder.   Alternatively,  you can install this dll using nuget package manager PM> Install-Package Microsoft.Web.Infrastructure -Version 1.0.0 Happy coding!!

    Dockerize a dotnet core application with SQL connectivity

    Before reading this article, I am assuming that you know Docker, Dotnet core and have a dotnet core application which is trying to connect to SQL server. Read how to build aspnet core app, docker and run the docker container. If docker container is running and you are not able to connect to database, this blog should help you fix it.  Prerequisite -  Make sure code is working via running aspnet core locally via visual studio or command line. Port 1433 is opened for connecting to SQL server. Solution If you have Docker file ready, it should somewhat look like below file -  FROM AS build-env WORKDIR /app # Copy csproj and restore as distinct layers COPY /SampleAPI/*.csproj ./ RUN dotnet restore # Copy everything else and build COPY . . WORKDIR /app/SampleAPI RUN dotnet publish -c Production -o publish # Build runtime image FROM WORKDIR /app/SampleAPI COPY --from=build-env /app/SampleAPI . WORK