[prev in list] [next in list] [prev in thread] [next in thread] 

List:       solr-user
Subject:    Re: SolR 9.3.0 embeddedn zookeeper on wildcard address [bug exists/resolved]
From:       Morten Bøgeskov <mb () dbc ! dk ! INVALID>
Date:       2023-08-23 12:10:21
Message-ID: DB8PR03MB58512E6A64B5C8A6978ED6E1B11CA () DB8PR03MB5851 ! eurprd03 ! prod ! outlook ! com
[Download RAW message or body]

[Attachment #2 (text/plain)]

Most likely - yes... Thank you Jan.

Now why didn't I see that, when I searched the bug reports. (and why can't I find it, \
when I have it in an adjacent tab?) ________________________________
From: Jan Høydahl <jan.asf@cominvent.com>
Sent: Wednesday, August 23, 2023 13:46
To: users@solr.apache.org <users@solr.apache.org>
Subject: Re: SolR 9.3.0 embeddedn zookeeper on wildcard address

[You don't often get email from jan.asf@cominvent.com. Learn why this is important at \
https://aka.ms/LearnAboutSenderIdentification ]

Perhaps you are affected by this https://issues.apache.org/jira/browse/SOLR-16926 \
which is recently fixed but not released?

Jan

> 23. aug. 2023 kl. 12:18 skrev Morten Bøgeskov <mb@dbc.dk.INVALID>:
> 
> Sorry I forgot to attach the log
> 
> ________________________________
> From: Morten Bøgeskov <mb@dbc.dk.INVALID>
> Sent: Wednesday, August 23, 2023 12:01
> To: users@solr.apache.org <users@solr.apache.org>
> Subject: SolR 9.3.0 embeddedn zookeeper on wildcard address
> 
> [You don't often get email from mb@dbc.dk.invalid. Learn why this is important at \
> https://aka.ms/LearnAboutSenderIdentification ] 
> Hello
> 
> I've previously (SolR 9.1) been using this approach, inside own test docker image, \
> that boils down to: 
> echo "clientPortAddress=0.0.0.0" >> server/solr/zoo.cfg
> ./bin/solr start -f -c
> 
> This allows other containers to connect to the zookeeper and update/query/stream \
> from the SolR during integration testing. 
> How ever what I see now is, if I go to \
> http://localhost:8983/solr/#/~cloud?view=zkstatus, is a message that says: 
> Status: red
> Errors:
> 
> *   Failed talking to Zookeeper null:9983
> 
> ZK connection string: 0.0.0.0:9983
> 
> My question is:
> Is that expected (now)?
> Did I miss some configuration change, that allows to set the zookeeper uri to \
> localhost:9983, and still start the embedded one? Is it no longer supported - i.e. \
> run your own container with a zookeeper? Tedious to fix all the tests, but ok. Or \
> is this actually a bug? 
> Yours
> Bøgeskov
> 
> The stacktrace in the SolR is:
> 
> Caused by: java.net.UnknownHostException: null
>       at \
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:229) ~[?:?] \
>       at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) \
> ~[?:?]       at java.net.Socket.connect(Socket.java:609) ~[?:?]
>       at java.net.Socket.connect(Socket.java:558) ~[?:?]
>       at java.net.Socket.<init>(Socket.java:454) ~[?:?]
>       at java.net.Socket.<init>(Socket.java:231) ~[?:?]
>       at \
> org.apache.solr.handler.admin.ZookeeperStatusHandler.getZkRawResponse(ZookeeperStatusHandler.java:336) \
> ~[?:?]       ... 54 more
> 



[prev in list] [next in list] [prev in thread] [next in thread]