-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with KazooTimeout #593
Comments
I am facing the same issue. It's further giving an OS error stating "too many files open" |
Have you confirmed you still experience the same issue with the latest
release?
There were fixed around timeouts in 2.7.x releases
Cheers
…On Tue, Aug 4, 2020 at 8:17 AM Deepa12 ***@***.***> wrote:
netan-porwal Did you find any solution to the issue? I am also getting the
same error.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#593 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIFTHXVXOYAVIPEDXVNYK3R6736BANCNFSM4LCP2FMQ>
.
--
Charles-Henri de Boysson
|
Had checked pysolr's internal code for this. It worked fine for me by closing the zookeeper object which is created in class Zookeeper in pyslor.py file. In the documentation it says the following: ** For SolrCloud mode, initialize your Solr like this:zookeeper = pysolr.ZooKeeper("zkhost1:2181,zkhost2:2181,zkhost3:2181") Try using this after creating the above object. If you check kazoo's documentation, it says to close the created kazoo session to free any resources held by the client. |
I have an issue where Kazoo client timesout. I'm using Kazoo through a library called pysolr.
Here's a link to the source code line number:
https://github.com/django-haystack/pysolr/blob/cbb68d3905cf2aa7dc9b3100dd9ec959e10add18/pysolr.py#L1509
I am using default settings but I've also tried a timeout=12 (less than the zk.start() timeout just to test), and I'm still getting the problem.
It's possible my host has intermittent connection issues but I don't see why the client won't handle it gracefully and just reconnect automatically like it implies in the "delay", "retry" parameters. Why does it just crash and stop trying?
I'm using Kazoo 2.6.1
The text was updated successfully, but these errors were encountered: