Moving to solrcloud from single instance

2019-08-12 Thread Erie Data Systems
I am starting the planning stages of moving from a single instance of solr 8 to a solrcloud implementation. Currently I have a 148GB index on a single dedicated server w 96gb ram @ 16 cores /2.4ghz ea. + SSD disk. The search is fast but obviously the index size is greater than the physical

Odd error with Solr 8 log / ingestion

2019-06-06 Thread Erie Data Systems
Hello everyone, I recently setup Solr 8 in SolrCloud mode, previously I was using standalone mode and was able to easily push 10,000 records in per HTTP call wit autocommit. Ingestion occurs when server A pushes (HTTPS) payload to server B (SolrCloud) on LAN network. However, once converted to

Issue with max documents on single instance

2019-05-31 Thread Erie Data Systems
Solr 8.0.0 (single server, single instance, single core) Centos 6x86_64 Error : number of documents in the index cannot exceed 2147483519 Ive read about the max number of documents which means I need to go with SolrCloud.. My question is this, can I implement a "clustered" environment on single

Interesting Grouping/Facet issue

2019-04-09 Thread Erie Data Systems
Solr 8.0.0, I have a HASHTAG string field I am trying to facet on to get the most popular hashtags (top 100) across many sources. (SITE field is string) /select?facet.field=hashtag=on=0=%2Bhashtag:*%20%2BDT:[" . date('Y-m-d') . "T00:00:00Z+TO+" . date('Y-m-d') . "T23:59:59Z]=100=1=fc It works

Re: CommonTerms & slow queries

2019-03-29 Thread Erie Data Systems
> > All great advice thanks Michael, have an excellent weekend! Testing the > common grams > -Craig

Re: CommonTerms & slow queries

2019-03-29 Thread Erie Data Systems
hese inputs > ("parsedquery" or "parsedquery_toString" output included for requests with > "debug=query" parameter)? What is performance like if you turn off pf > (i.e., no implicit phrase searching)? > Michael > > On Fri, Mar 29, 2019 at 11:53 AM Erie

CommonTerms & slow queries

2019-03-29 Thread Erie Data Systems
Using Solr 8.0.0, single instance, single core, 50m records (38gb index) on one SSD, 96gb ram, 16 cores CPU Most queries run very very fast <1 sec however we have noticed queries containing "common" words are quite slow sometimes 10+sec , currently using edismax with 2 text_general fields,. qf,