Yes, the docs mention one-to-one and many-to-one fetches, but one-to-many
is not supported currently. I've never really been happy with fetch. It
really needs to be replaced with a standard nested loop join that handles
all scenarios.
Joel Bernstein
http://joelsolr.blogspot.com/
On Tue, Oct
While the tool is only included in 8.5 and higher, it will index logs from any
version of Solr 7.x or 8.x (and possibly even 6.x). So if you want to use it,
you could download Solr 8.5 or higher to your local machine and index your
8.4.1 logs there, or use an 8.5 or higher Docker image. You
Kaya is certainly correct. I’d add that Solr has changed so much
in the last 12 years that you should treat it as a new Solr installation.
Do not, for instance, just use the configs from Solr 1.3, start
with the ones from the version of Solr you install.
Best,
Erick
> On Oct 14, 2020, at 3:41
Zisis makes good points. One other thing is I’d look to
see if the CPU spikes coincide with commits. But GC
is where I’d look first.
Continuing on with the theme of caches, yours are far too large
at first glance. The default is, indeed, size=512. Every time
you open a new searcher, you’ll be
SOLR-14914 (scheduled for 8.7) adds a boolean property (either by modifying
solr.xml:/metrics element or via “metricsEnabled” system property) to almost
completely turn off the metrics collection and processing. The “almost” part
means that the instrumentation still remains in place, but the
The values you have for the caches and the maxwarmingsearchers do not look
like the default. Cache sizes are 512 for the most part and
maxwarmingsearchers are 2 (if not limit them to 2)
Sudden CPU spikes probably indicate GC issues. The # of documents you have
is small, are they huge documents?
Thank you!
On Wed, 14 Oct 2020 09:41:16 +0200
Szűcs Roland wrote:
> Hi,
> I got it from the solr user list.
>
>
> Roland
>
> uyilmaz ezt írta (időpont: 2020. okt. 14.,
> Sze, 9:39):
>
> > Hello all,
> >
> > I have never got an answer to my questions in this mailing list yet, and
> > my
Hi community,
When I set solr time zone to Asia/Tokyo to specify solr log time.
However, the solr gc log is still using my machine's default timezone.
How to keep time zone in gc log consistent with solr log?
Thanks.
Thanks Alexandre, silly me. I though 8.4.1 was recent enough...
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi,
Yes, the API works by default on 8.2:
https://lucene.apache.org/solr/guide/8_2/metrics-reporting.html
I don’t know of a way to disable it, but he configuration is described in the
page above (i.e. on how to configure different reporters).
Best regards,
Radu
--
Sematext Cloud - Full Stack
Hello,
If you enable authentication, this will work on your HTTP port. Solr won’t make
a difference on whether the request comes from the Web UI or Dovecot.
I guess the workaround could be to put the web UI behind a proxy like NGINX and
have authentication there?
But if anyone can have direct
Hi,
I wouldn’t commit on every update. The general practice is to use autoCommit
and autoSoftCommit, so this work is done in background depending on how quickly
you want data persisted and available for search:
Hi,
I got it from the solr user list.
Roland
uyilmaz ezt írta (időpont: 2020. okt. 14.,
Sze, 9:39):
> Hello all,
>
> I have never got an answer to my questions in this mailing list yet, and
> my mail client shows INVALID next to my mail address, so I thought I should
> check if my emails are
Hi,
Replacing fils under the data directory won't work as you expected.
Solr has changed its index format,
so whenever you consider upgrading, you are strongly recommended to
re-index all of your documents for your safety.
FYI: not only index format, but also other things have been changed from
Hello all,
I have never got an answer to my questions in this mailing list yet, and my
mail client shows INVALID next to my mail address, so I thought I should check
if my emails are reaching to you.
Can anyone reply?
Regards
--
uyilmaz
15 matches
Mail list logo
