You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/11/25 14:08:10 UTC
[jira] [Commented] (EAGLE-7) expose storm config as individual
eagle topology config
[ https://issues.apache.org/jira/browse/EAGLE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026728#comment-15026728 ]
ASF GitHub Bot commented on EAGLE-7:
------------------------------------
Github user qingwen220 closed the pull request at:
https://github.com/apache/incubator-eagle/pull/5
> expose storm config as individual eagle topology config
> -------------------------------------------------------
>
> Key: EAGLE-7
> URL: https://issues.apache.org/jira/browse/EAGLE-7
> Project: Eagle
> Issue Type: Improvement
> Environment: production linux
> Reporter: Edward Zhang
> Assignee: Zhao, Qingwen
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Storm has many configurations which can be configured through storm.yaml, and those configurations are actually can be per topology. Eagle should have a capability to expose all the configurations through Eagle configuration. Some examples are
> topology.acker.executors: 2
> topology.tasks: 8
> topology.max.spout.pending: 1000
> topology.executor.receive.buffer.size: 16384
> topology.executor.send.buffer.size: 16384
> Today we only have parallelism of bolt/spout can be configured through eagle configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)