lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Venner (at ning) (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1395) Integrate Katta
Date Tue, 29 Sep 2009 21:43:07 GMT

     [ https://issues.apache.org/jira/browse/SOLR-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Venner (at ning) updated SOLR-1395:
-----------------------------------------

    Attachment: katta.zk.properties
                katta.node.properties
                solr-1395-1431-3.patch

/tmp/solr-1395-1431-3.patch contains an additional unit test for the query string serialization
code, and two additional classes that allow for deployment to katta.

WIth this jar, a katta client node may be started via
katta-daemon.sh start katta\ startNode org.apache.solr.katta.DeployableSolrKattaServer
The system properties that control the node startup are

solr.server.name - the property to look for the server name, default proxy
solr.home - the property to look for the server root, default solrHome
solr.config.file - the property to look for the server config file name, default solr.xml

These will be used to find a solr configuration to run the embedded server which will search
the deployed shards.

Index shards may be deployed via the standard katta mechanism of katta addIndex index-name
shared-path-to-index
I use the zip files produced by SOLR-1301 and deploy from hdfs.

For searching, create a solr configuration with a handler:

  <requestHandler name="standard" class="solr.KattaRequestHandler" default="true">
    <!-- default values for query parameters -->
     <lst name="defaults">
       <str name="echoParams">explicit</str>
       <!--
       <int name="rows">10</int>
       <str name="fl">*</str>
       <str name="version">2.1</str>
        -->
	   <str name="shards">*</str>
     </lst>
  </requestHandler>

This will search all deployed shards, replace the shards parameter with an explicit shard
list if you only wish to query an explicit subset with this query handler.

The solr instance for search will need the zookeeper information.

conf/katta.node.properties
conf/katta.zk.properties, replace the zookeeper nodes with your clusters nodes

I tend to run java -d64 -Xmx2g -Dkatta.request.timeout=100000 start.jar
for my testing work as my cluster is on the far side of a couple of firewals



> Integrate Katta
> ---------------
>
>                 Key: SOLR-1395
>                 URL: https://issues.apache.org/jira/browse/SOLR-1395
>             Project: Solr
>          Issue Type: New Feature
>    Affects Versions: 1.4
>            Reporter: Jason Rutherglen
>            Priority: Minor
>             Fix For: 1.5
>
>         Attachments: hadoop-core-0.19.0.jar, katta-core-0.6-dev.jar, katta.node.properties,
katta.zk.properties, log4j-1.2.13.jar, solr-1395-1431-3.patch, solr-1395-1431.patch, SOLR-1395.patch,
SOLR-1395.patch, SOLR-1395.patch, test-katta-core-0.6-dev.jar, zkclient-0.1-dev.jar, zookeeper-3.2.1.jar
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> We'll integrate Katta into Solr so that:
> * Distributed search uses Hadoop RPC
> * Shard/SolrCore distribution and management
> * Zookeeper based failover
> * Indexes may be built using Hadoop

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message