[
https://issues.apache.org/jira/browse/DL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782303#comment-15782303
]
Hudson commented on DL-17:
--------------------------
UNSTABLE: Integrated in Jenkins build distributedlog-nightly-build #170 (See
[https://builds.apache.org/job/distributedlog-nightly-build/170/])
DL-17: Ledger allocator pool should be able to use hostname to (sijieg: rev
58ba6f47c2e7b38a2a58330fb45afbcead8ecf27)
* (edit)
distributedlog-service/src/main/java/com/twitter/distributedlog/service/config/ServerConfiguration.java
* (add)
distributedlog-service/src/main/java/com/twitter/distributedlog/service/utils/ServerUtils.java
* (edit)
distributedlog-service/src/test/java/com/twitter/distributedlog/service/config/TestServerConfiguration.java
* (add)
distributedlog-service/src/test/java/com/twitter/distributedlog/service/utils/TestServerUtils.java
* (edit)
distributedlog-service/src/main/java/com/twitter/distributedlog/service/DistributedLogServiceImpl.java
> Ledger allocator pool should be able to use hostname to distinguish write
> proxies
> ---------------------------------------------------------------------------------
>
> Key: DL-17
> URL: https://issues.apache.org/jira/browse/DL-17
> Project: DistributedLog
> Issue Type: Task
> Components: distributedlog-service
> Reporter: Sijie Guo
> Assignee: Jay Juma
> Labels: help-wanted
> Fix For: 0.4.0
>
>
> Currently write proxy uses shard id to distinguish ledger allocators in the
> pool. Using shard id is very convenient if deploying using a scheduler like
> aurora, as scheduler usually be able to assign a unique shard id.
> However, for deployments not using aurora, it might make sense to use just
> hostname to identify the allocator used by a specific write proxy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
