lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (SOLR-2355) simple distrib update processor
Date Wed, 09 Feb 2011 20:53:57 GMT


Yonik Seeley commented on SOLR-2355:

Some sample configuration:

  <updateRequestProcessorChain name="distrib">
    <processor class="com.lucid.update.DistributedUpdateProcessorFactory">
      <!-- example configuration...
       "shards should be in the *same* order for every server
        in a cluster.  Only "self" should change to represent
        what server *this* is.

      <str name="self">localhost:8983/solr</str>
      <arr name="shards">
    <processor class="solr.LogUpdateProcessorFactory">
      <int name="maxNumToLog">10</int>
    <processor class="solr.RunUpdateProcessorFactory"/>

Now on any update command, you can set update.processor=distrib and have distrib indexing
controlled by the "shards" and "self" params, either configured in solrconfig, or passed in
w/ the update command.

Or if you don't want to have to specify update.processor=distrib, you can set it as the default
update processor for any update request handlers:
  <!-- CSV update handler, loaded on demand -->
  <requestHandler class="solr.CSVRequestHandler" name="/update/csv" startup="lazy">
    <lst name="defaults">
      <str name="update.processor">distrib</str>

> simple distrib update processor
> -------------------------------
>                 Key: SOLR-2355
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Yonik Seeley
>            Priority: Minor
>         Attachments:,
> Here's a simple update processor for distributed indexing that I implemented years ago.
> It implements a simple hash(id) MOD nservers and just fails if any servers are down.
> Given the recent activity in distributed indexing, I thought this might be at least a
good source for ideas.

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message