GitHub user sijie opened a pull request:

    https://github.com/apache/incubator-distributedlog/pull/58

    DL-86: Improve handling of lock conflicts in zk session lock

    merge twitter's change from Sijie Guo.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sijie/incubator-distributedlog merge/DL-86

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-distributedlog/pull/58.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #58
    
----
commit 904b8986b46fc908cfd1a0ee05b35dce77d12f5c
Author: Jordan Bull <jb...@twitter.com>
Date:   2016-05-13T18:27:19Z

    when publishing per partition stats, also publish per stream stats
    
    RB_ID=820062

commit 00919605f1bfa3f3e0c8514dc63552df4eeb3cc2
Author: Jordan Bull <jb...@twitter.com>
Date:   2016-05-18T17:18:34Z

    use zero padded partition strings in stats
    
    RB_ID=833803

commit 7b46a9ac6bb5d520366069c244332347ef019e8e
Author: Sijie Guo <sij...@twitter.com>
Date:   2016-05-23T23:49:19Z

    Improve handling of lock conflicts in zk session lock
    
    - lock reacquire could happen in foreground and background thread. so use a 
semaphore to make sure there is only on e outstanding  acquire operation. and  
check if already hold lock before reacquire.
    - fix handling zk sibling znode logic. as the znode is sequential znode, 
the name would be different each time. so only comparing the client id and 
session id of the znodes
    
    RB_ID=833945

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to