A document sent to any Solr Cloud node will be sent to the right place.
Shard merging and splitting is not supported now. There is work on shard
splitting: https://issues.apache.org/jira/browse/SOLR-3755
wunder
On Apr 6, 2013, at 4:15 PM, Furkan KAMACI wrote:
> My last questions.
>
> 1) If I
My last questions.
1) If I sent document to a replica does it pass document to shard leader
and do you mean that even if I send document to shard leader does it can
pass that document
one of replicas to be indexed.
2) Does it possible to copy a shard into another shard, or merge them?
By the way
In Solr Cloud, a document is indexed on the shard leader. The replicas in that
shard get the document and add it to their indexes. There is some indexing that
happens on the replicas, but that is managed by Solr.
wunder
On Apr 6, 2013, at 3:58 PM, Furkan KAMACI wrote:
> Hi Walter;
>
> Thanks
Hi Walter;
Thanks for your explanation. You said "Indexing happens on one Solr
server". Is it true even for SolrCloud?
2013/4/7 Walter Underwood
> Indexing happens on one Solr server. After a commit, the documents are
> searchable. In Solr 4, there is a "soft commit", which makes the documents
Indexing happens on one Solr server. After a commit, the documents are
searchable. In Solr 4, there is a "soft commit", which makes the documents
searchable, but does not create on-disk indexes.
Solr replication copies the committed indexes to another Solr server.
Solr Cloud uses a transaction
Hi Walter;
I am new to Solr and digging into code to understand it. I think that when
indexer copies indexes, before the commit it is unsearchable.
Where exactly that commit occurs at code and can I say that: rollback
something because I don't want that indexes (reason maybe anything else,
maybe
This is precisely how Solr replication works. It copies the indexes then does a
commit.
wunder
On Apr 6, 2013, at 2:40 PM, Furkan KAMACI wrote:
> Hi Daire Mac Mathúna;
>
> If there is a way copying one Solr's indexes into another Solr instance,
> this may also solve the problem. Somebody gener
Hi Daire Mac Mathúna;
If there is a way copying one Solr's indexes into another Solr instance,
this may also solve the problem. Somebody generates indexes and some of
other instances could get a copy of them. At synchronizing process you may
eliminate some of indexes at reader instance. So you can
I don't understand why this would be more performant.. seems like it'd be
more memory and resource intensive as you'd have multiple class-loaders and
multiple cache spaces for no good reason. Just have a single core with
sufficiently large caches to handle your response needs.
If you want to load
Hi. Wat are the thoughts on having multiple SOLR instances i.e. multiple
SOLR war files, sharing the same index (i.e. sharing the same solr_home)
where only one SOLR instance is used for writing and the others for reading?
Is this possible?
Is it beneficial - is it more performant than having jus
10 matches
Mail list logo
