Thank you both for the clarification and proposals!
This solrcloud_manager looks very promising. I'll try it out, the shared
filesystem requirement is no issue for me.
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-backup-restore-tp4267954p4268197.html
Sent
I've tested backup/restore successfully in a SolrCloud installation with a
single node (no replicas). This has been achieved in
https://issues.apache.org/jira/browse/SOLR-6637
Can you do something similar when more replicas are involved? What I'm
looking for is a restore command that will restore
Hi Tom,
Thanks for clarifying the purpose of XJoin, makes sense now. Hope it makes
it into Solr's main branch, this could prove useful! For the time being
PostFilter covers my needs.
--
View this message in context:
Hi Charlie,
This looks like an interesting feature, but I have a couple of questions
before giving it a try.
I had similar needs - filtering results based on information outside of the
queried Solr collection - and I went down the post-filtering path.
More specifically I've implemented a
I'm conducting some indexing experiments in SolrCloud and I want to confirm
my conclusions and ask for suggestions on how to improve performance.
My setup includes a single-sharded collection with 1 additional replica in
SolrCloud 5.3.1. I'm using SolrJ and the indexing speed refers to the actual
Erick Erickson wrote
OK, I think this is the root of your problem:
bq: Everything was setup using the - now deprecated - tags
cores
and
core
inside solr.xml.
There are a bunch of ways this could go wrong. I'm pretty sure you
have something that would take quite a while to
Well, I don't know If I'm being helpful but here goes.
My clusterstate.json actually has no leader for the shard in question. I
have 2 nodes as recovery_failed and one as down. No leaders there. I've
not used core admin or collections api to create anything. Everything was
setup using the - now
From the logs I've got one instance failing as described in my first comment
and the other two failing during PeerSync recovery when trying to
communicate with the server that was missing the segments_* files. The
exception follows
org.apache.solr.client.solrj.SolrServerException: IOException
I'm using SolrCloud 4.10.3 and the current setup is simple using 3 nodes with
1 shard. After a rolling restart of the Solr cluster I've ended up with 2
failing nodes reporting the following
org.apache.solr.servlet.SolrDispatchFilter
null:org.apache.solr.common.SolrException: SolrCore 'core' is
It seems that a solution has been found.
PostingsHighlighter uses by default Java's SENTENCE BreakIterator so it
breaks the snippets into fragments per sentence.
In my text_en analysis chain though I was using a filter that lowercases
input and this seems to mess with the logic of SENTENCE
Hi all,
I'm using SolrCloud 4.10.0 and trying to incorporate
PostingsSolrHighlighter. One issue that I'm having is that I cannot have the
functionality of hl.fragsize in PostingsSolrHighlighter. How can I limit
the size of the highlighted text? I get highlighted results but their
snippet size
Daniel Collins wrote
Is it important where your leader is? If you just want to minimize
leadership changes during rolling re-start, then you could restart in the
opposite order (S3, S2, S1). That would give only 1 transition, but the
end result would be a leader on S2 instead of S1 (not sure
SolrCloud uses ZooKeeper sequence flags to keep track of the order in which
nodes register themselves as leader candidates. The node with the lowest
sequence number wins as leader of the shard.
What I'm trying to do is to keep the leader re-assignments to the minimum
during a rolling restart. In
In case anyone else runs into this, I've managed to make it work. I didn't
notice in the ticket discussion that the specific feature is enabled when
min_rf =2, I was setting min_rf=1. It goes without saying that you should
also have at least 2 replicas in your SolrCloud configuration. The actual
Hi all,
I'm trying to make use of the min_rf (minimum replication factor) feature
described in https://issues.apache.org/jira/browse/SOLR-5468. According to
the ticket, all that is needed is to pass min_rf param into the update
request and get back the rf param from the response or even easier
Hi all,
I'm using Solr 4.9.0 and have setup a spellcheck component for returning
suggestions. The configuration inside my solr.SpellCheckComponent has as
follows.
str name=classnameorg.apache.solr.spelling.suggest.Suggester/str
str
16 matches
Mail list logo