zoukankan      html  css  js  c++  java
  • multicore solr deploy process(not complete)

    根据/etc/tomcat6/Catalina/localhost/solr.xml中部署的solr.home的位置上创建
    mkdir solrm
    sudo chgrp mlzboy solrm
    sudo chmod 777 solrm

    change tomcat port:
    Tomcat runs on the port defined $CATALINA_HOME/conf/server.xml,
    configured by default to port 8080.
    in ubuntu check location here /etc/tomcat6/server.xml

    Configuring Solr Home with JNDI


    A Tomcat
    context fragments can be used to configure the JNDI property needed to
    specify your Solr Home directory.

    Just put a
    context fragment file under $CATALINA_HOME/conf/Catalina/localhost that
    looks something like this...

    $ cat
    /tomcat55/conf/Catalina/localhost/solr.xml

    <Context docBase="/some/path/solr.war" debug="0" crossContext="true" >
       <Environment name="solr/home" type="java.lang.String" value="/my/solr/home" override="true" />
    </Context>

    A few things to keep in mind:

    • The
      "conf/Catalina/localhost" directory may not exist by default in your
      installation. You may have to create it.
    • "/some/path/solr.war" is the absolute path
      to where ever you want to keep the Solr war using the appropriate
      syntax for your Operating System. In Tomcat 5.5 and later, the war file
      must be stored outside of the webapps directory for this to work.
      Otherwise, this entire Context element is ignored.
    • "/my/solr/home" should be to where you
      have created your Solr Home directory, using the appropriate syntax for
      your Operating System.
    • Prior
      to Tomcat 5.5, a "path" attribute was required for Context elements
      (starting with 5.5, the path attribute must not be used except when
      statically defining a Context in server.xml, as it will be inferred from
      the Context fragment filename.


    Enabling Longer Query Requests


    If you try
    to submit too long a GET query to Solr, then Tomcat will reject your
    HTTP request on the grounds that the HTTP header is too large; symptoms
    may include an HTTP 400 Bad Request error or (if you execute the query
    in a web browser) a blank browser window.

    If you need to enable longer queries, you can set the
    maxHttpHeaderSize attribute on the HTTP Connector element in your
    server.xml file. The default value is 4K. (See http://tomcat.apache.org/tomcat-5.5-doc/config/http.html)





  • 相关阅读:
    响应式的WEB设计
    WPF的抽奖程序
    使用Visual Studio 利用WinGDB编译和远程调试嵌入式Linux的程序
    Sqler 工具帮你解决(更新部分监控)
    YSlow相关规则的调优工具和方法
    wcf基础笔记
    HTTP协议之状态码详解
    网站首页图片滚动显示
    CodeLove初版发布
    HDFS学习– Namenode and Datanode
  • 原文地址:https://www.cnblogs.com/lexus/p/1783992.html
Copyright © 2011-2022 走看看