distributedlog-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DL-17) Ledger allocator pool should be able to use hostname to distinguish write proxies
Date Tue, 27 Dec 2016 17:03:58 GMT

    [ https://issues.apache.org/jira/browse/DL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15780790#comment-15780790
] 

ASF GitHub Bot commented on DL-17:
----------------------------------

Github user asfgit closed the pull request at:

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


> 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)

Mime
View raw message