@Anshum Gupta
The failure seems to be because of a timeout during collection
creation. My h/w is really fast and beefy and may be that's why it
doesn't get reproduced. We have sped up collection creation
significantly in branch_8x. Can you please re run the same tests on 8x
branch please? If it's
Interesting.
I didn't use the flag, but just changed the code to comment out the
randomization from SolrCloudTestCase.java.
I think Tim did the same, so I'm not sure if that's the difference or if
there's a difference of environment.
On Mon, Feb 15, 2021 at 9:48 PM Ishan Chattopadhyaya <
I did another round of beast, this time setting that flag to true (as
suggested to me by Noble).
ant -Duse.perreplica=true -Dtests.dups=1 -Dtests.iters=5 -Dbeast.iters=5
-Dtestcase=SolrCloudReportersTest beast
-beast:
[beaster] Beast round 1 results:
Ishan/Noble, thanks for taking a look at this.
I only just started to look at the cause, so I'm sure you have better
context on why this is failing and if it makes sense to still release with
this issue.
FYI, I was able to get a successful smoke test run finally, but the fact
that it took me
I think embracing Docker is how we can identify if a plugin works in
multiple versions of Solr. The setup of such a test would start Solr via
Docker and install the plugin into a Solr server using the package
manager. The test code itself would interact with Solr purely via
SolrClient. This
I tried light beasting the test on branch_8_8:
ant -Dtests.dups=1 -Dtests.iters=5 -Dbeast.iters=5
-Dtestcase=SolrCloudReportersTest beast
No failures.
[beaster] Beast round 1 results:
/home/ishan/code/lucene-solr/solr/build/solr-core/test/1
[beaster] Beast round 2 results:
@Anshum Gupta
I think we should not hold up the release of RC1 because of that failure.
This is a new feature and new features take time to get hardened.
However, We can investigate and fix this anyway.
If required, we can do a 8.8.3
On Tue, Feb 16, 2021 at 3:10 PM Ishan Chattopadhyaya
Here's my +1 for the RC1.
SUCCESS! [0:42:38.936787]
On Tue, Feb 16, 2021 at 9:02 AM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> Per Replica States is a new feature introduced in 8.8.0. It will require a
> critical bugfix (SOLR-15138) immediately after 8.8.1 (in a 8.8.2 release).
Per Replica States is a new feature introduced in 8.8.0. It will require a
critical bugfix (SOLR-15138) immediately after 8.8.1 (in a 8.8.2 release).
If this issue is confirmed to be PRS related, then I think we should
continue with this release and fix PRS in 8.8.2.
However, if you still want us
Surprising. I'll take a look.
On Tue, 16 Feb, 2021, 7:29 am Anshum Gupta, wrote:
> I've unsuccessfully tried getting the smoketester to pass and have had 6
> fails so far.
>
> At this point it seems like SolrCloudReporterTest and
> AutoscalingHistoryTest tests are failing pretty consistently
I've unsuccessfully tried getting the smoketester to pass and have had 6
fails so far.
At this point it seems like SolrCloudReporterTest and
AutoscalingHistoryTest tests are failing pretty consistently for me.
The former is a new failure, and seems to be caused by the
USE_PER_REPLICA_STATE
Hi folks-
I'm reaching out to understand if there's been any past exploration into
alternative concurrent DrillSideways execution approaches. My understanding
of the current approach is that we're achieving some concurrency by using a
CollectorManager with IndexSearcher (allowing parallel
Hi,
> One important reason why separate repo for solr-extras is a good idea, as
> opposed to conrib modules, is that 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
Hoss,
One important reason why separate repo for solr-extras is a good idea, as
opposed to conrib modules, is that 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
14 matches
Mail list logo
