Re: SolrCloud - Underlying core creation failed while creating collection with new configset

2020-03-04 Thread Vignan Malyala
Hi Erick, Did see any extra error in solr logs. Its the same error I mentioned earlier. I'm using SolrCloud by the way. On Wed, Mar 4, 2020 at 8:06 PM Erick Erickson wrote: > You need to look at the solr logs on the machine where the attempt was > made to create the replica... > > Best, > Erick

exactMatchFirst Solr Suggestion Component

2020-03-04 Thread Audrey Lorberfeld - audrey.lorberf...@ibm.com
Hi All, Would anyone be able to help me debug my suggestion component? Right now, our config looks like this: mySuggester FuzzyLookupFactory FileDictionaryFactory ./conf/queries_list_with_weights.txt , conf keywords_w3_en false We like the idea of the

Re: Custom update processor and race condition with concurrent requests

2020-03-04 Thread Sachin Divekar
Thanks, Chris. I think I should stop thinking about doing it in Solr. Anyway, I was just trying to see how far I can go. On Wed, Mar 4, 2020 at 11:50 PM Chris Hostetter wrote: > > : So, I thought it can be simplified by moving this state transitions and > : processing logic into Solr by

Re: Custom update processor and race condition with concurrent requests

2020-03-04 Thread Chris Hostetter
: So, I thought it can be simplified by moving this state transitions and : processing logic into Solr by writing a custom update processor. The idea : occurred to me when I was thinking about Solr serializing multiple : concurrent requests for a document on the leader replica. So, my thought :

Re: Solr Search cause high CPU with **

2020-03-04 Thread Shreyas Kothiya
Thanks you for quick response. we do use wild card searches. I am sorry if i have not asked my question correctly. in SOLR if you search with consecutive asterisks [**] does not like it and cause high CPU. and does not return any result. q= N*W* 154 ** underpass was converted to

Re: Custom update processor and race condition with concurrent requests

2020-03-04 Thread Walter Underwood
This really, really looks like something that should be done with a database, not with Solr. This assumes a transactional model, which Solr doesn’t have. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Mar 3, 2020, at 7:56 PM, Sachin Divekar wrote:

Re: SolrCloud - Underlying core creation failed while creating collection with new configset

2020-03-04 Thread Erick Erickson
You need to look at the solr logs on the machine where the attempt was made to create the replica... Best, Erick > On Mar 4, 2020, at 03:24, Vignan Malyala wrote: > > Hi > I created a new config set as mentioned in Solr Cloud documentation using > upload zip. > I get this error when I try to

Re: Custom update processor and race condition with concurrent requests

2020-03-04 Thread Sachin Divekar
So, the idea was that Solr serializes writes while appending records to tlogs. Combining that with realtime gets to make decisions to modify the request would achieve the result. > I do wonder if it’s possible to insure that a given doc is always updated from the same thread? I’m assuming that

SolrCloud - Underlying core creation failed while creating collection with new configset

2020-03-04 Thread Vignan Malyala
Hi I created a new config set as mentioned in Solr Cloud documentation using upload zip. I get this error when I try to create a collection using my new configset. Error from shard: http://X.X.X.X:8983/solr OverseerCollectionMessageHandler Cleaning up collection [test5]. Collection: test5

Fwd: Issue With Autoscaling

2020-03-04 Thread Sandeep Dharembra
Hi, *Here are the details of what we are trying to do -* 1) Setup a solr cloud cluster using solr version 8.4.1 2) Replica type - Tlog + Pull setup 3) All Tlog replicas to be placed on one node 4) All pull replicas need to be placed on the remaining nodes 5) External Zookeeper to be used 6) On a

Disastor Scenario Question Regarding Tlog+pull solrcloud setup

2020-03-04 Thread Sandeep Dharembra
Hi, My question is about the solrcloud cluster we are trying to have. We have a collection with Tlog and pull type replicas. We intend to keep all the tlogs on one node and use that for writing and pull replicas distributed on the remaining nodes. What we have noticed is that when the Tlog node