eagle-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wujinhu <...@git.apache.org>
Subject [GitHub] incubator-eagle pull request #684: [EAGLE-800] Use InterProcessMutex to sync...
Date Fri, 25 Nov 2016 05:49:37 GMT
Github user wujinhu commented on a diff in the pull request:

    https://github.com/apache/incubator-eagle/pull/684#discussion_r89567435
  
    --- Diff: eagle-jpm/eagle-jpm-util/src/main/java/org/apache/eagle/jpm/util/jobrecover/RunningJobManager.java
---
    @@ -49,12 +53,21 @@ private CuratorFramework newCurator(String zkQuorum, int zkSessionTimeoutMs,
int
             );
         }
     
    -    public RunningJobManager(String zkQuorum, int zkSessionTimeoutMs, int zkRetryTimes,
int zkRetryInterval, String zkRoot) {
    +    public RunningJobManager(String zkQuorum, int zkSessionTimeoutMs, int zkRetryTimes,
int zkRetryInterval, String zkRoot, String siteId) {
    --- End diff --
    
    I think pass the lock path to utility class directly will be better since utility class
does not need to know how to make the lock path.
    How to define the lock path is decided by applications


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message