Dear Apache Solr Community,
My name is *Surafel Temesgen*, and I’m thrilled to introduce a project I’ve
been working on called *Debo* — a lightweight, unified infrastructure
management platform that provides monitoring and control across various big
data technologies, including *Apache Solr
n't
> see any downside to just letting it go - it's just one more CI.
>
> D.
>
> On Tue, Apr 22, 2025 at 7:30 PM Christos Malliaridis
> wrote:
> >
> > Infra provided us with two new nodes – lucene-solr-3 and lucene-solr-4 –
> to replace the old ones. The
Nice! I can't think of anything. I guess we just let it burn? I can't
see any downside to just letting it go - it's just one more CI.
D.
On Tue, Apr 22, 2025 at 7:30 PM Christos Malliaridis
wrote:
>
> Infra provided us with two new nodes – lucene-solr-3 and lucene-solr-4 –
Infra provided us with two new nodes – lucene-solr-3 and lucene-solr-4 – to
replace the old ones. They come with upgraded hardware:
16GB -> 32GB RAM
> 4CPU -> 16CPU
> 256/350GB -> 500GB disk
Once we are ready to turn off the old nodes, I'll respond to the Jira issue.
*
dejs,) and those lead to package conflicts so
> >>>> do-release-upgrade
> >>>> bails out.
> >>>
> >>>> I could uninstall all those PPAs with "ppa-purge", but I don't know
> >>>> how
> >>>> to get
rry, but puppet is the worst tool that I try to avoid at all of my
customers, it always causes issues administering machines for Solr
installations!).
I can do the jenkins home directory backup tomorrow and then we can
ask
them to reinstall newer OS. We just need to make sure to tell them that
s, it always causes issues administering machines for Solr
installations!).
I can do the jenkins home directory backup tomorrow and then we can ask
them to reinstall newer OS. We just need to make sure to tell them that
they should use a puppet configuration that contains all packages we
need for Je
tool that I try to avoid at all of my
> customers, it always causes issues administering machines for Solr
> installations!).
> I can do the jenkins home directory backup tomorrow and then we can ask
them to reinstall newer OS. We just need to make sure to tell them that
> they sh
ll of my
customers, it always causes issues administering machines for Solr
installations!).
I can do the jenkins home directory backup tomorrow and then we can ask
them to reinstall newer OS. We just need to make sure to tell them that
they should use a puppet configuration that contains all
indler:
> >
> > Hi,
> >
> > I have root access on both machines. Indeed one of them (lucene-solr1)
> > is Ubuntu 18.04 LTS and the other one (lucene-solr - no digit) is
> > Unbuntu 20.04 LTS. In fact, both are outdated, whereas the first one
> > is out
Security updates ongoing... reboot ongoing... running again... 😉
Uwe
Am 27.03.2025 um 16:40 schrieb Uwe Schindler:
Hi,
see my mails on the lucene ML, these ones were lost as they only got
to Solr.
Actually, I was involved together with Jenkins and I also have root
access. Yes, they were
Hi,
see my mails on the lucene ML, these ones were lost as they only got to
Solr.
Actually, I was involved together with Jenkins and I also have root
access. Yes, they were provided by Infra, but there was some additional
work needed to make them Jenkins nodes. It is long ago that I touched
-solr - no digit) is
Unbuntu 20.04 LTS. In fact, both are outdated, whereas the first one
is out of support as far as I remember.
There are two ways:
* do-release-upgrade => this works well on Ubuntu LTS nodes, never
had a problem with that. In fact the one on Ubuntu 20.04 was
upda
Hi,
I have root access on both machines. Indeed one of them (lucene-solr1)
is Ubuntu 18.04 LTS and the other one (lucene-solr - no digit) is
Unbuntu 20.04 LTS. In fact, both are outdated, whereas the first one is
out of support as far as I remember.
There are two ways:
* do-release
Was it actually only one machine that was too out-of-date?
On Wed, Mar 26, 2025 at 1:05 PM Christos Malliaridis
wrote:
> Hello everyone,
>
> In consultation with David Smiley, I am planning to request an OS upgrade
> for our build nodes *lucene-solr-1* and *lucene-solr-2* on Monday
ade
> for our build nodes *lucene-solr-1* and *lucene-solr-2* on Monday, March
> 31, as they are running older operating systems and causing OS-related
> build errors in the Solr project.
>
> Since the nodes will be replaced with new instances, they will need to be
> reconfigure
Hello everyone,
In consultation with David Smiley, I am planning to request an OS upgrade
for our build nodes *lucene-solr-1* and *lucene-solr-2* on Monday, March
31, as they are running older operating systems and causing OS-related
build errors in the Solr project.
Since the nodes will be
Hello and good time
I have problem connecting solr 9 to hadoop
I put the logs in the attachment
It is very important to me, but no matter what I do, they are not connected to
create a new collection
It connects to Apache ZooKeeper but not Hadoop
What is the solution?
what should i do
Please
Also as a workaround, I can confirm that setting indexSearcherExecutor to 0
from the Solr side as mentioned in
https://issues.apache.org/jira/browse/SOLR-17642 mitigates the problem for
now.
On Thu, Jan 30, 2025 at 10:40 AM Benjamin Trent
wrote:
> Yes, FYI, we found the bug in the kNN qu
Moll for bringing this to our attention!
On Thu, Jan 30, 2025 at 1:26 PM Varun Thacker wrote:
> Benjamin - I think this has to do with Solr 9.7+ using thread executor's
> for searching.
>
> I can take Solr 9.7 or Solr 9.8 and just undo this one line in
> SolrIndexSearcher
&
Benjamin - I think this has to do with Solr 9.7+ using thread executor's
for searching.
I can take Solr 9.7 or Solr 9.8 and just undo this one line in
SolrIndexSearcher
<https://github.com/apache/solr/blob/7af2ad56753bf75b8391639233dcc8d465767de9/solr/core/src/java/org/apache/sol
did happen in 9.10:
https://github.com/apache/lucene/pull/12962 But since this issue doesn't
happen in 9.10, I am at a loss.
Since `knn` rewrites itself to `KnnScoreDoc` object, It's surprising that
the result set should change between collecting and scoring.
I wonder if Solr adjuste
Hi,
I want to inform you about a behavior change in SolR 9.6 (Lucene 9.10) vs. SolR
9.7 (Lucene 9.11) for vector searches.
We heavily rely on vector searches for embeddings in combination with filter
queries on the parent documents.
Our queries in general looked like this:
select?q={ knn f
> >
> > > looks like killing the stuck slave process ("sudo pkill -9 -u
> > > jenkins") helped lucene-solr-2 to recover.
> > >
> > > Uwe
> > >
> > > Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
> > >> Hi Uwe
> > &
news at
> https://solr.apache.org/news.html#apache-solrtm-8114-available and it says
>
> -
> Solr is the blazing-fast, open source, multi-modal search platform built
> on Apache Lucene. It powers full-text, vector, analytics, and geospatial
> search at many of the world
Hi
> This vote has PASSED
Congrats!
I've read the release news at
https://solr.apache.org/news.html#apache-solrtm-8114-available and it says
-----
Solr is the blazing-fast, open source, multi-modal search platform built on
Apache Lucene. It powers full-text, vector, analytics, and ge
l. 20:51 skrev Houston Putman :
>
> Please vote for release candidate 1 for Lucene/Solr 8.11.4
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.4-RC1-reve27f44e3d78dfcec230c97e0a1240e3751daeff9
>
> You can run the smoke
It's been >72h since the vote was initiated and the result is:
+1 5 (5 binding)
0 0
-1 0
This vote has PASSED
+1
SUCCESS! [1:29:27.098734] (on fifth run or something)
Jan
> 19. sep. 2024 kl. 20:51 skrev Houston Putman :
>
> Please vote for release candidate 1 for Lucene/Solr 8.11.4
>
> The artifacts can be downloaded from:
> https://dist.apache.org/repos/dist/dev/lucene/luce
for release candidate 1 for Lucene/Solr 8.11.4
>>
>> The artifacts can be downloaded from:
>>
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.4-RC1-reve27f44e3d78dfcec230c97e0a1240e3751daeff9
>>
>> You can run the smoke tester directly with this
+1 (binding)
SUCCESS! [1:01:01.305159]
On Thu, Sep 19, 2024 at 11:51 AM Houston Putman wrote:
> Please vote for release candidate 1 for Lucene/Solr 8.11.4
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-
t; 6.6.1
>>>
>>> 6.6.2
>>>
>>> 6.6.3
>>>
>>> 6.6.4
>>>
>>> 6.6.5
>>>
>>> 6.6.6
>>>
>>> 7.0.0
>>>
>>> 7.0.1
>>>
>>> 7.1.0
>&
8.5.1
>>
>> 8.5.2
>>
>> 8.6.0
>>
>> 8.6.1
>>
>> 8.6.2
>>
>> 8.6.3
>>
>> 8.7.0
>>
>> 8.8.0
>>
>> 8.8.1
>>
>> 8.8.2
>>
>> 8.9.0
>>
>> 8.10.0
>>
mokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
> c.is_signed, c.local_keys, ' '.join(c.test_args),
>
> File
> "/Users/dsmiley/DevSearch/lucene-solr_8x/dev-tools/scripts/smokeTestRelease.py",
> line 1477, in smokeTest
>
&g
e 1397, in confirmAllReleasesAreTestedForBackCompat
raise RuntimeError('some releases are not tested by
TestBackwardsCompatibility?')
RuntimeError: some releases are not tested by TestBackwardsCompatibility?
On Thu, Sep 19, 2024 at 2:51 PM Houston Putman wrote:
> Please vote for release candidate 1 for
Please vote for release candidate 1 for Lucene/Solr 8.11.4
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.4-RC1-reve27f44e3d78dfcec230c97e0a1240e3751daeff9
You can run the smoke tester directly with this command:
python3 -u dev-tools/scripts
NOTICE:
I am now preparing for a bugfix release from branch branch_8_11
Please observe the normal rules for committing to this branch:
* Before committing to the branch, reply to this thread and argue
why the fix needs backporting and how long it will take.
* All issues accepted for backportin
Am 26.06.2024 um 22:39 schrieb Uwe Schindler:
> > Hi,
> >
> > looks like killing the stuck slave process ("sudo pkill -9 -u
> > jenkins") helped lucene-solr-2 to recover.
> >
> > Uwe
> >
> > Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
> >
u
jenkins") helped lucene-solr-2 to recover.
Uwe
Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
Hi Uwe
Thanks for the context! A few follow-up questions for you (or anyone
else that can answer):
1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
is lacking, but I
Hi,
looks like killing the stuck slave process ("sudo pkill -9 -u jenkins")
helped lucene-solr-2 to recover.
Uwe
Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
Hi Uwe
Thanks for the context! A few follow-up questions for you (or anyone
else that can answer):
1. What's t
Hi Jason,
Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
Hi Uwe
Thanks for the context! A few follow-up questions for you (or anyone
else that can answer):
1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
is lacking, but I can't find the full hostname expose
Hi Uwe
Thanks for the context! A few follow-up questions for you (or anyone
else that can answer):
1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
is lacking, but I can't find the full hostname exposed anywhere in
Jenkins, and I'd like to try SSH-ing in.
Hi,
yes e.g., I have access to that machine and can issue a reboot. The two
machines are VMs specifically owned by the Lucene PMC (not Solr as far
as I remeber), but they were created before the split of projects.
Some people have direct access, not sure how this is managed. Basically
to
Hey all,
Sending this email to discuss the ASF Jenkins' 'lucene-solr-1' worker
node, which both Lucene and Solr use to run builds.
While investigating a recent issue with some Solr builds, I asked
INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I
Not sure why this ancient build ran at all - I turned it off.
D.
On Tue, Jun 4, 2024 at 3:49 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Solr-NightlyTests-8.10/57/
>
> No tests ran.
>
> Buil
Hi Solr Community,
We are getting below error message while indexing the data in SOLR.
request:http://x.x.x.x:8983/solr/fieldportal_shard2_replica_n5/
Remote error message: ERROR:
[doc=/content/dam/agilent/en/entitled-partner/checklist/plm Maintenance
Checklist.pdf] unknown field
Hey Vijay,
I'm afraid this isn't the appropriate channel for your query. Please reach
out to us...@solr.apache.org (https://solr.apache.org/community.html) for
assistance with Solr-related issues, and someone will certainly help you
out. When you reach out, be sure to include the stack
Hi Support Team,
We are facing solr issues like stalled issue and cancel stream
error,Checked the logs and got this stalled issue when solr is trying to
replicate data with dead/down replicas we are facing this issue,Can you
please help on this.
Solr version:-9.2
Thanks
Vijay
It's been >72h since the vote was initiated and the result is:
+1 6 (6 binding)
0 0
-1 0
This vote has PASSED
gt;>
>>> SUCCESS! [1:18:24.494917]
>>>
>>> On Wed, 7 Feb 2024 at 18:24, Jan Høydahl wrote:
>>>
>>>> +1 (binding)
>>>>
>>>> SUCCESS! [1:18:11.930433]
>>>>
>>>> Only ran smoke tester. macOS, Temurin 1.8.0
> +1 (binding)
>>
>> SUCCESS! [1:18:24.494917]
>>
>> On Wed, 7 Feb 2024 at 18:24, Jan Høydahl wrote:
>>
>>> +1 (binding)
>>>
>>> SUCCESS! [1:18:11.930433]
>>>
>>> Only ran smoke tester. macOS, Temurin 1.8.0_402
>
8:11.930433]
>>
>> Only ran smoke tester. macOS, Temurin 1.8.0_402
>>
>> Jan
>>
>> 5. feb. 2024 kl. 23:23 skrev Houston Putman :
>>
>> Please vote for release candidate 1 for Lucene/Solr 8.11.3
>>
>> The a
or release candidate 1 for Lucene/Solr 8.11.3
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.3-RC1-revbaa7c80af4278cc8951a344d8e9320386588d12d
>
> You can run the smoke tester directly with this command:
>
> pyt
+1 (binding)
SUCCESS! [1:18:11.930433]
Only ran smoke tester. macOS, Temurin 1.8.0_402
Jan
> 5. feb. 2024 kl. 23:23 skrev Houston Putman :
>
> Please vote for release candidate 1 for Lucene/Solr 8.11.3
>
> The artifacts can be downloaded from:
> https://dist.apache.org/rep
I'm running the smoke tester on branch_8_11
python3 -u dev-tools/scripts/smokeTestRelease.py \
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.3-RC1-revbaa7c80af4278cc8951a344d8e9320386588d12d
and getting
File
> "/Users/risdenk/repos/apache/lucene-solr/dev-
Here's my +1 (binding)
SUCCESS! [0:56:16.591754]
On Mon, Feb 5, 2024 at 5:23 PM Houston Putman wrote:
> Please vote for release candidate 1 for Lucene/Solr 8.11.3
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lu
Please vote for release candidate 1 for Lucene/Solr 8.11.3
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.3-RC1-revbaa7c80af4278cc8951a344d8e9320386588d12d
You can run the smoke tester directly with this command:
python3 -u dev-tools/scripts
Shouldn't we wait for the 9.4.1 to go out first? That's what I was holding
out on.
On Sat, 13 Jan, 2024, 12:43 am Houston Putman, wrote:
> NOTICE:
>
> I am now preparing for a bugfix release from branch branch_8_11
>
> Please observe the normal rules for committing to this branch:
>
> * Before c
NOTICE:
I am now preparing for a bugfix release from branch branch_8_11
Please observe the normal rules for committing to this branch:
* Before committing to the branch, reply to this thread and argue
why the fix needs backporting and how long it will take.
* All issues accepted for backportin
Hello Praveen,
IIRC this jar is used only by Tika (Solr Cell) module which is disabled by
default. So, it's up to user to turn on this vulnerability.
On Mon, Jan 8, 2024 at 9:55 AM Praveen Kamath
wrote:
> Hey Team,
>
> Greetings for the day. This is Praveen from Acquia - on
Hey Team,
Greetings for the day. This is Praveen from Acquia - one of your Solr
customers.
We recently ran an ORCA scan on our solr instances and got to know of
several vulnerabilities in Lucene 8.11.2. I couldn't find any tickets
regarding vulnerability reported in bcprov-jdk15on-1.69.jar
Investingating
On Dec 3 2023, at 2:44 pm, David Smiley wrote:
> I updated the script accordingly and I still see the problem:
>
> https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/6008/console
> (https://link.getmailspring.com/link/af58603e-fb74-492a-8190-f5b8275db...@getmail
I updated the script accordingly and I still see the problem:
https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/6008/console
+ status=0
+ ./crave pull --extra-rsync-flags ' --ignore-missing-args'
'**/build/**/test/TEST-*.xml' '**/*.events' 'heapdump
ps or $mkdir -p heapdumps (depending on script's
> error handling more) before $crave pull
>
>
> On Thu, Nov 30, 2023 at 11:24 PM Yuvraaj Kelkar wrote:
>
> I just started a build with crave:
> crave run ./gradlew --console=plain check integrationTests
>
> And at
umps or $mkdir -p heapdumps (depending on script's
> > > error handling more) before $crave pull
> > >
> > >
> > > On Thu, Nov 30, 2023 at 11:24 PM Yuvraaj Kelkar > > (mailto:u...@crave.io)> wrote:
> > > > I just started a build with
or handling more) before $crave pull
>
>
> [image: Sent from Mailspring]
> On Thu, Nov 30, 2023 at 11:24 PM Yuvraaj Kelkar wrote:
>
> I just started a build with crave:
> crave run ./gradlew --console=plain check integrationTests
>
> And at the end of it, looked for the
ld with crave:
> > crave run ./gradlew --console=plain check integrationTests
> >
> > And at the end of it, looked for the patterns in the crave pull command:
> >
> > admin@171074329f9e:/tmp/src/solr$ find . -name '*.events'
> > admin@171074329f9e
ed for the patterns in the crave pull command:
>
> admin@171074329f9e:/tmp/src/solr$ find . -name '*.events'
> admin@171074329f9e:/tmp/src/solr$ find . -name 'hs_err_pid*'
> admin@171074329f9e:/tmp/src/solr$
> admin@171074329f9e:/tmp/src/solr$ ls -l heapdumps
> ls:
I just started a build with crave:
crave run ./gradlew --console=plain check integrationTests
And at the end of it, looked for the patterns in the crave pull command:
admin@171074329f9e:/tmp/src/solr$ find . -name '*.events'
admin@171074329f9e:/tmp/src/solr$ find . -name 'hs_
-*.xml' '**/*.events' 'heapdumps/**'
> > > '**/hs_err_pid*'
> > > Error: rsync: [sender] change_dir "/tmp/src/solr/heapdumps" failed: No
> > > such file or directory (2)
> > > rsync error: some files/attr
>>
>> + status=0
>> + ./crave pull '**/build/**/test/TEST-*.xml' '**/*.events' 'heapdumps/**'
>> '**/hs_err_pid*'
>> Error: rsync: [sender] change_dir "/tmp/src/solr/heapdumps" failed: No such
>> file or dir
#x27; '**/*.events' 'heapdumps/**'
> '**/hs_err_pid*'
> Error: rsync: [sender] change_dir "/tmp/src/solr/heapdumps" failed: No such
> file or directory (2)
> rsync error: some files/attrs were not transferred (see previous errors)
> (code 23) at main.c(
Hello
It's rather like a logical error in crave pull. How to work around it?
+ status=0
+ ./crave pull '**/build/**/test/TEST-*.xml' '**/*.events'
'heapdumps/**' '**/hs_err_pid*'
Error: rsync: [sender] change_dir "/tmp/src/solr/heapdumps"
Thanks Qizhi and Shawn for digging into this.
So yeah, I think when I worked on migrating us to using bin/solr post I didn’t
get ALL of the examples in the Ref Guide updated.
I’ve open https://issues.apache.org/jira/browse/SOLR-17068 and am going to try
and get the migration done.
Thanks
Hi Qizhi,
I am moving your question to the Solr users list.
Le sam. 4 nov. 2023, 01:58, Qizhi Zheng a
écrit :
> Hello,
>
>
>
> I am trying to run the Solr Tutorial Exercise 1 Index Techproducts Data in
> Windows 10. I typed the exact same command following it
Hello,
I am trying to run the Solr Tutorial Exercise 1 Index Techproducts Data in
Windows 10. I typed the exact same command following it link:
https://solr.apache.org/guide/solr/latest/getting-started/tutorial-techprodu
cts.html
java -jar -Dc=techproducts -Dauto example\exampledocs
uration (repo pointing at the commit that informs about project
> split
> : between Solr and Lucene). I've disabled the plan.
>
> This jenkins job stoped sending emails ~ March of 2021.
>
> There is a thread from March of 2022 where Smiley mentioned it
> didn't surv
: I'm not even sure how it's possible but this build seems to be using stale
: configuration (repo pointing at the commit that informs about project split
: between Solr and Lucene). I've disabled the plan.
This jenkins job stoped sending emails ~ March of 2021.
There is a th
I'm not even sure how it's possible but this build seems to be using stale
configuration (repo pointing at the commit that informs about project split
between Solr and Lucene). I've disabled the plan.
Dawid
On Fri, Nov 3, 2023 at 10:17 PM Apache Jenkins Server <
jenk...@builds
t; Jan
>
> 31. okt. 2023 kl. 10:24 skrev Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com>:
>
>
> Please vote for release candidate 1 for Lucene/Solr 8.11.3
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-sol
.
Not 100% sure if all three qualify as blockers either, but they all look
security related.
Jan
> 31. okt. 2023 kl. 10:24 skrev Ishan Chattopadhyaya
> :
>
>
> Please vote for release candidate 1 for Lucene/Solr 8.11.3
>
> The artifacts can be downloaded from:
> https
Please vote for release candidate 1 for Lucene/Solr 8.11.3
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.3-RC1-rev10d925469f3d4e66b6339b9e1c7d4d4afa4cf206
You can run the smoke tester directly with this command:
python3 -u dev-tools/scripts
ector (extending the SimpleCollector) [0]. this
introduced the second 'finish' call, one on Lucene side for the leaf
collectors and one on Solr side for completing the DelegatingCollector. the
new method fit so well with the existing method that I did not even see it
clashing. Renami
ene test case that reproduces this double
calling of finish()?
I'm sorry this change broke Solr. I remember that Solr had post-collection
hooks, which felt like another case for adding this new API, but I
overlooked that it could break Solr by introducing a clash given that Solr
uses Sim
Hi,
I am working on getting Solr upgraded to Lucene 9.8 [0] and I wanted to
raise visibility on an issue I ran into.
I believe PR#12380 [1] introduced a change that calls `finish()` on the
LeafCollector [2]. The trouble is on Solr side we have a few collectors
that extend SimpleCollector. (to be
Hi guys,
sorry for the spam but I wanted to let you know that tonight in Tokyo
there's going to be the first Lucene/Solr in-person free meetup after a
long time!
https://lnkd.in/eDCXjdiX
I am visiting Japan so it would be a pleasure to meet any member of the
community that's aro
+dev@solr
-dev@lucene to bcc
Hi Nemo,
The canonical location of our tags for the 8.x release line is
https://gitbox.apache.org/repos/asf?p=lucene-solr.git;a=tags
The tags for 9.x (and future) will all be at
https://gitbox.apache.org/repos/asf?p=solr.git;a=tags as you have found.
This is the
Hi,
It appears that recent 8.x Solr releases (post 8.8.1) haven't been
tagged on the Git repository[1]
Is this an intentional release process change? Seeing as how the 9.0.0
release was correctly tagged, could the missing releases be backtagged
with the correct dates? The list of unt
e result is:
>
> +1 6 (6 binding)
> 0 1
> -1 0
>
> This vote has PASSED
>
> On Mon, Jun 13, 2022 at 12:05 PM Mike Drob wrote:
>
>> Please vote for release candidate 2 for Lucene/Solr 8.11.2
>>
>> The artifacts can be downloaded from:
>>
&
It's been >72h since the vote was initiated and the result is:
+1 6 (6 binding)
0 1
-1 0
This vote has PASSED
On Mon, Jun 13, 2022 at 12:05 PM Mike Drob wrote:
> Please vote for release candidate 2 for Lucene/Solr 8.11.2
>
> The artifacts can be downloade
Test.basicTest
>>>
>>> On Tue, Jun 14, 2022 at 4:36 AM Jan Høydahl wrote:
>>> >
>>> > +1 (binding)
>>> >
>>> > SUCCESS! [1:19:45.192785]
>>> >
>>> > Jan
>>> >
>&
.apache.solr.cloud.LeaderVoteWaitTimeoutTest.basicTest
>>
>> On Tue, Jun 14, 2022 at 4:36 AM Jan Høydahl
>> wrote:
>> >
>> > +1 (binding)
>> >
>> > SUCCESS! [1:19:45.192785]
>> >
>> > Jan
>> >
>> >
; SUCCESS! [1:19:45.192785]
> >
> > Jan
> >
> > 13. jun. 2022 kl. 21:05 skrev Mike Drob :
> >
> > Please vote for release candidate 2 for Lucene/Solr 8.11.2
> >
> > The artifacts can be downloaded from:
> >
> https://dist.apache.org/repos/
>
> SUCCESS! [1:19:45.192785]
>
> Jan
>
> 13. jun. 2022 kl. 21:05 skrev Mike Drob :
>
> Please vote for release candidate 2 for Lucene/Solr 8.11.2
>
> The artifacts can be downloaded from:
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.2-RC2-rev17de
+1 (binding)
SUCCESS! [1:19:45.192785]
Jan
> 13. jun. 2022 kl. 21:05 skrev Mike Drob :
>
> Please vote for release candidate 2 for Lucene/Solr 8.11.2
>
> The artifacts can be downloaded from:
> https://dist.apache.org/repos/dist/dev/lucene/luce
+1
SUCCESS! [1:02:16.559513]
On Mon, Jun 13, 2022 at 12:07 PM Mike Drob wrote:
> Please vote for release candidate 2 for Lucene/Solr 8.11.2
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-
Please vote for release candidate 2 for Lucene/Solr 8.11.2
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.2-RC2-rev17dee71932c683e345508113523e764c3e4c80fa
You can run the smoke tester directly with this command:
python3 -u dev-tools/scripts
l respin and put up a new RC with the fix.
>
> On Sat, Jun 11, 2022 at 11:21 AM Houston Putman
> wrote:
>
>> +0
>>
>> SUCCESS! [1:02:38.547629]
>>
>> I saw this in the example logs during the smoketester:
>>
>>> ps: Invalid proces
the smoketester:
>
>> ps: Invalid process id: i��\r\001
>> Waiting up to 180 seconds to see Solr running on port 8983 [/]
>> Started Solr server on port 8983 (pid=16758). Happy searching!
>>
> This seems related to SOLR-16191
> <https://issues.apache.org/jira/b
+0
SUCCESS! [1:02:38.547629]
I saw this in the example logs during the smoketester:
> ps: Invalid process id: i��\r\001
> Waiting up to 180 seconds to see Solr running on port 8983 [/]
> Started Solr server on port 8983 (pid=16758). Happy searching!
>
This seems related to SOLR-
1 - 100 of 52778 matches
Mail list logo
