[
https://issues.apache.org/jira/browse/SOLR-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14719301#comment-14719301
]
Mark Miller commented on SOLR-7789:
-----------------------------------
I just hit one of those fails on a normal 'ant test' run. I think we may have
to raise this 180 second timeout to be something that is a little more hearty.
{noformat}
[junit4] FAILURE 181s J1 | TestConfigSetsAPIExclusivity.testAPIExclusivity
<<<
[junit4] > Throwable #1: java.lang.AssertionError: Unexpected exception:
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
from server at http://127.0.0.1:57409/solr: create the configset time out:180s
expected:<0> but was:<2>
[junit4] > at
__randomizedtesting.SeedInfo.seed([36DBA95D885A778C:4BAEB0A6D1FECEC5]:0)
[junit4] > at
org.apache.solr.cloud.TestConfigSetsAPIExclusivity.testAPIExclusivity(TestConfigSetsAPIExclusivity.java:95)
[junit4] > at java.lang.Thread.run(Thread.java:745)
[junit4] 2> 361809 INFO
(SUITE-TestConfigSetsAPIExclusivity-seed#[36DBA95D885A778C]-worker) [ ]
o.a.s.SolrTestCaseJ4 ###deleteCore
{noformat}
{noformat}
> Introduce a ConfigSet management API
> ------------------------------------
>
> Key: SOLR-7789
> URL: https://issues.apache.org/jira/browse/SOLR-7789
> Project: Solr
> Issue Type: New Feature
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Fix For: Trunk, 5.4
>
> Attachments: SOLR-7789.patch, SOLR-7789.patch, SOLR-7789.patch,
> SOLR-7789.patch, SOLR-7789.patch
>
>
> SOLR-5955 describes a feature to automatically create a ConfigSet, based on
> another one, from a collection API call (i.e. one step collection creation).
> Discussion there yielded SOLR-7742, Immutable ConfigSet support. To close
> the loop, we need support for a ConfigSet management API.
> The simplest ConfigSet API could have one operation:
> create a new config set, based on an existing one, possible modifying the
> ConfigSet properties. Note you need to be able to modify the ConfigSet
> properties at creation time because otherwise Immutable could not be changed.
> Another logical operation to support is ConfigSet deletion; that may be more
> complicated to implement than creation because you need to handle the case
> where a collection is already using the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
