I’m going to go against the advice SLIGHTLY, it really depends on how you have
things set up as far as your solr server hosting is done. If you’re searching
off the same solr server you’re indexing to, yeah don’t ever optimize it will
take care of itself, people much smarter than us, like
Hi Erick,
Hi Walter,
Thanks for these information,
I will learn seriously about the solr article you gave me.
I thought it was important to always delete and optimize collection.
More information concerning my collection,
Index size is about 390Go for 130M docs (3-5ko / doc), around 25 fields
Hi Alex,
Hi Erick,
Thanks a lot for the prompt reply. Indeed, the functionality is completely
fine and checking the values with the analyzer gives results as expected. I
also checked the jira issue, nicely described.
Cheers,
Arturas
On Wed, Dec 2, 2020 at 7:23 PM Erick Erickson
wrote:
>
Images are stripped by the mail server, so we can’t see the result.
I looked at master and the admin UI has problems, I just
raised a JIRA, see:
https://issues.apache.org/jira/browse/SOLR-15024
The _functionality_ is fine. If you go to the analysis page
and enter values, you’ll see the
Did you reload the core for it to notice the new schema? Or try creating a
new core from the same schema?
If it is a SolrCloud, you also have to upload the schema to the Zookeeper.
Regards,
Alex.
On Wed, 2 Dec 2020 at 09:19, Arturas Mazeika wrote:
> Hi Solr-Team,
>
> The manual of
Hi Solr-Team,
The manual of charfilters says that one can chain them: (from
https://lucene.apache.org/solr/guide/6_6/charfilterfactories.html#CharFilterFactories-solr.MappingCharFilterFactory
):
CharFilters can be chained like Token Filters and placed in front of a
Tokenizer. CharFilters can
expungeDeletes is unnecessary, optimize is a superset of expungeDeletes.
The key difference is commit=true. I suspect if you’d waited until your
indexing process added another doc and committed, you’d have seen
the index size drop.
Just to check, you send the command to my_core but talk about
You can certainly use the TTL logic. Note the TimeRoutedAlias, but
the DocExpirationUpdateFactory. DocExpirationUpdateFactory
operates on each document individually so you can mix-n-match
if you want.
As for knowing when a shard is empty, I suggested a method for that
in one of the earlier
Hi everyone,
As per suggestions in previous post (by Erick and Shawn) we did following
changes.
OLD
NEW
*Reduced JVM heap size from 30GB to 26GB*
GC setting:
GC_TUNE=" \
-XX:+UseG1GC \
-XX:+PerfDisableSharedMem \
-XX:+ParallelRefProcEnabled \
-XX:G1HeapRegionSize=8m \
