Hi!
After upgrading our Solr Cloud collections from 8.7.0 to 8.8.0 I struggle
to get a consistent state. We have 8 servers hosting 3 collections, with
shards/replicas spread over alle the servers.
All replicas on solr3577 is in "Recovering" state, and is repeating every
five minutes: "RemoteSolr
We are seeing performance degradation on our SolrCloud instances after
upgrading to 6.4.1.
Here are a couple of graphs. As you can see, 6.4.1 was introduced 2/10
1200:
https://www.dropbox.com/s/qrc0wodain50azz/solr1.png?dl=0
https://www.dropbox.com/s/sdk30imm8jlomz2/solr2.png?dl=0
These are
re you using? SolrJ doesn't rely on Jetty, and
> should be enough to query, index, etc.
>
> -Matt
>
>
> On 24/06/16 08:45, Henrik Brautaset Aronsen wrote:
>
>> I have a Spring Boot project, and I am trying to upgrade from Solr 5.4 to
>> Solr 6.1. Solr 6.1 has a dep
I have a Spring Boot project, and I am trying to upgrade from Solr 5.4 to
Solr 6.1. Solr 6.1 has a dependency to Jetty 9.3. Now Spring Boot
complains: it gives a NoClassDefFoundError:
org/eclipse/jetty/server/handler/ContextHandler$NoContext. ContextHandler
exists in Jetty 9.3, but not the inner cl
On Mon, Jun 13, 2016 at 4:59 PM, Erick Erickson
wrote:
> Yes, Solr will pick that up. You won't have any replicas
> though so you'll have to ADDREPLICA afterwards.
> You could use the EMPTY option on the creteNodeSet
> of the Collections API to create a dummy collection
> to see what a no-replica
On Mon, Jun 13, 2016 at 1:50 AM, Erick Erickson
wrote:
> So to be clear we're talking about the same thing, your
> Zookeeper has a collections>>my_collection>>state.json
> ZNode. In that state.json you have information
> for all the shards, and you're saying that you had
> only 16 when there used
On Fri, Jun 10, 2016 at 6:18 PM, Erick Erickson
wrote:
> Well, how brave do you want to be ;)?
Hi Erick, thanks for your reply!
> There's no great magic to the
> Zookeeper nodes here. If you do everything just right you could create
> one manually. By that I mean you could "hand edit" the zno
Hi.
We have a SolrCloud setup with 20 shards, each with only 1 replica, served
on 8 servers.
After a server went down we are left with 16 shards, which means that some
of the compositeId hash ranges aren't hosted by any cores. Somehow the
shards/cores didn't come back after the server came up ag