Hi Santosh Kumar,
You need to subscribe yourself to Solr mailing list. For more details refer
"Mailing List and IRC" section here:
http://lucene.apache.org/solr/community.html
Hope this helps you.
Regards
--
Pritam Kute
On Tue, Aug 1, 2017 at 5:38 PM, Santosh Kumar
wrote:
> Hi,
> Please add m
Hi devs,
I was exploring the /export handler in solr and got an exception. When I
research online I found this open jira case : SOLR-8860
https://issues.apache.org/jira/plugins/servlet/mobile#issue/SOLR-8806
is this a valid jira case? Any workarounds?
Jira says affect version is 5.5 but I'm get
To add to this, not sure of solr cloud uses it, but you're going to want to
destroy the wrote.lock file as well
> On Aug 1, 2017, at 9:31 PM, Shawn Heisey wrote:
>
>> On 8/1/2017 7:09 PM, Erick Erickson wrote:
>> WARNING: what I currently understand about the limitations of AWS
>> could fill vo
On 8/1/2017 7:09 PM, Erick Erickson wrote:
> WARNING: what I currently understand about the limitations of AWS
> could fill volumes so I might be completely out to lunch.
>
> If you ADDREPLICA with the new replica's data residing on the new EBS
> volume, then wait for it to sync (which it'll do al
And please do not use optimize unless your index is
totally static. I only recommend it when the pattern is
to update the index periodically, like every day or
something and not update any docs in between times.
Implied in Shawn's e-mail was that you should undo
anything you've done in terms of co
WARNING: what I currently understand about the limitations of AWS
could fill volumes so I might be completely out to lunch.
If you ADDREPLICA with the new replica's data residing on the new EBS
volume, then wait for it to sync (which it'll do all by itself) then
DELETEREPLICA on the original you'
re: automated tests. In the Solr JUnit tests you'll see this pattern
- create collection
- add a bunch of docs
- do a commit
- now test consistency
Which, of course, doesn't particularly help if you're indexing after the commit.
For things like soft commit tests special care is taken to allow th
On 8/1/2017 4:00 PM, Mahmoud Almokadem wrote:
> I'm using ubuntu and I'll try rsync command. Unfortunately I'm using one
> replication factor but I think the downtime will be less than five minutes
> after following your steps.
>
> But how can I start Solr backup or why should I run it although I
Thanks for the reply Erick, I feared that would be the case. Interesting
idea with using the fq but not sure I like the performance implications. I
will see how big of a deal it will be in practice, I was just thinking
about this as a hypothetical scenario today, and as you said, we have a lot
of a
Thanks Shawn,
I'm using ubuntu and I'll try rsync command. Unfortunately I'm using one
replication factor but I think the downtime will be less than five minutes
after following your steps.
But how can I start Solr backup or why should I run it although I copied
the index and changed theo path?
Way back in the 1.x days, replication was done with shell scripts and rsync,
right?
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Aug 1, 2017, at 2:45 PM, Shawn Heisey wrote:
>
> On 7/31/2017 12:28 PM, Mahmoud Almokadem wrote:
>> I've a SolrClou
On 7/31/2017 12:28 PM, Mahmoud Almokadem wrote:
> I've a SolrCloud of four instances on Amazon and the EBS volumes that
> contain the data on everynode is going to be full, unfortunately Amazon
> doesn't support expanding the EBS. So, I'll attach larger EBS volumes to
> move the index to.
>
> I can
You're understanding is correct.
As for how people cope? Mostly they ignore it. The actual number of
times people notice this is usually quite small, mostly it surfaces
when automated test suites are run.
If you must lock this up, and you can stand the latency you could add
a timestamp for each d
On 8/1/2017 12:09 PM, Michael B. Klein wrote:
> I have a 3-node solrcloud cluster orchestrated by zookeeper. Most stuff
> seems to be working OK, except that one of the nodes never seems to get its
> replica updated.
>
> Queries take place through a non-caching, round-robin load balancer. The
> col
Hi,
I think I know the answer to this question, but just wanted to verify/see
what other people do to address this concern.
I have a Solr Cloud setup (6.6.0) with 2 nodes, 1 collection with 1 shard
and 2 replicas (1 replica per node). The nature of my use case requires
frequent updates to Solr, a
I have a 3-node solrcloud cluster orchestrated by zookeeper. Most stuff
seems to be working OK, except that one of the nodes never seems to get its
replica updated.
Queries take place through a non-caching, round-robin load balancer. The
collection looks fine, with one shard and a replicationFacto
Hi,
Please add me in solr mailing list.
Thanks,
Santosh
17 matches
Mail list logo
