lly, expungeDeletes is less expensive than optimize because it doesn’t
rewrite segments with 10% deleted docs so that’s an alternative to optimizing
after upgrading.
Best,
Erick
> On Feb 24, 2020, at 5:42 PM, Zimmermann, Thomas
wrote:
>
> Hi Folks –
>
Hi Folks –
Few questions before I tackled an upgrade here. Looking to go from 7.4 to 7.7.2
to take advantage of the improved Tiered Merge Policy and segment cleanup – we
are dealing with some high (45%) deleted doc counts in a few cores. Would
simply upgrading Solr and setting the cores to use
this, we could of course give it
a quick go.
-TZ
On 11/6/18, 12:35 PM, "Shawn Heisey" wrote:
>On 11/6/2018 10:12 AM, Zimmermann, Thomas wrote:
>> Shawn -
>>
>> Server performance is fine and request time are great. We are tolerating
>> the level of traff
I should mention I¹m also hanging out in the Solr IRC Channel today under
the nick ³apatheticnow² if anyone wants to follow up in real time during
business hours EST.
On 11/6/18, 11:39 AM, "Shawn Heisey" wrote:
>On 11/6/2018 9:06 AM, Zimmermann, Thomas wrote:
>> For exampl
On 11/6/18, 11:39 AM, "Shawn Heisey" wrote:
>On 11/6/2018 9:06 AM, Zimmermann, Thomas wrote:
>> For example - 75k request per minute going to this one box, and 3.5k
>>RPM to all other nodes in the cloud.
>>
>> All of those extra requests on the one box are
Question about CloudSolrClient and CLUSTERSTATUS. We just deployed a 3 server
ZK cluster and a 5 node solr cluster using the CloudSolrClient in Solr 7.4.
We're seeing a TON of traffic going to one server with just cluster status
commands. Every single query seems to be hitting this box for
We have a Solr v7 Instance sourcing data from a Data Import Handler with a Solr
data source running Solr v4. When it hits a single server in that instance
directly, all documents are read and written correctly to the v7. When we hit
the load balancer DNS entry, the resulting data import handler
In case anyone else runs into this, I tracked it down. I had to force maven to
explicitly include all of it’s dependent jars in the plugin jar using the
assembly plugin in the pom like so:
maven-assembly-plugin
2.5.3
jar-with-dependencies
Hi,
We have a custom java plugin that leverages the UpdateRequestProcessorFactory
to push data to multiple cores when a single core is written to. We are
building the plugin with maven, deploying it to /solr/lib and sourcing the jar
via a lib directive in our solr config. It currently works
1:50 PM Shawn Heisey, wrote:
>
>> On 8/17/2018 6:15 PM, Zimmermann, Thomas wrote:
>> > I¹m trying to track down an odd issue I¹m seeing when using the
>> SolrEntityProcessor to seed some test data from a solr 4.x cluster to a
>> solr 7.x cluster. It seems like strings
Hi,
I’m trying to track down an odd issue I’m seeing when using the
SolrEntityProcessor to seed some test data from a solr 4.x cluster to a solr
7.x cluster. It seems like strings are being interpreted as multivalued when
passed from a string field to a text field via the copyTo directive. Any
ers you think
>is redundant?
>
>On top of that: in your chain the HTMLStripCharFilterFactory applied at
>query time is something unusual, because while it makes perfectly sense
>at index time (where I guess you index some HTML source), at query time
>I can't imagine a scenario
Hi,
We have the text field below configured on fields that are both stored and
indexed. It seems to me that applying the same filters on both index and query
would be redundant, and perhaps a waste of processing on the retrieval side if
the filter work was already done on the index side. Is
Hi,
We're in the midst of our first major Solr upgrade in years and are trying to
run some cleanup across all of our client codebases. We're currently using the
standard PHP Solr Extension when communicating with our cluster from our
Wordpress installs. http://php.net/manual/en/book.solr.php
Thanks all! I think we will maintain our current approach of hand editing
the configs in git and implement something at the shell level to automate
the process of running upconfig and performing a core reload.
Hi,
We have several cores with identical configurations with the sole exception
being the language of their document sets. I'd like to leverage Config Sets to
manage the going forward, but ran into two issues I'm struggling to solve
conceptually.
Sample Cores:
our_documents
our_documents_de
Hi,
We're transitioning from Solr 4.10 to 7.x and working through our options
around managing our schemas. Currently we manage our schema files in a git
repository, make changes to the xml files, and then push them out to our
zookeeper cluster via the zkcli and the upconfig command like:
Thanks Shawn - I misspoke when I said recommendation, should have said
³packaged with². I appreciate the feedback and the quick updates to the
Jira issue. We¹ll plan to proceed with 3.4.12 when we go live.
-TZ
On 6/29/18, 11:38 AM, "Shawn Heisey" wrote:
>On 6/28/2018 8:39 P
Hi,
I was wondering if there was a reason Solr 7.4 is still recommending ZK 3.4.11
as the major version in the official changelog vs shipping with 3.4.12 despite
the known regression in 3.4.11. Are there any known issues with running 7.4
alongside ZK 3.4.12. We are beginning a major Solr
19 matches
Mail list logo
