You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Henry Robinson (JIRA)" <ji...@apache.org> on 2009/10/07 00:02:31 UTC

[jira] Updated: (ZOOKEEPER-541) zkpython limited to 256 handles

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henry Robinson updated ZOOKEEPER-541:
-------------------------------------

    Attachment: ZOOKEEPER-541.patch

This patch ups the limit of concurrently active connections to 32768, and allocates these handles dynamically in increasing powers of two.

Handles are re-used when they are correctly closed. This involves an O(n) scan of the handle array, but I think this is preferable to the overhead of managing linked lists with O(1) lookup. 

Tests are included.



> zkpython limited to 256 handles
> -------------------------------
>
>                 Key: ZOOKEEPER-541
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-541
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: contrib-bindings
>    Affects Versions: 3.2.1
>            Reporter: Patrick Hunt
>            Assignee: Henry Robinson
>             Fix For: 3.3.0
>
>         Attachments: ZOOKEEPER-541.patch
>
>
> zkpython is currently limited to a max of 256 total handles - not 256 open handles, but rather 256 total handles created
> over the lifetime of the python application.
> In general this isn't a real issue, however in the case of a long lived application which polls the cluster periodically (closing
> the session btw calls) this is an issue.
> it would be great if the slots could be reused? or perhaps a more complex structure, such as a linked list, which would allow
> dynamic growth/shrinkage of the handle list.
> Also see ZOOKEEPER-540

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.