This is a thoughtful organization attempt and needed, I think. Thanks Gus!
I want to see if I could get a security specialist/engineer where I work to
help us with this. I'm tempted to say I'm joining this thing but I'm weary
of dedicating time per week.
~ David Smiley
Apache Lucene/Solr
Big per-file overhead on writing suggests it'd be beneficial to set
useCompoundFile to true (the default is false).
I think unlocking more write performance requires some sort of write level
cache to enable segment merges to use local segment files if they have been
written recently. It could be
Solr already supports today reading and indexing on cloud storage - ABFS,
GCS, and S3 - using the Hadoop HDFS module. I assume the same works with
HDFS backup/restore as well. I haven't checked if all the supporting
libraries are included in the shipped Solr distribution, but the HDFS
filesystem
As far as a Lucene/Solr directory on cloud storage. Performance on the
write has a lot of overhead per file, hundreds of millis. The read overhead
is about half as much. I believe the write is so expensive due to the
strong consistency of both gcs and s3. So I think the main bottleneck would
be
The Apache Solr PMC is pleased to announce the release of the Apache Solr
Operator v0.7.0.
The Apache Solr Operator is a safe and easy way of managing a Solr
ecosystem in Kubernetes.
This release contains numerous bug fixes, optimizations, and improvements,
some of which are highlighted below.
It's been >72h since the vote was initiated and the result is:
+1 5 (4 binding)
0 0
-1 0
This vote has PASSED
It's been >72h since the vote was initiated and the result is:
+1 5 (4 binding)
0 0
-1 0
This vote has PASSED
On Mon, Apr 24, 2023 at 2:27 PM Anshum Gupta wrote:
> +1 (binding)
>
> Smoke test is happy!
>
> On Thu, Apr 20, 2023 at 1:32 AM Houston Putman wrote:
>
> > Please vote for
Thank you Ishan and Mark for chiming in.
>From the feedback I received so far it looks like there is very little gain
to be had enabling compression.
I tried running some tests locally and this fits, I don't see any gains,
whatever you might save on transfer time, you waste on compression.
+1 (binding)
Smoke test is happy!
On Thu, Apr 20, 2023 at 1:32 AM Houston Putman wrote:
> Please vote for release candidate 1 for the Solr Operator v0.7.0
>
> The artifacts can be downloaded from:
>
>
*Rationale*
Over the course of the last decade the way software security is viewed has
changed. Solr has changed significantly over this time too and we have
gained some important security features and fixed a variety of
vulnerabilities. However, I think as a project we have not really developed
Yup, let's wait in that case. I didn't realize it would fail since I had
temporarily added my key locally to be able to execute the additional
steps. This results in the smoketester passing for me. I'll resend a vote
once I'm able to push my key.
On Mon, Apr 24, 2023 at 12:32 PM Houston Putman
Hey Justin,
Should we wait to run this until after your GPG key is in
https://downloads.apache.org/solr/KEYS?
The smoketester fails for me because it can't find your key.
- Houston
On Mon, Apr 24, 2023 at 12:20 PM Justin Sweeney
wrote:
> Please vote for release candidate 1 for Solr 9.2.1
>
>
Please vote for release candidate 1 for Solr 9.2.1
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/solr/solr-9.2.1-RC1-rev-a4c64ab6a2a270ca69c28c706dabb2927ed8a7c2
You can run the smoke tester directly with this command:
python3 -u
Here's my +1!
I was able to run the smoketester. Also ran some manual tests focused
mainly on solrbackup resources going to GCS and S3.
Best,
Jason
On Sun, Apr 23, 2023 at 1:28 AM Arrieta, Alejandro
wrote:
>
> Hello Team
>
> +1
> #Successfully smoke tested the Solr Operator v0.7.0!
>
> On a
14 matches
Mail list logo
