Re: [VOTE] Release Solr 9.4.1 RC1

[Arrieta, Alejandro]

+1 (not binding)

SUCCESS! [0:43:05.715183]

built solr and solr-slim successfully.

note: back online after a crazy end of year 2023.

On Tue, Jan 16, 2024 at 7:03 PM Houston Putman  wrote:

> +1 (binding)
>
> SUCCESS! [0:51:47.471576]
>
> I also successfully built both Docker images and ran the Solr Operator
> integration tests with the full image:
>
> Will run 23 of 23 specs
> Running in parallel across 3 processes
> •••
>
> Ran 23 of 23 Specs in 433.438 seconds
> SUCCESS! -- 23 Passed | 0 Failed | 0 Pending | 0 Skipped
>
> - Houston
>
> On Tue, Jan 16, 2024 at 8:28 AM Kevin Risden  wrote:
>
> > +1 (binding)
> >
> > SUCCESS! [0:33:05.648738]
> >
> > Kevin Risden
> >
> >
> > On Sat, Jan 13, 2024 at 3:34 PM Jan Høydahl 
> wrote:
> >
> > > +1 (binding)
> > >
> > > SUCCESS! [0:42:51.792486]
> > >
> > > Also built docker container and spun up the server locally.
> > >
> > >
> > > PS: Need to remove extra newline between the two lines of command when
> > > copy/pasting:
> > >
> > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > >
> > > Jan
> > >
> > > > 13. jan. 2024 kl. 17:14 skrev David Smiley :
> > > >
> > > > Please vote for release candidate 1 for Solr 9.4.1
> > > >
> > > > The artifacts can be downloaded from:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > >
> > > >
> > > > You can run the smoke tester directly with this command:
> > > >
> > > >
> > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > >
> > > >
> > > > You can build a release-candidate of the official docker images
> (full &
> > > > slim) using the following command:
> > > >
> > > >
> > > > SOLR_DOWNLOAD_SERVER=
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476/solr
> > > > && \
> > > >
> > > >  docker build
> > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-full \
> > > >
> > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >
> > > >-t solr-rc:9.4.1-1 && \
> > > >
> > > >  docker build
> > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-slim \
> > > >
> > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >
> > > >-t solr-rc:9.4.1-1-slim
> > > >
> > > >
> > > > The vote will be open for at least 72 hours i.e. until 2024-01-16
> 17:00
> > > UTC.
> > > >
> > > >
> > > > [ ] +1  approve
> > > >
> > > > [ ] +0  no opinion
> > > >
> > > > [ ] -1  disapprove (and reason why)
> > > >
> > > >
> > > > Here is my +1
> > > >
> > > > ~ David Smiley
> > > > Apache Lucene/Solr Search Developer
> > > > http://www.linkedin.com/in/davidwsmiley
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > > For additional commands, e-mail: dev-h...@solr.apache.org
> > >
> > >
> >
>

Re: [VOTE] Release Solr 9.4.1 RC1

[Jason Gerlowski]

+1 (binding)

Ran the smoketester (lost my timestamp in terminal scrollback), and did
some manual testing on the docker images (mostly focused on backup/restore
through the operator).

Jason

On Wed, Jan 17, 2024 at 4:02 AM Arrieta, Alejandro <
aarri...@perrinsoftware.com> wrote:

> +1 (not binding)
>
> SUCCESS! [0:43:05.715183]
>
> built solr and solr-slim successfully.
>
> note: back online after a crazy end of year 2023.
>
> On Tue, Jan 16, 2024 at 7:03 PM Houston Putman  wrote:
>
> > +1 (binding)
> >
> > SUCCESS! [0:51:47.471576]
> >
> > I also successfully built both Docker images and ran the Solr Operator
> > integration tests with the full image:
> >
> > Will run 23 of 23 specs
> > Running in parallel across 3 processes
> > •••
> >
> > Ran 23 of 23 Specs in 433.438 seconds
> > SUCCESS! -- 23 Passed | 0 Failed | 0 Pending | 0 Skipped
> >
> > - Houston
> >
> > On Tue, Jan 16, 2024 at 8:28 AM Kevin Risden  wrote:
> >
> > > +1 (binding)
> > >
> > > SUCCESS! [0:33:05.648738]
> > >
> > > Kevin Risden
> > >
> > >
> > > On Sat, Jan 13, 2024 at 3:34 PM Jan Høydahl 
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > SUCCESS! [0:42:51.792486]
> > > >
> > > > Also built docker container and spun up the server locally.
> > > >
> > > >
> > > > PS: Need to remove extra newline between the two lines of command
> when
> > > > copy/pasting:
> > > >
> > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > >
> > > > Jan
> > > >
> > > > > 13. jan. 2024 kl. 17:14 skrev David Smiley :
> > > > >
> > > > > Please vote for release candidate 1 for Solr 9.4.1
> > > > >
> > > > > The artifacts can be downloaded from:
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > > >
> > > > >
> > > > > You can run the smoke tester directly with this command:
> > > > >
> > > > >
> > > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > > >
> > > > >
> > > > > You can build a release-candidate of the official docker images
> > (full &
> > > > > slim) using the following command:
> > > > >
> > > > >
> > > > > SOLR_DOWNLOAD_SERVER=
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476/solr
> > > > > && \
> > > > >
> > > > >  docker build
> > > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-full \
> > > > >
> > > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > > >
> > > > >-t solr-rc:9.4.1-1 && \
> > > > >
> > > > >  docker build
> > > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-slim \
> > > > >
> > > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > > >
> > > > >-t solr-rc:9.4.1-1-slim
> > > > >
> > > > >
> > > > > The vote will be open for at least 72 hours i.e. until 2024-01-16
> > 17:00
> > > > UTC.
> > > > >
> > > > >
> > > > > [ ] +1  approve
> > > > >
> > > > > [ ] +0  no opinion
> > > > >
> > > > > [ ] -1  disapprove (and reason why)
> > > > >
> > > > >
> > > > > Here is my +1
> > > > >
> > > > > ~ David Smiley
> > > > > Apache Lucene/Solr Search Developer
> > > > > http://www.linkedin.com/in/davidwsmiley
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > > > For additional commands, e-mail: dev-h...@solr.apache.org
> > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Solr 9.4.1 RC1

[David Smiley]

I'll close the vote tomorrow morning for me (like in about 24 hours).

On Wed, Jan 17, 2024 at 9:24 AM Jason Gerlowski 
wrote:

> +1 (binding)
>
> Ran the smoketester (lost my timestamp in terminal scrollback), and did
> some manual testing on the docker images (mostly focused on backup/restore
> through the operator).
>
> Jason
>
> On Wed, Jan 17, 2024 at 4:02 AM Arrieta, Alejandro <
> aarri...@perrinsoftware.com> wrote:
>
> > +1 (not binding)
> >
> > SUCCESS! [0:43:05.715183]
> >
> > built solr and solr-slim successfully.
> >
> > note: back online after a crazy end of year 2023.
> >
> > On Tue, Jan 16, 2024 at 7:03 PM Houston Putman 
> wrote:
> >
> > > +1 (binding)
> > >
> > > SUCCESS! [0:51:47.471576]
> > >
> > > I also successfully built both Docker images and ran the Solr Operator
> > > integration tests with the full image:
> > >
> > > Will run 23 of 23 specs
> > > Running in parallel across 3 processes
> > > •••
> > >
> > > Ran 23 of 23 Specs in 433.438 seconds
> > > SUCCESS! -- 23 Passed | 0 Failed | 0 Pending | 0 Skipped
> > >
> > > - Houston
> > >
> > > On Tue, Jan 16, 2024 at 8:28 AM Kevin Risden 
> wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > SUCCESS! [0:33:05.648738]
> > > >
> > > > Kevin Risden
> > > >
> > > >
> > > > On Sat, Jan 13, 2024 at 3:34 PM Jan Høydahl 
> > > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > SUCCESS! [0:42:51.792486]
> > > > >
> > > > > Also built docker container and spun up the server locally.
> > > > >
> > > > >
> > > > > PS: Need to remove extra newline between the two lines of command
> > when
> > > > > copy/pasting:
> > > > >
> > > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > > >
> > > > > Jan
> > > > >
> > > > > > 13. jan. 2024 kl. 17:14 skrev David Smiley :
> > > > > >
> > > > > > Please vote for release candidate 1 for Solr 9.4.1
> > > > > >
> > > > > > The artifacts can be downloaded from:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > > > >
> > > > > >
> > > > > > You can run the smoke tester directly with this command:
> > > > > >
> > > > > >
> > > > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > > > >
> > > > > >
> > > > > > You can build a release-candidate of the official docker images
> > > (full &
> > > > > > slim) using the following command:
> > > > > >
> > > > > >
> > > > > > SOLR_DOWNLOAD_SERVER=
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476/solr
> > > > > > && \
> > > > > >
> > > > > >  docker build
> > > > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-full \
> > > > > >
> > > > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > > > >
> > > > > >-t solr-rc:9.4.1-1 && \
> > > > > >
> > > > > >  docker build
> > > > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-slim \
> > > > > >
> > > > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > > > >
> > > > > >-t solr-rc:9.4.1-1-slim
> > > > > >
> > > > > >
> > > > > > The vote will be open for at least 72 hours i.e. until 2024-01-16
> > > 17:00
> > > > > UTC.
> > > > > >
> > > > > >
> > > > > > [ ] +1  approve
> > > > > >
> > > > > > [ ] +0  no opinion
> > > > > >
> > > > > > [ ] -1  disapprove (and reason why)
> > > > > >
> > > > > >
> > > > > > Here is my +1
> > > > > >
> > > > > > ~ David Smiley
> > > > > > Apache Lucene/Solr Search Developer
> > > > > > http://www.linkedin.com/in/davidwsmiley
> > > > >
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > > > > For additional commands, e-mail: dev-h...@solr.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>

failing: not ok 3 auth enable/disable lifecycle in 10000ms

[David Smiley]

The integration tests (bats) are failing on branch_9x for me locally and as
also seen in Jenkins.
> not ok 3 auth enable/disable lifecycle in 1ms
https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/167/console

Hopefully someone has a clue why?

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley

Re: failing: not ok 3 auth enable/disable lifecycle in 10000ms

[Eric Pugh]

I will take a look….

> On Jan 17, 2024, at 10:38 AM, David Smiley  wrote:
> 
> The integration tests (bats) are failing on branch_9x for me locally and as
> also seen in Jenkins.
>> not ok 3 auth enable/disable lifecycle in 1ms
> https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/167/console
> 
> Hopefully someone has a clue why?
> 
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley

___
Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com  | 
My Free/Busy   
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 


This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.

Re: [VOTE] Release Solr 9.4.1 RC1

[Alessandro Benedetti]

+1 (binding)

SUCCESS! [0:45:30.104906]


Thanks for coordinating!

--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*

e-mail: a.benede...@sease.io


*Sease* - Information Retrieval Applied
Consulting | Training | Open Source

Website: Sease.io 
LinkedIn  | Twitter
 | Youtube
 | Github



On Wed, 17 Jan 2024 at 15:23, David Smiley  wrote:

> I'll close the vote tomorrow morning for me (like in about 24 hours).
>
> On Wed, Jan 17, 2024 at 9:24 AM Jason Gerlowski 
> wrote:
>
> > +1 (binding)
> >
> > Ran the smoketester (lost my timestamp in terminal scrollback), and did
> > some manual testing on the docker images (mostly focused on
> backup/restore
> > through the operator).
> >
> > Jason
> >
> > On Wed, Jan 17, 2024 at 4:02 AM Arrieta, Alejandro <
> > aarri...@perrinsoftware.com> wrote:
> >
> > > +1 (not binding)
> > >
> > > SUCCESS! [0:43:05.715183]
> > >
> > > built solr and solr-slim successfully.
> > >
> > > note: back online after a crazy end of year 2023.
> > >
> > > On Tue, Jan 16, 2024 at 7:03 PM Houston Putman 
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > SUCCESS! [0:51:47.471576]
> > > >
> > > > I also successfully built both Docker images and ran the Solr
> Operator
> > > > integration tests with the full image:
> > > >
> > > > Will run 23 of 23 specs
> > > > Running in parallel across 3 processes
> > > > •••
> > > >
> > > > Ran 23 of 23 Specs in 433.438 seconds
> > > > SUCCESS! -- 23 Passed | 0 Failed | 0 Pending | 0 Skipped
> > > >
> > > > - Houston
> > > >
> > > > On Tue, Jan 16, 2024 at 8:28 AM Kevin Risden 
> > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > SUCCESS! [0:33:05.648738]
> > > > >
> > > > > Kevin Risden
> > > > >
> > > > >
> > > > > On Sat, Jan 13, 2024 at 3:34 PM Jan Høydahl  >
> > > > wrote:
> > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > SUCCESS! [0:42:51.792486]
> > > > > >
> > > > > > Also built docker container and spun up the server locally.
> > > > > >
> > > > > >
> > > > > > PS: Need to remove extra newline between the two lines of command
> > > when
> > > > > > copy/pasting:
> > > > > >
> > > > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > > > >
> > > > > > Jan
> > > > > >
> > > > > > > 13. jan. 2024 kl. 17:14 skrev David Smiley  >:
> > > > > > >
> > > > > > > Please vote for release candidate 1 for Solr 9.4.1
> > > > > > >
> > > > > > > The artifacts can be downloaded from:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > > > > >
> > > > > > >
> > > > > > > You can run the smoke tester directly with this command:
> > > > > > >
> > > > > > >
> > > > > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > > > > >
> > > > > > >
> > > > > > > You can build a release-candidate of the official docker images
> > > > (full &
> > > > > > > slim) using the following command:
> > > > > > >
> > > > > > >
> > > > > > > SOLR_DOWNLOAD_SERVER=
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476/solr
> > > > > > > && \
> > > > > > >
> > > > > > >  docker build
> > > > > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-full \
> > > > > > >
> > > > > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > > > > >
> > > > > > >-t solr-rc:9.4.1-1 && \
> > > > > > >
> > > > > > >  docker build
> > > > > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-slim \
> > > > > > >
> > > > > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > > > > >
> > > > > > >-t solr-rc:9.4.1-1-slim
> > > > > > >
> > > > > > >
> > > > > > > The vote will be open for at least 72 hours i.e. until
> 2024-01-16
> > > > 17:00
> > > > > > UTC.
> > > > > > >
> > > > > > >
> > > > > > > [ ] +1  approve
> > > > > > >
> > > > > > > [ ] +0  no opinion
> > > > > > >
> > > > > > > [ ] -1  disapprove (and reason why)
> > > > > > >
> > > > > > >
> > > > > > > Here is my +1
> > > > > > >
> > > > > > > ~ David Smiley
> > > > > > > Apache Lucene/Solr Search Developer
> > > > > > > http://www.linkedin.com/in/davidwsmiley
> > > > > >
> > > > > >
> > > > > >
> > -
> > > > > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org

Re: [DISCUSS] SIP-20: Separation of Compute and Storage in SolrCloud

[Jason Gerlowski]

Hey Ilan,

Thanks for putting together this writeup.  I think I understand the goal
conceptually, and it sounds like a good one for Solr!  But I'm still having
trouble understanding how this all would actually work.  So a few
questions, inline:

> A fourth replica type called ZERO is introduced

Why the name "Zero"? Is it conveying something about the design that I'm
not picking up on?

> At Collection creation time, it is possible to specify that the
collection exclusively uses replicas of type ZERO rather than being a
“normal” collection that uses NRT/TLOG/PULL.

Am I correct in understanding this to mean that if "zero" is used, it must
be used for every replica in the collection?  If so, it almost sounds like
this isn't a new type of replica but a new "collection type" altogether?

> This allows scaling compute (more queries, more indexing) independently
of storage

I think the biggest question I have is: how does the "compute" side of this
actually work?

On the indexing side: what all happens in Solr before giving a response
back to users?  What happens on a commit?  Are updates indexed only on the
leader (like TLOG/PULL) or on all replicas (like NRT), or some other
arrangement altogether?

On the querying side: what situations cause index data to be pulled from
the remote store?

(These last questions might be a bit lengthy to get into via email, but
they should probably be in the writeup?  Not sure what's best there...)

Best,

Jason

On Sat, Jan 13, 2024 at 9:15 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:

> +1, thanks for the contribution Ilan! Looking forward to seeing this coming
> to fruition.
>
> On Sun, 14 Jan 2024 at 03:40, Ilan Ginzburg  wrote:
>
> > I have created SIP-20
> >
> >
> https://cwiki.apache.org/confluence/display/SOLR/SIP-20%3A+Separation+of+Compute+and+Storage+in+SolrCloud
> >
> > In the next few days I will create a Jira + a branch that implements
> > the SIP proposal and that includes documentation on how to approach
> > that branch and what's in it.
> >
> > This proposed contribution is based on work done at Salesforce these
> > last few years and currently running at scale in multiple regions.
> >
> > Thanks,
> > Ilan
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > For additional commands, e-mail: dev-h...@solr.apache.org
> >
> >
>

Re: [DISCUSS] Community Virtual Meetup, January 2024

[raghavan m]

Hello everyone
*Reminder!!* 1/18 9 am pacific time Apache Solr Virtual Meetup (10:30 pm
IST)
Please directly edit meeting notes for agenda
https://cwiki.apache.org/confluence/display/SOLR/2024-01-18+Meeting+notes

thanks,
*Raghavan*


On Mon, Jan 15, 2024 at 4:58 AM Eric Pugh 
wrote:

> One more topic would be a discussion about a hackathon that is being
> proposed for C/C 2024 NA.
>
> > On Jan 15, 2024, at 4:04 AM, raghavan m  wrote:
> >
> > Thanks, Eric. I updated the page with the two topics
> >
> > Everyone,
> > The meetup will be on 01/18 9 am pacific time, 10:30pm IST.
> > Please submit topics that you would like to discuss here.
> >
> https://cwiki.apache.org/confluence/display/SOLR/2024-01-18+Meeting+notes
> >
> > https://meet.google.com/wek-upvd-pff
> >
> > thanks,
> > *Raghavan*
> >
> >
> > On Fri, Jan 12, 2024 at 10:19 AM Eric Pugh <
> ep...@opensourceconnections.com >
> > wrote:
> >
> >> I’d be interested in a discussion around:
> >>
> >> Standardizing System Property Names and Ramifications:
> >> https://lists.apache.org/thread/ckb3tqnjf0h66rd0mlpfblpvkrvp3wq6
> >>
> >> Migration from JIRA to Github for issues:
> >> https://lists.apache.org/thread/7kg0m7528h4xox1hzf5wb26fzcl9758g
> >>
> >> I’d love to also share some early plans for a 1 day Hackathon for
> various
> >> Search related projects at C / C North America coming up this year.
> >>
> >>
> >>
> >>> On Jan 11, 2024, at 6:46 PM, raghavan m 
> wrote:
> >>>
> >>> Hello everyone
> >>> So far, 1/18 is the most voted date. I’ll announce in meetup and slack
> >>> channels, also create a meeting notes page.
> >>> Please reply to this thread with any agenda/ presentation that you want
> >> to
> >>> discuss.
> >>>
> >>> Thanks
> >>> Raghavan
> >>>
> >>> Sent from iPhone
> >>>
> >>>
> >>> On Wed, Jan 10, 2024 at 10:42 PM Marcus Eagan 
> >> wrote:
> >>>
>  On the 18th, I'll be available to join.
> 
>  On Wed, Jan 10, 2024 at 7:06 PM David Smiley 
> >> wrote:
> 
> > 18th
> > or probably any
> >
> > On Wed, Jan 10, 2024 at 12:15 AM raghavan m 
> > wrote:
> >
> >> Hey everyone,
> >> Please vote for one of the following days
> >>
> >>  - 1/15
> >>  - 1/16
> >>  - 1/17
> >>  - 1/18
> >>  - 1/19
> >>  - 1/22
> >>
> >> Time: 9 am pacific time.
> >> Thanks
> >> Raghavan
> >>
> >> Sent from iPhone
> >>
> >>
> >> On Mon, Jan 8, 2024 at 5:27 AM Jason Gerlowski <
> gerlowsk...@gmail.com
> >>>
> >> wrote:
> >>
> >>> Awesome, thanks for volunteering Raghavan!
> >>>
> >>> Anyone have thoughts on scheduling?  Absent other strong opinions,
> > maybe
> >> we
> >>> could aim for the week of Monday the 15th through Friday the 19th
> and
> >> pick
> >>> a day/time in that range?
> >>>
> >>> Best,
> >>>
> >>> Jason
> >>>
> >>> On Sun, Jan 7, 2024 at 1:27 AM raghavan m 
> >> wrote:
> >>>
>  Happy New Year everyone. I can volunteer for January.
> 
>  Sent from iPhone
> 
> 
>  On Tue, Jan 2, 2024 at 7:49 AM Jason Gerlowski <
> > gerlowsk...@gmail.com>
>  wrote:
> 
> > Hey all,
> >
> > After missing December, It's time once again to start thinking
> > ahead
> >> to
>  our
> > first Virtual Meetup in the New Year!  As always, there's two
>  main
> > questions to answer in terms of planning:
> >
> > 1. Any volunteers to organize?  Organizer duties are pretty light
> > and
> >>> are
> > summarized here:
> > https://cwiki.apache.org/confluence/display/SOLR/Meeting+notes.
> > Volunteers
> > get some discretion in terms of picking a meeting time/day that
> > works
> >>> for
> > them.  If there are no volunteers by the end of the week, I'm
>  more
> >> than
> > happy to set things up for this month.
> >
> > 2. When should we meet?  I've started the discussion early this
> >> month,
> >>> so
> > we've got plenty of days to choose from.  If you have any
>  opinions,
>  please
> > discuss.
> >
> > Best,
> >
> > Jason
> >
> 
> >>>
> >>
> >
> 
> 
>  --
>  Marcus Eagan
> 
> >>
> >> ___
> >> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 |
> >> http://www.opensourceconnections.com <
> >> http://www.opensourceconnections.com/> | My Free/Busy <
> >> http://tinyurl.com/eric-cal>
> >> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> >>
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> >
> >>
> >> This e-mail and all contents, including attachments, is considered to be
> >> Company Confidential unless explicit

Re: [DISCUSS] SIP-20: Separation of Compute and Storage in SolrCloud

[Ilan Ginzburg]

Hi Jason,

Good questions!
Note there is a related question on the users list, see thread Node roles
vs SIP-20 Separation of Compute and Storage


When I share the code (later this week in all likelihood) I will share a
detailed write up. I'm open to discuss/present/write more as needed (and
plan to attend Thursday 18/1 Meetup
 to
present the SIP).

To your questions:

   - The name "Zero" is because "Shared" was too broad (and already used)
   and "Blob" was already used as well in Solr code, and we didn't find any
   better name (but the name can be changed, there are a couple thousand
   occurrences of it in different forms in the code, I know because "Zero" is
   not the name we use internally at Salesforce for that replica type, I've
   renamed everything for sharing here). The reason for "Zero" is that there
   is only one instance (zero copies) in persistent storage for each shard,
   and also this evoques the (longer term) option to have zero (i.e. no)
   replicas for a shard on the cluster, pick a node, load and materialize a
   replica when needed. But that's longer term.
   - Your understanding is correct, currently it's a kind of new type of
   collection given all replicas are ZERO (or none are) for a collection. ZERO
   could have been a new type of shard, as one could imagine different shards
   having different types (but shards do not have types), or why not also
   allow a given shard to have ZERO replicas as well as other types of
   replicas (this is not supported in the current implementation for
   simplicity and we didn't really felt the need). If collectively we think
   that PULL + ZERO do make sense, why not. PULL would then be fetching its
   content from ZERO replicas rather than directly from the shared storage. I
   don't see ZERO coexisting with NRT or TLOG in a given shard though.
   Currently as the implementation forces all replicas of all shards of a
   "Zero" collection to be ZERO, there is a flag on that collection saying it
   is a Zero collection.
   - How the compute behaves:
   With the implementation in its current state, an indexing batch (as sent
   by the client) is processed by the leader replica, committed to local disk
   then written into the remote storage (S3) before SolrCloud acknowledges the
   batch. Transaction log is not used and the commit is forced. This slows
   down indexing, but a design guideline from the start was that the SolrCloud
   nodes are stateless (can restart with empty disk) to simplify managing
   elasticity (and in a public cloud setting, Availability Zone failures).
   The next evolution step of this code that we plan to start upstream once
   the branch has been shared is to enable the transaction log for ZERO
   replicas, and have indexing behave more like a normal SolrCloud: persist
   the transaction log before replying to a client, do not force a commit. The
   transaction log would be changed to be on shared storage as well, with a
   single copy for a shard, not one log per node/replica. All replicas of the
   shard, when they're becoming leaders, would access the same transaction
   log. Some of the logic used for implementing the shared storage for the
   index segments will be reused.
   For serving queries, the non leader replicas (also of type ZERO) update
   themselves from the shared storage directly. They behave mostly like PULL
   replicas (except the data doesn't come from the leader but from the shared
   storage), but can become leader because the shared storage is the "source
   of truth" and by reading all the data present there, any replica can get
   itself up to date with all acknowledged updates to become leader (there is
   protection so two replicas that think they're leader at the same time do
   not overwrite each other, I can describe this on another occasion).
   Currently the (basic) approach is that a replica checks if it is up to
   date as long as it's getting queries. If it is already up to date, the cost
   of that check is a ZooKeeper node read. If it is not up to date, it then
   fetches the updated content from the shared storage. Other strategies
   (check less often, check while not getting queries etc. are easy to
   implement). The updates are currently done asynchronously so do not delay
   the queries (that serve the "previous" content, like normal SolrCloud
   replication does).

I'd be happy to discuss and explain this in more detail. Quickly tomorrow
then more once I've shared the source code branch and the design doc.
I'd of course be happy to also follow up here with any questions, so don't
hesitate to ask!

Ilan



On Wed, Jan 17, 2024 at 8:30 PM Jason Gerlowski 
wrote:

> Hey Ilan,
>
> Thanks for putting together this writeup.  I think I understand the goal
> conceptually, and it sounds like a good one for Solr!  But I'm still having
> troub

Re: [DISCUSS] Community Virtual Meetup, January 2024

[Marcus Eagan]

Is it possible to send out a calendar link as well, like this:
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MmhoOGQyb3JucWZyc3UybWY4azE0YTFjZDIgbWFyY3VzZWFnYW5AbQ&tmsrc=marcuseagan%40gmail.com

That's an example. It's not real.

On Wed, Jan 17, 2024 at 4:32 PM raghavan m  wrote:

> Hello everyone
> *Reminder!!* 1/18 9 am pacific time Apache Solr Virtual Meetup (10:30 pm
> IST)
> Please directly edit meeting notes for agenda
> https://cwiki.apache.org/confluence/display/SOLR/2024-01-18+Meeting+notes
>
> thanks,
> *Raghavan*
>
>
> On Mon, Jan 15, 2024 at 4:58 AM Eric Pugh  >
> wrote:
>
> > One more topic would be a discussion about a hackathon that is being
> > proposed for C/C 2024 NA.
> >
> > > On Jan 15, 2024, at 4:04 AM, raghavan m 
> wrote:
> > >
> > > Thanks, Eric. I updated the page with the two topics
> > >
> > > Everyone,
> > > The meetup will be on 01/18 9 am pacific time, 10:30pm IST.
> > > Please submit topics that you would like to discuss here.
> > >
> >
> https://cwiki.apache.org/confluence/display/SOLR/2024-01-18+Meeting+notes
> > >
> > > https://meet.google.com/wek-upvd-pff
> > >
> > > thanks,
> > > *Raghavan*
> > >
> > >
> > > On Fri, Jan 12, 2024 at 10:19 AM Eric Pugh <
> > ep...@opensourceconnections.com  >>
> > > wrote:
> > >
> > >> I’d be interested in a discussion around:
> > >>
> > >> Standardizing System Property Names and Ramifications:
> > >> https://lists.apache.org/thread/ckb3tqnjf0h66rd0mlpfblpvkrvp3wq6
> > >>
> > >> Migration from JIRA to Github for issues:
> > >> https://lists.apache.org/thread/7kg0m7528h4xox1hzf5wb26fzcl9758g
> > >>
> > >> I’d love to also share some early plans for a 1 day Hackathon for
> > various
> > >> Search related projects at C / C North America coming up this year.
> > >>
> > >>
> > >>
> > >>> On Jan 11, 2024, at 6:46 PM, raghavan m 
> > wrote:
> > >>>
> > >>> Hello everyone
> > >>> So far, 1/18 is the most voted date. I’ll announce in meetup and
> slack
> > >>> channels, also create a meeting notes page.
> > >>> Please reply to this thread with any agenda/ presentation that you
> want
> > >> to
> > >>> discuss.
> > >>>
> > >>> Thanks
> > >>> Raghavan
> > >>>
> > >>> Sent from iPhone
> > >>>
> > >>>
> > >>> On Wed, Jan 10, 2024 at 10:42 PM Marcus Eagan  >
> > >> wrote:
> > >>>
> >  On the 18th, I'll be available to join.
> > 
> >  On Wed, Jan 10, 2024 at 7:06 PM David Smiley 
> > >> wrote:
> > 
> > > 18th
> > > or probably any
> > >
> > > On Wed, Jan 10, 2024 at 12:15 AM raghavan m <
> raghavan@gmail.com>
> > > wrote:
> > >
> > >> Hey everyone,
> > >> Please vote for one of the following days
> > >>
> > >>  - 1/15
> > >>  - 1/16
> > >>  - 1/17
> > >>  - 1/18
> > >>  - 1/19
> > >>  - 1/22
> > >>
> > >> Time: 9 am pacific time.
> > >> Thanks
> > >> Raghavan
> > >>
> > >> Sent from iPhone
> > >>
> > >>
> > >> On Mon, Jan 8, 2024 at 5:27 AM Jason Gerlowski <
> > gerlowsk...@gmail.com
> > >>>
> > >> wrote:
> > >>
> > >>> Awesome, thanks for volunteering Raghavan!
> > >>>
> > >>> Anyone have thoughts on scheduling?  Absent other strong
> opinions,
> > > maybe
> > >> we
> > >>> could aim for the week of Monday the 15th through Friday the 19th
> > and
> > >> pick
> > >>> a day/time in that range?
> > >>>
> > >>> Best,
> > >>>
> > >>> Jason
> > >>>
> > >>> On Sun, Jan 7, 2024 at 1:27 AM raghavan m <
> raghavan@gmail.com>
> > >> wrote:
> > >>>
> >  Happy New Year everyone. I can volunteer for January.
> > 
> >  Sent from iPhone
> > 
> > 
> >  On Tue, Jan 2, 2024 at 7:49 AM Jason Gerlowski <
> > > gerlowsk...@gmail.com>
> >  wrote:
> > 
> > > Hey all,
> > >
> > > After missing December, It's time once again to start thinking
> > > ahead
> > >> to
> >  our
> > > first Virtual Meetup in the New Year!  As always, there's two
> >  main
> > > questions to answer in terms of planning:
> > >
> > > 1. Any volunteers to organize?  Organizer duties are pretty
> light
> > > and
> > >>> are
> > > summarized here:
> > > https://cwiki.apache.org/confluence/display/SOLR/Meeting+notes
> .
> > > Volunteers
> > > get some discretion in terms of picking a meeting time/day that
> > > works
> > >>> for
> > > them.  If there are no volunteers by the end of the week, I'm
> >  more
> > >> than
> > > happy to set things up for this month.
> > >
> > > 2. When should we meet?  I've started the discussion early this
> > >> month,
> > >>> so
> > > we've got plenty of days to choose from.  If you have any
> >  opinions,
> >  please
> > > discuss.
> > >
> > > Best,

Re: [DISCUSS] Community Virtual Meetup, January 2024

[raghavan m]

Thanks Marcus. I sent an event invite via meetup.com.
https://www.meetup.com/apache-solr-virtual-community-meetups/events/298557704

Perhaps I could have sent that link here if you want to sign up.

thanks,
Raghavan


On Wed, Jan 17, 2024 at 5:05 PM Marcus Eagan  wrote:

> Is it possible to send out a calendar link as well, like this:
>
> https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MmhoOGQyb3JucWZyc3UybWY4azE0YTFjZDIgbWFyY3VzZWFnYW5AbQ&tmsrc=marcuseagan%40gmail.com
>
> That's an example. It's not real.
>
> On Wed, Jan 17, 2024 at 4:32 PM raghavan m  wrote:
>
> > Hello everyone
> > *Reminder!!* 1/18 9 am pacific time Apache Solr Virtual Meetup (10:30 pm
> > IST)
> > Please directly edit meeting notes for agenda
> >
> https://cwiki.apache.org/confluence/display/SOLR/2024-01-18+Meeting+notes
> >
> > thanks,
> > *Raghavan*
> >
> >
> > On Mon, Jan 15, 2024 at 4:58 AM Eric Pugh <
> ep...@opensourceconnections.com
> > >
> > wrote:
> >
> > > One more topic would be a discussion about a hackathon that is being
> > > proposed for C/C 2024 NA.
> > >
> > > > On Jan 15, 2024, at 4:04 AM, raghavan m 
> > wrote:
> > > >
> > > > Thanks, Eric. I updated the page with the two topics
> > > >
> > > > Everyone,
> > > > The meetup will be on 01/18 9 am pacific time, 10:30pm IST.
> > > > Please submit topics that you would like to discuss here.
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/SOLR/2024-01-18+Meeting+notes
> > > >
> > > > https://meet.google.com/wek-upvd-pff
> > > >
> > > > thanks,
> > > > *Raghavan*
> > > >
> > > >
> > > > On Fri, Jan 12, 2024 at 10:19 AM Eric Pugh <
> > > ep...@opensourceconnections.com  ep...@opensourceconnections.com
> > >>
> > > > wrote:
> > > >
> > > >> I’d be interested in a discussion around:
> > > >>
> > > >> Standardizing System Property Names and Ramifications:
> > > >> https://lists.apache.org/thread/ckb3tqnjf0h66rd0mlpfblpvkrvp3wq6
> > > >>
> > > >> Migration from JIRA to Github for issues:
> > > >> https://lists.apache.org/thread/7kg0m7528h4xox1hzf5wb26fzcl9758g
> > > >>
> > > >> I’d love to also share some early plans for a 1 day Hackathon for
> > > various
> > > >> Search related projects at C / C North America coming up this year.
> > > >>
> > > >>
> > > >>
> > > >>> On Jan 11, 2024, at 6:46 PM, raghavan m 
> > > wrote:
> > > >>>
> > > >>> Hello everyone
> > > >>> So far, 1/18 is the most voted date. I’ll announce in meetup and
> > slack
> > > >>> channels, also create a meeting notes page.
> > > >>> Please reply to this thread with any agenda/ presentation that you
> > want
> > > >> to
> > > >>> discuss.
> > > >>>
> > > >>> Thanks
> > > >>> Raghavan
> > > >>>
> > > >>> Sent from iPhone
> > > >>>
> > > >>>
> > > >>> On Wed, Jan 10, 2024 at 10:42 PM Marcus Eagan <
> marcusea...@gmail.com
> > >
> > > >> wrote:
> > > >>>
> > >  On the 18th, I'll be available to join.
> > > 
> > >  On Wed, Jan 10, 2024 at 7:06 PM David Smiley 
> > > >> wrote:
> > > 
> > > > 18th
> > > > or probably any
> > > >
> > > > On Wed, Jan 10, 2024 at 12:15 AM raghavan m <
> > raghavan@gmail.com>
> > > > wrote:
> > > >
> > > >> Hey everyone,
> > > >> Please vote for one of the following days
> > > >>
> > > >>  - 1/15
> > > >>  - 1/16
> > > >>  - 1/17
> > > >>  - 1/18
> > > >>  - 1/19
> > > >>  - 1/22
> > > >>
> > > >> Time: 9 am pacific time.
> > > >> Thanks
> > > >> Raghavan
> > > >>
> > > >> Sent from iPhone
> > > >>
> > > >>
> > > >> On Mon, Jan 8, 2024 at 5:27 AM Jason Gerlowski <
> > > gerlowsk...@gmail.com
> > > >>>
> > > >> wrote:
> > > >>
> > > >>> Awesome, thanks for volunteering Raghavan!
> > > >>>
> > > >>> Anyone have thoughts on scheduling?  Absent other strong
> > opinions,
> > > > maybe
> > > >> we
> > > >>> could aim for the week of Monday the 15th through Friday the
> 19th
> > > and
> > > >> pick
> > > >>> a day/time in that range?
> > > >>>
> > > >>> Best,
> > > >>>
> > > >>> Jason
> > > >>>
> > > >>> On Sun, Jan 7, 2024 at 1:27 AM raghavan m <
> > raghavan@gmail.com>
> > > >> wrote:
> > > >>>
> > >  Happy New Year everyone. I can volunteer for January.
> > > 
> > >  Sent from iPhone
> > > 
> > > 
> > >  On Tue, Jan 2, 2024 at 7:49 AM Jason Gerlowski <
> > > > gerlowsk...@gmail.com>
> > >  wrote:
> > > 
> > > > Hey all,
> > > >
> > > > After missing December, It's time once again to start
> thinking
> > > > ahead
> > > >> to
> > >  our
> > > > first Virtual Meetup in the New Year!  As always, there's two
> > >  main
> > > > questions to answer in terms of planning:
> > > >
> > > > 1. Any volunteers to organize?  Organizer duties are pretty
> > light
> > > > and
> > > >>> are
> > > > summarized here:
> > > >>