On Thu, Feb 4, 2021 at 12:23 PM Tomás Fernández Löbbe
wrote:
> The point I was trying to make is that, having a single configset loading
> from both, local and zk may be confusing for the user and cause issues that
> may be difficult to track: Which file is Solr really reading right now? is
> it
And I continue to struggle with the python3 command:
python3 -u dev-tools/scripts/smokeTestRelease.py \
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.8.1-RC2-rev64f3b496bfee762a9d2dbff40700f457f4464dfe
On Tue, Feb 16, 2021 at 7:41 PM Timothy Potter wrote:
>
> Please vote for
Please vote for release candidate 2 for Lucene/Solr 8.8.1
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.8.1-RC2-rev64f3b496bfee762a9d2dbff40700f457f4464dfe
You can run the smoke tester directly with this command:
python3 -u
Limiting open connections is not the same as rate limiting. Open connections is
a count of the requests being processed by a node. When the load balancer gets
a new request and all current connections are waiting for a response, a new
connection is opened.
If the requests are all the same
I'm going to try to fix SOLR-15135 and then kick-off RC2 later today.
If you're in the middle of the RC1 smoke test, it's still valuable to let
it finish, otherwise, please hold off on testing RC1
Cheers,
Tim
On Tue, Feb 16, 2021 at 10:53 AM Timothy Potter
wrote:
> Ha! I pulled in Ishan's
https://issues.apache.org/jira/browse/SOLR-15149#
: Date: Tue, 16 Feb 2021 17:55:17 + (UTC)
: From: Policeman Jenkins Server
: Reply-To: dev@lucene.apache.org
: To: bui...@lucene.apache.org
: Subject: [JENKINS] Lucene-Solr-8.x-Linux (64bit/jdk-11.0.6) - Build # 5837 -
: Still Unstable!
Ha! I pulled in Ishan's fixes for 15138 and now AutoscalingHistoryHandlerTest
behaves the same as in 8.7! Beasted 10 out of 10 passed, so
no @BadApple'ing needed ;-)
On Tue, Feb 16, 2021 at 10:29 AM Anshum Gupta
wrote:
> Yes, doing a single 8.8.2 release that has all the fixes, especially as we
Hello everyone,
Last year the Apache Lucene committers voted to propose the spinning off
and creation of Solr as an Apache TLP (Top Level Project)[1]
The PMC has submitted an ASF board resolution, to be reviewed during the
upcoming board meeting on Wednesday, Feb 17 2021.
The Lucene PMC also
Yes, doing a single 8.8.2 release that has all the fixes, especially as we
have the fix already is much better for the users.
Thanks for your patience, Tim :)
On Tue, Feb 16, 2021 at 9:05 AM Timothy Potter wrote:
> @Ishan ~ Can you look at the question Mike raised about
>
@Ishan ~ Can you look at the question Mike raised about
https://issues.apache.org/jira/browse/SOLR-15135 please?
So the AutoscalingHistoryHandlerTest has a number of hard-coded wait times
in it. While I can appreciate the need for waiting to see state changes
occur, tests like this aren't great
Walter, it sounds like you were doing rate limiting, just in a different
way that is more dynamic than a simple (yet fiddly) constant?
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Sun, Feb 14, 2021 at 2:54 PM Walter Underwood
wrote:
> Rate
> Shoving such a component into lucene-solr repo makes no sense, given its
> branching strategy is based on master / branch_8x
I get how this could cause issues - I def hadn't thought much about
multi-version support and branching. But I don't think moving plugins
to a separate repo solves that
Sounds good, Tim. I've ported the fix to the release branch. Just ran the
tests to make sure it works fine.
Thanks for the extra work you'll have to do (RC2) in order to save me
future work (8.8.2). Really owe you one!
> Are there other fixes you're aware of that are slated for 8.8.2 @Ishan
I'm beasting AutoscalingHistoryHandlerTest locally now, I haven't seen that
one fail on my side yet.
As far as respin 8.8.1 RC, it's not a problem for me and I prefer that to
doing an 8.8.2 soon after 8.8.1 comes out. Are there other fixes you're
aware of that are slated for 8.8.2 @Ishan
On Tue, Feb 16, 2021 at 8:38 AM Eric Pugh
wrote:
> Testing across multiple versions is always very difficult ;-). I recently
> saw this very interesting approach to using our Dockerized Solr’s to test a
> component against a number of previous versions of Solr.
>
Hmm, I got a failure on
org.apache.solr.handler.admin.AutoscalingHistoryHandlerTest.testHistory,
but it did not reproduce (tried twice). Would that possibly also be
addressed by those fixes?
On Tue, Feb 16, 2021 at 7:38 AM Ishan Chattopadhyaya
wrote:
>
> > The failure seems to be because of a
Testing across multiple versions is always very difficult ;-). I recently saw
this very interesting approach to using our Dockerized Solr’s to test a
component against a number of previous versions of Solr.
https://github.com/querqy/querqy/pull/147. I’m hopeful it could be a model for
other
Imagine a component that wants to have its own release cadence. Say, a 1.x
line of the component that supports certain features (across Solr 6x to 9x)
and 2.x line that supports certain other features (which are a big upgrade
from previous 1.x). A Solr UI can be a good example, where say 1.x uses
> The failure seems to be because of a timeout during collection
> creation
Thanks for digging in. Seems like that is the exact class of fix that we
did for SOLR-15138 and are planning for 8.8.2. Shall we backport that fix
to the release branch now (for RC2 or 8.8.2)?
> My h/w is really fast and
Curious, the smoke tester passed for me on the first try:
SUCCESS! [0:44:29.979512]
Mike McCandless
http://blog.mikemccandless.com
On Sun, Feb 14, 2021 at 11:26 AM Timothy Potter
wrote:
> Please vote for release candidate 1 for Lucene/Solr 8.8.1
>
>
> The artifacts can be downloaded from:
> separate repo can be used to test against many Solr versions. Imagine a
> component that works across Solr versions 6x through 9x from day one. I can't
> imagine such a component being part of the lucene-solr repo itself.
It'll be great to test contrib's on multiple Solr versions, but I
can't
21 matches
Mail list logo
