[
https://issues.apache.org/jira/browse/DL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769130#comment-15769130
]
ASF GitHub Bot commented on DL-17:
----------------------------------
GitHub user jayk-juma opened a pull request:
https://github.com/apache/incubator-distributedlog/pull/86
DL-17: Ledger allocator pool should be able to use hostname to distinguish
write proxies
…guish write proxies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jayk-juma/incubator-distributedlog
jay/use_hostname_for_ledger_allocation
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-distributedlog/pull/86.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 #86
----
commit 9b86ee41c94e9a9965843fb66205cf7edeaa6643
Author: Jay Juma <jayk.j...@gmail.com>
Date: 2016-12-22T05:39:52Z
DL-17: Ledger allocator pool should be able to use hostname to distinguish
write proxies
----
> 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)
