Yes, 303 looks very promising. And I would like to get involved. I have
gone to the JIRA thread and very impressed by the activity going on
there. It is THE hangout :-)
Following up, does anyone (especially Yonik or Sharad) have any
documentation of this feature? Such as goals, use cases, requ
On 15-Jan-08, at 9:23 PM, Srikant Jakilinki wrote:
2) Solr that has to handle a large collective index which has to be
split up on multi-machines
- The index is ever increasing (TB scale) and dynamic and all of it
has to be searched at any point
This will require significant development on you
On 16-Jan-08, at 11:09 AM, Srikant Jakilinki wrote:
Thanks for that Shalin. Looks like I have to wait and keep track of
developments.
Forgetting about indexes that cannot be fit on a single machine
(distributed search), any links to have Solr running in a 2-machine
environment? I want to
Solr provides a few scripts to create a multiple-machine deployment. One box
is setup as the master (used primarily for writes) and others as slaves.
Slaves are added as per application requirements. The index is transferred
using rsync. Look at http://wiki.apache.org/solr/CollectionDistribution fo
Thanks for that Shalin. Looks like I have to wait and keep track of
developments.
Forgetting about indexes that cannot be fit on a single machine
(distributed search), any links to have Solr running in a 2-machine
environment? I want to measure how much improvement there will be in
performanc
Look at http://issues.apache.org/jira/browse/SOLR-303
Please note that it is still work in progress. So you may not be able to use
it immeadiately.
On Jan 16, 2008 10:53 AM, Srikant Jakilinki <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> There is a requirement in our group of indexing and searching s
Hi All,
There is a requirement in our group of indexing and searching several
millions of documents (TREC) in real-time and millisecond responses.
For the moment we are preferring scale-out (throw more commodity
machines) approaches rather than scale-up (faster disks, more
RAM). This is in-turn in
