The errors are unusual but the znode_count is normal
On Fri, Jan 28, 2022 at 9:12 PM Reej Nayagam wrote:
>
> Hi All,
>
> As suggested from the group I tried using this api call
> /sol/admin/zookeeper/status, to get the zk status
> whenever i try this in my browser one time I get the status as 0
Hi All,
As suggested from the group I tried using this api call
/sol/admin/zookeeper/status, to get the zk status
whenever i try this in my browser one time I get the status as 0 and get
the zk ensemble details, after a while when I try i get
status : 500
error: msg: "Java.net.SocketException:con
Hi Vinay,
We are connecting using cloudsolrclient passing the zk host, so if zk is
down, the connection to solr also won't happen.
*Thanks,*
*Reej*
On Thu, Jan 27, 2022 at 12:35 PM Vinay Rajput
wrote:
> It also looks like from your requirement that you want to disable solr
> search and activa
It also looks like from your requirement that you want to disable solr
search and activate DB search in case of zookeeper cluster failure.
That is NOT needed. Solr search is not impacted when zk cluster is down,
only indexing is impacted. We have had a situation when our all zk nodes
were down for
You can check the status of each Zookeeper node with the “ruok” command.
This is one of the “four lettter words” admin commands.
https://zookeeper.apache.org/doc/r3.4.8/zookeeperAdmin.html#sc_zkCommands
This is how it works from a command line.
$ echo ruok | nc zoo-shared-1.test.search.cheggnet.
Thank you Shawn, I will try this way and see if it helps.
*Thanks,*
*Reej*
On Wed, Jan 26, 2022 at 10:59 PM Shawn Heisey wrote:
> On 1/26/22 06:53, Reej Nayagam wrote:
> > The scenario is solr servers are up, but majority of the zk is down,
> > so we need to tell the issue is with the zookeepe
Thanks Matthew, got some idea now.
Either this way or with Shawn's approach of passing zkconnection timeout
will workout for me
*Thanks,*
*Reej*
On Wed, Jan 26, 2022 at 10:37 PM matthew sporleder
wrote:
> Check this out:
> curl 'localhost:8983/solr/admin/zookeeper/status'
>
> On Wed, Jan 26,
On 1/26/22 06:53, Reej Nayagam wrote:
The scenario is solr servers are up, but majority of the zk is down,
so we need to tell the issue is with the zookeeper. I don’t find a way on
how to identify the zookeeper status without waiting for the timeout to
happen after 30 seconds.
I think the issue
Check this out:
curl 'localhost:8983/solr/admin/zookeeper/status'
On Wed, Jan 26, 2022 at 8:54 AM Reej Nayagam wrote:
>
> The scenario is solr servers are up, but majority of the zk is down,
> so we need to tell the issue is with the zookeeper. I don’t find a way on
> how to identify the zookeepe
The scenario is solr servers are up, but majority of the zk is down,
so we need to tell the issue is with the zookeeper. I don’t find a way on
how to identify the zookeeper status without waiting for the timeout to
happen after 30 seconds.
On Wed, 26 Jan 2022 at 9:39 PM, matthew sporleder
wrote:
I don't understand your approach --
For checking solr health I would probably use the ping endpoint or a
very fast query with a low timeout (q=*:*&timeAllowed=100&rows=0).
IIRC zookeeper health (as seen by solr) is in the CLUSTERSTATUS admin
api command? It's somewhere near there if not in CLUST
Hi All,
I need to handle zk failure and so monitoring the zk ensemble, and if the
majority of the zk fails we'll activate the HA to point to a DB search.
So to check if each of the zk is alive , we are connecting as below,
*zkClient = solrZkClient(zkaddress,1),*
*return zkclient.getSolrZooke
12 matches
Mail list logo
