Thanks Jan for the flexibility, esp with respect to the vector search
thing. If it happens to be ready within your proposed timelines, it will be
a good thing for our project. I don't advocate delaying the release, though.
> Honestly, if you are out of the chair when the music stops, you look more
On Mon, Jan 10, 2022 at 12:57 AM Jan Høydahl wrote:
>
> Hi,
>
> This is quite simple.
> - The 9.0 release is on-going - now on branch_9_0
> - The normal feature feeze rules apply. Anything explicitly approved as
> blocker gets in
>
> We can still consider adding features to the branch if the benf
JMX is really a toy metric system and comes with potential security concerns
that have to be considered and managed over time.
The cost in the case you are seeing has also been potentially much worse in the
past - a variety of expensive metrics are now cached I believe - but as it
iterated over
I noticed Solr auto-creates a metrics SolrJmxReporter if there is a
platform "MBeanServer" that exists, which AFAICT is always. Thanks? Ehh,
no thanks. It's not evident how to disable JMX after some fruitless google
searches. Don't get me wrong, I like jconsole, jvisualvm, JFR etc and I
think s
Can’t restrain myself.
The discussion whether we have "enough features" is i.m.o. silly
Lucene used to release major versions with something like no features and
just deprecation work.
It’s historically common, but the silly smell reminds me of the
stereotypical kid selling his parents on some
One thing we haven’t talked about yet is the Ref Guide for 9.0.
SOLR-1 re-organized the entire guide and changed a lot of page names. At
the time I merged this into the main branch there was a little bit of comment
about trying to provide page redirects for the changed page names but AFAIK n
Hi,
This is quite simple.
- The 9.0 release is on-going - now on branch_9_0
- The normal feature feeze rules apply. Anything explicitly approved as blocker
gets in
We can still consider adding features to the branch if the benfit/risk ratio is
high enough. Having a long stabilization period al
That is generally an expected trade off when using the new collectors - perhaps
a 15% hit to throughput due to locking in concurrent compaction but better
latency with the shorter pauses.
The last I saw, for smaller heaps, G1 generally wins - better throughput and
latency that’s just as good.
