distributedlog-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DL-39) Allow using distributed log uri for resolving the write proxy addresses
Date Thu, 08 Sep 2016 07:32:21 GMT

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

Hudson commented on DL-39:
--------------------------

UNSTABLE: Integrated in Jenkins build distributedlog-nightly-build #50 (See [https://builds.apache.org/job/distributedlog-nightly-build/50/])
DL-39: Use a distributedlog uri to configure write proxy routing address (sijieg: rev 05a8daa2aa468fe82f6ca919f7d93f0bab86c522)
* (edit) distributedlog-benchmark/src/main/java/com/twitter/distributedlog/benchmark/Benchmarker.java
* (edit) distributedlog-client/src/main/java/com/twitter/distributedlog/service/DistributedLogClientBuilder.java
* (edit) distributedlog-benchmark/bin/dbench
* (edit) docs/operations/deployment.rst
* (edit) distributedlog-benchmark/src/main/java/com/twitter/distributedlog/benchmark/ReaderWorker.java
* (edit) distributedlog-benchmark/src/main/java/com/twitter/distributedlog/benchmark/WriterWorker.java
* (edit) distributedlog-benchmark/conf/dlogenv.sh


> Allow using distributed log uri for resolving the write proxy addresses
> -----------------------------------------------------------------------
>
>                 Key: DL-39
>                 URL: https://issues.apache.org/jira/browse/DL-39
>             Project: DistributedLog
>          Issue Type: Improvement
>          Components: distributedlog-client
>            Reporter: Jon Derrick
>             Fix For: 0.4.0
>
>
> it is a bit inconvenient to configure the finagle name str for building clients. I have
to construct myself by parsing the zkservers and path from the distributed log uri. it would
be good that the client builder can accept the uri as resolver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message