I like your suggestion David on the CLI supporting configset directly. I’m
sort of waiting till the V2 api for putting configsets is done. According to
the Solr v2 API Proposed Changes spreadsheet, while there is a V2 api, it
hasn’t been given the “restful/jax-rs/exposed in solrj” treatment
+1 SUCCESS! [0:51:20.054401]
BTW the first run failed due to a test. I ran the repro line and it
did reproduce ... but just once and not again. Didn't on main.
Didn't see in build failures (tracked via fucit.org) but saw once in
Gradle Enterprise albeit in that build 50 tests failed:
I suppose direct ZK has an advantage of not requiring that Solr is
running yet. But maybe that's moot. I do think it would make sense
to have CLI options for configset upload that use Solr's API and don't
refer to ZK. Broadly, this is the direction we're going in; ZK is
more of an internal
Zookeeper file size limits are probably the most common failure. I had to mess
around a lot with our suggestion dictionary to get it to upload.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Feb 11, 2024, at 11:25 AM, Eric Pugh
> wrote:
>
> Ah..
Ah.. yeah, I can’t speak to Solr 6.x! In 9x at least you could use the
configset API to deploy configs and avoid the direct ZK interaction.
It would be interesting to explore if the process of deploying a configset is
risky, has a high chance of things failing, then how do we account for that
The was deploying configs with Jenkins on Solr 6.x. Maybe the APIs were there,
but I didn't know about them.
Rebuilding the suggester did need external help, since that needs to be done
separately on each node.
I think working directly with Zookeeper is less risky. If there is any issue
with
The grade task also does not require installed solr... but still leverages
the solr classes (to avoid the very risk Eric is talking about in his reply)
https://github.com/nsoft/solr-gradle/blob/master/src/main/groovy/com/needhamsoftware/gradle/solr/SolrGradlePlugin.groovy#L38
granted it probably
Could you share more about “update Solr remotely” that you were doing? Are we
missing some APIs that would have made whatever you had to do require ZK direct
access?
While it’s cool that we can impact Solr via hacking around in ZK, it also seems
like an approach fraught with risk!
> On
I wanted something that didn’t require installing Solr locally in order to
update Solr remotely, so I didn’t use the provided zk commands. I wrote some
Python to dig the Zookeeper addresses out of clusterstatus (I think) then
uploaded directly to Zookeeper with the Python kazoo package.
The
I pretty much always use zk upconfig, which also works for overwriting
existing. I certainly tell my clients to use apis from the ref guide for
such operations, but zk upconfig certainly counts as one. Mostly I tell
them that they should only break out things like
https://github.com/rgs1/zk_shell
Hi all.. I was playing around with a cluster and wanted to upload a configset
into Solr….
I ran bin/solr and noticed a bin/solr config -h command, but it just lets me
tweak a config. Then I ran bin/solr create -h and it appears to let me upload
a configset, but I have to create the
11 matches
Mail list logo
