You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Flavio Paiva Junqueira (JIRA)" <ji...@apache.org> on 2009/05/05 13:09:30 UTC

[jira] Commented: (ZOOKEEPER-383) Asynchronous version of createLedger()

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705990#action_12705990 ] 

Flavio Paiva Junqueira commented on ZOOKEEPER-383:
--------------------------------------------------

createLedger, openLedger, and closeLedger are operations that do not involve talking to bookies, so they don't go into the same pipeline as addEntry and readEntry operations. Instead, they are executed by the application thread when invoked. These operations do require talking to ZooKeeper, though. 

Making such operations asynchronous in the sense that a different thread executes the operation may require some restructuring. Perhaps what we can do is have ClientCBWorker executing the operation and calling back the application client. 

> Asynchronous version of createLedger()
> --------------------------------------
>
>                 Key: ZOOKEEPER-383
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-383
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: contrib-bookkeeper
>            Reporter: Utkarsh Srivastava
>            Assignee: Flavio Paiva Junqueira
>
> While there are async versions for read and write, there is no async version for creating a ledger. This can cause applications to have to change their whole thread design. 
> It should be easier and more consistent to add an async version of createLedger().

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