You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/10/17 00:33:01 UTC

[jira] [Work logged] (CURATOR-619) Replace OutstandingOps with JDK bundled Phaser

     [ https://issues.apache.org/jira/browse/CURATOR-619?focusedWorklogId=665775&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-665775 ]

ASF GitHub Bot logged work on CURATOR-619:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Oct/21 00:32
            Start Date: 17/Oct/21 00:32
    Worklog Time Spent: 10m 
      Work Description: eolivelli commented on pull request #365:
URL: https://github.com/apache/curator/pull/365#issuecomment-944901878






-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@curator.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 665775)
    Remaining Estimate: 0h
            Time Spent: 10m

> Replace OutstandingOps with JDK bundled Phaser
> ----------------------------------------------
>
>                 Key: CURATOR-619
>                 URL: https://issues.apache.org/jira/browse/CURATOR-619
>             Project: Apache Curator
>          Issue Type: Improvement
>            Reporter: Zili Chen
>            Assignee: Zili Chen
>            Priority: Minor
>             Fix For: 5.2.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Back to the day we implemented CuratorCache, there is an outstanding discussion about OutstandingOps can be replaced with JDK bundled Phaser class so that we don't have to implement and maintain our own.
> See also [https://github.com/apache/curator/pull/335#discussion_r399591042]
> This is the very issue to follow this conversation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)