Are there any significant (or not so significant) changes? I have browsed the
release notes and searched JIRA, but the latest news seems to be in 7.3 (where
the old Leader-In-Recovery logic was replaced).
Context:
We are currently running Solr 7.4 in production. In the past year, we’ve seen
t
ower in the log.
>
> It really seems like the data isn't being sent from the leader. As I said it
> could easily be something stupid that I've done along the way but I can't see
> what it is.
>
> Thanks again,
> Peter.
>
> -Original Message-
> Fr
Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: 08 August 2017 18:23
To: solr-user
Subject: Re: SolrCloud - leader updates not updating followers
This _better_ be a problem with your configuration or all my assumptions are
false ;)
What are you autocommit settings
ng these symptoms.
>
> Thanks in anticipation,
> Peter Lancaster.
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SolrCloud-leader-updates-not-updating-followers-tp4349618.html
> Sent from the Solr - User mailing list archive at Nabble.com.
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-leader-updates-not-updating-followers-tp4349618.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi Pushkar Raste,
Thanks for your hits.
We will try the 3rd solution and keep you posted.
Gérald Reinhart
On 10/07/2016 02:23 AM, Pushkar Raste wrote:
A couple of questions/suggestions
- This normally happens after leader election, when new leader gets elected, it
will force all the nodes
nodefr_fr_blue] INFO
org.apache.solr.cloud.RecoveryStrategy:sendPrepRecoveryCmd:605 - Sending prep recovery command to
http://dc1-s6-prod-solr-52.prod.dc1.kelkoo.net:8080/searchsolrnodefr; WaitForState:
action=PREPRECOVERY&core=fr_blue&nodeName=dc1-s6-prod-solr-57.prod.dc1.kelkoo.net:8080_
A couple of questions/suggestions
- This normally happens after leader election, when new leader gets
elected, it will force all the nodes to sync with itself.
Check logs to see when this happens, if leader was changed. If that is true
then you will have to investigate why leader change takes place
There is no information here at all that would us to say anything
meaningful. You might review:
http://wiki.apache.org/solr/UsingMailingLists
What do the logs say? Are there any exceptions? What happens on your system
that's
unusual if anything? In short, what have you tried to do to diagnose the
Hello everyone,
Our Solr Cloud works very well for several months without any significant
changes: the traffic to serve is stable, no major release deployed...
But randomly, the Solr Cloud leader puts all the replicas in recovery at the
same time for no obvious reason.
Hence, we ca
if possible distribute the traffic only between Physical Box 1
> and Physical Box 2.
>
> Is it possible to manually assign leadership? Would appreciate your inputs
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Overriding-SolrCloud-Leader-Election-and-manually-assign-leadership-Is-it-possible-tp4265932.html
> Sent from the Solr - User mailing list archive at Nabble.com.
ne.472066.n3.nabble.com/Overriding-SolrCloud-Leader-Election-and-manually-assign-leadership-Is-it-possible-tp4265932.html
Sent from the Solr - User mailing list archive at Nabble.com.
Restarting the node cleared out the problem and everything recovered.
Thanks!
On 5/21/15 5:42 AM, Ramkumar R. Aiyengar wrote:
This shouldn't happen, but if it does, there's no good way currently for
Solr to automatically fix it. There are a couple of issues being worked on
to do that currently.
This shouldn't happen, but if it does, there's no good way currently for
Solr to automatically fix it. There are a couple of issues being worked on
to do that currently. But till then, your best bet is to restart the node
which you expect to be the leader (you can look at ZK to see who is at the
he
My SolrCloud cluster isn't reassigning the collections leaders from
downed cores--the downed cores are still listed as the leaders. The
cluster has been in the state for a few hours and the logs continue to
report "No registered leader was found after waiting for 4000ms." Is
there a way to forc
On 7/14/2013 6:42 AM, kowish.adamosh wrote:
> The problem is that I don't want to invoke data import on 8 server nodes but
> to choose only one for scheduling. Of course if this server will shut down
> then another one needs to take the scheduler role. I can see that there is
> task for sheduling h
.
Scheduling is currently outside of the scope of Solr and SolrCloud.
-- Jack Krupansky
-Original Message-
From: kowish.adamosh
Sent: Sunday, July 14, 2013 8:42 AM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud leader
The problem is that I don't want to invoke data import on 8 s
message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-leader-tp4077759p4077878.html
Sent from the Solr - User mailing list archive at Nabble.com.
ntage.
This is an interesting issue to ponder.
-- Jack Krupansky
-Original Message-
From: kowish.adamosh
Sent: Saturday, July 13, 2013 10:51 AM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud leader
Ya :-) I need it for different reason.
I have 8 server nodes and one of them h
lse optimization and that distracts attention from optimizing
the full application architecture.
-- Jack Krupansky
-Original Message-
From: Radim Kolar
Sent: Saturday, July 13, 2013 10:32 AM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud leader
Since SolrCloud is a master-free a
want to invoke scheduled updates in separate application
because of HA requirement. Any ideas?
Kowish
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-leader-tp4077759p4077806.html
Sent from the Solr - User mailing list archive at Nabble.com.
Since SolrCloud is a master-free architecture, you can send both queries
and updates to ANY node and SolrCloud will assure that the data gets to
where it belongs
its way faster to send them to right node
SolrCloud will assure that the data gets to where it
belongs and queries gets distributed to the nodes that have the data needed
to satisfy the queries.
-- Jack Krupansky
-Original Message-
From: kowish.adamosh
Sent: Saturday, July 13, 2013 5:11 AM
To: solr-user@lucene.apache.org
S
programmatically)?
Maybe there is better solution than invoking CloudSolrServer by one of the
server nodes (which is not so good idea)?
Kowish
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-leader-tp4077759.html
Sent from the Solr - User mailing list archive at Nabble.com.
Replica asks to Zookeper and Leader does not do anything. Thanks for your
answer Otis.
2013/4/17 Otis Gospodnetic
> Oui, ZK holds "the map".
>
> Otis
> --
> Solr & ElasticSearch Support
> http://sematext.com/
>
>
>
>
>
> On Tue, Apr 16, 2013 at 6:33 PM, Furkan KAMACI
> wrote:
> > Hi Otis;
> >
>
Oui, ZK holds "the map".
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Tue, Apr 16, 2013 at 6:33 PM, Furkan KAMACI wrote:
> Hi Otis;
>
> You said:
>
> "It can just do it because it knows where things are."
>
> Does it learn it from Zookeeper?
>
> 2013/4/17 Otis Gospodnetic
>
Hi Otis;
You said:
"It can just do it because it knows where things are."
Does it learn it from Zookeeper?
2013/4/17 Otis Gospodnetic
> If query comes to shard X on some node and this shard X is NOT a
> leader, but HAS data, it will just execute the query. If it needs to
> query shards on ot
If query comes to shard X on some node and this shard X is NOT a
leader, but HAS data, it will just execute the query. If it needs to
query shards on other nodes, it will have the info about which shards
to query and will just do that and aggregate the results. It doesn't
have to ask leader for p
Hi Mark;
When I speak with proper terms I want to ask that: is there a data locality
of spatial locality (
http://www.roguewave.com/portals/0/products/threadspotter/docs/2011.2/manual_html_linux/manual_html/ch_intro_locality.html
- I mean if you have data on your machine, use it and don't search i
Leaders don't have much to do with querying - the node that you query will
determine what other nodes it has to query to search the whole index and do a
scatter/gather for you. (Though in some cases that request can be proxied to
another node)
- Mark
On Apr 16, 2013, at 7:48 AM, Furkan KAMACI
When a leader responses for a query, does it says that: "If I have the data
what I am looking for, I should build response with it, otherwise I should
find it anywhere. Because it may be long to search it?"
or
does it says I only index the data, I will tell it to other guys to build
up the response
enormously valuable to us and we really appreciate
your helps!
Lisheng
-Original Message-
From: Otis Gospodnetic [mailto:otis.gospodne...@gmail.com]
Sent: Thursday, April 11, 2013 5:27 PM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud leader to replica
Hi,
I think Timothy is right
4 a little (I have not read solr4x fully yet) to
>> compromise
>> consistency (C) in order to increase availability (A), on a high level do
>> you see
>> serious problems in this approach (I am familiar with lucene/solr code to
>> some
>> extent)?
>>
>>
gt; you see
> serious problems in this approach (I am familiar with lucene/solr code to
> some
> extent)?
>
> Thanks and best regards, Lisheng
>
> -Original Message-
> From: Otis Gospodnetic [mailto:otis.gospodne...@gmail.com]
> Sent: Thursday, April 11, 2013 2:50 PM
>
On 4/11/2013 3:50 PM, Otis Gospodnetic wrote:
But note that I misspoke, which I realized after re-reading the thread
I pointed you to. Mark explains it nicely there:
* the index call returns only when (and IF!) indexing to all replicas succeeds
Does this actually mean "all active replicas" ...
@lucene.apache.org
Subject: Re: SolrCloud leader to replica
But note that I misspoke, which I realized after re-reading the thread
I pointed you to. Mark explains it nicely there:
* the index call returns only when (and IF!) indexing to all replicas succeeds
BUT, that should not be mixed with what search
ssage-
> From: Otis Gospodnetic [mailto:otis.gospodne...@gmail.com]
> Sent: Thursday, April 11, 2013 1:23 PM
> To: solr-user@lucene.apache.org
> Subject: Re: SolrCloud leader to replica
>
>
> Yes, I *think* that is the case. Some distributed systems have the
> option to re
Thanks very much for your helps!
-Original Message-
From: Otis Gospodnetic [mailto:otis.gospodne...@gmail.com]
Sent: Thursday, April 11, 2013 1:23 PM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud leader to replica
Yes, I *think* that is the case. Some distributed systems have
m: Otis Gospodnetic [mailto:otis.gospodne...@gmail.com]
> Sent: Thursday, April 11, 2013 8:11 AM
> To: solr-user@lucene.apache.org
> Subject: Re: SolrCloud leader to replica
>
>
> I believe it indexes locally on leader first. Otherwise one could end
> up with a situation wh
afer leader finishes his?
Thanks and best regards, Lisheng
-Original Message-
From: Otis Gospodnetic [mailto:otis.gospodne...@gmail.com]
Sent: Thursday, April 11, 2013 8:11 AM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud leader to replica
I believe it indexes locally on leader
I believe it indexes locally on leader first. Otherwise one could end
up with a situation where indexing to replica(s) succeeds and indexing
to leader fails, which I suspect might create a mess.
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Thu, Apr 11, 2013 at 2:53 AM, Zhang,
Hi,
In solr 4x solrCloud, suppose we have only one shard and
two replica, when leader receives the indexing request,
does it immediately forward request to two replicas or
it first indexes request itself, then sends request to its
two replica?
Thanks very much for helps, Lisheng
g
> SEVERE: Error while trying to recover.
> core=collection1:org.apache.solr.common.SolrException: No registered leader
> was found, collection:collection1 slice:shard1
> at
> org.apache.solr.common.cloud.ZkStateReader.getLeaderProps(ZkStateReader.java:413)
> at
> org.apache.solr.common.cloud.ZkStateReader.getLeaderProps(ZkStateReader.java:399)
> at
> org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:318)
> at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:220)
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SolrCloud-leader-election-on-single-node-tp4015804.html
> Sent from the Solr - User mailing list archive at Nabble.com.
at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:220)
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-leader-election-on-single-node-tp4015804.html
Sent from the Solr - User mailing list archive at Nabble.com.
44 matches
Mail list logo
