Hi,
I'm new to Solr and I'm tasked to upgrade our Solr 8.11.3 installation to
Solr 9.6.1.
I'm running into some trouble with the create collection command when it's
sent to a Solr 9.6.1 node with Solr 8.11.3 running as overseers.
The command in Java is
CollectionAdminRequest.createCollection(c
rialized java
> objects and so you cannot create collections while in the middle of a major
> upgrade.
> I'd pause such cluster events during the rolling upgrade so that the
> Overseer queues are empty once the overseer node is upgraded.
>
> Jan
>
> > 16. okt. 2024 kl. 04:
;:"ftest-collection_1.2",
"params.collection.configName":"test-collection",
"params.createNodeSet":"EMPTY",
"params.numShards":"2",
"params.router.name":"compositeId",
"params.nrtReplicas":"1",
"par
Hi,
We are seeing some weird issues with the Overseer ID which causes some
overseer election problems in our cluster.
Recently we have noticed that one of our Solr 8 clusters is having trouble
electing dedicated overseer hosts as leader. After some investigation, we
noticed that we are having "ne
can be reset, it is decided by this
> method. Solr code should be fixed to do a better job of parsing that
> string.
>
> Ilan
>
>
> On Tue, Dec 3, 2024 at 6:56 PM Patrick Lok
> wrote:
> >
> > That's what I think is happening too. The problem is the code is no
s wouldn’t it be a long
> wrapping around into negative territory?
>
> On Tue 3 Dec 2024 at 02:55, Patrick Lok .invalid>
> wrote:
>
> > Hi,
> >
> > We are seeing some weird issues with the Overseer ID which causes some
> > overseer election problems in our clus
Never mind, I created a JIRA account and filed the tickets.
https://issues.apache.org/jira/browse/ZOOKEEPER-4904
https://issues.apache.org/jira/browse/SOLR-17694
On Fri, Mar 7, 2025 at 2:02 PM Patrick Lok
wrote:
> Hi David and Ilan
>
> I don't have a JIRA account, could one
possible solution ideas.
>
> On Wed, Dec 18, 2024 at 12:27 PM Patrick Lok
> wrote:
>
> > Hi Ilan, thank you so much for the pointers! That's exactly the problem.
> We
> > updated our system to wrap the ZK server ID at 127, instead of 256, and
> > that
