> It's not builtin to Solr,
I should clarify that part... index replication/distribution is a part
of Solr, but it's *very* loosely coupled (and not enabled or set-up by
default). So you can come up with alternate ways of doing it if you
need multiple searchers for high-availability or traffic sc
On 4/7/06, Mike Austin <[EMAIL PROTECTED]> wrote:
> When is the replication part done or what is it used for? I need to get more
> familar with that.
It's not builtin to Solr, and it's only needed if you want a single
master Solr instance that you update, and automated copying of the
index that cr
When is the replication part done or what is it used for? I need to get more
familar with that.
What do you mean by hard links and rsync?
>From what I read it is ok to run tomcat and IIS together, you just need to
have a connector for certain things. However, if I call the servlets from my
asp pa
The Solr server itself requires Java 1.5 and an application server which
support Servlet 2.4.
I know nothing about ASP.NET so I don't know if that supports Servlet 2.4 or
not.
Shell support is needed for replication, which is done by a bunch of shell
scripts.
The current implemenation for replicat
Mike,
I recommend you use either Tomcat or Jetty. Personally, I am just
developing with the example application (thanks again to the Solr
creators for a nicely done example app) which has Jetty embedded. I
took the example app directory, copied it to my project, tweaked the
configuratio
