[jira] [Commented] (STORM-1632) Disable event logging by default

[ https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227704#comment-15227704 ] ASF GitHub Bot commented on STORM-1632: --- Github user arunmahadevan commented on the pull request:

[GitHub] storm pull request: STORM-1632 Disable event logging by default

Github user arunmahadevan commented on the pull request: https://github.com/apache/storm/pull/1217#issuecomment-206117168 @roshannaik yes, it will make the behavior consistent with "ackers". You may also want to update the tooltip. Since this PR is already merged, you may have to

[jira] [Commented] (STORM-1687) Divide by zero exception in stats

[ https://issues.apache.org/jira/browse/STORM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227656#comment-15227656 ] ASF GitHub Bot commented on STORM-1687: --- Github user unsleepy22 commented on the pull request:

[GitHub] storm pull request: [STORM-1687] divide by zero in StatsUtil

Github user unsleepy22 commented on the pull request: https://github.com/apache/storm/pull/1312#issuecomment-206103981 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[jira] [Commented] (STORM-1688) provide ParallismKillWorkerManager to shutdown workers in parallel

[ https://issues.apache.org/jira/browse/STORM-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227613#comment-15227613 ] John Fang commented on STORM-1688: -- [~caofangkun] You can refer to jstorm, which shutdown workers in

[jira] [Created] (STORM-1688) provide ParallismKillWorkerManager to shutdown workers in parallel

caofangkun created STORM-1688: - Summary: provide ParallismKillWorkerManager to shutdown workers in parallel Key: STORM-1688 URL: https://issues.apache.org/jira/browse/STORM-1688 Project: Apache Storm

[jira] [Commented] (STORM-1687) Divide by zero exception in stats

[ https://issues.apache.org/jira/browse/STORM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227549#comment-15227549 ] Jungtaek Lim commented on STORM-1687: - It depends on the priority of the issue. If priority of the

when can i change topology.max.spout.pending ?

First Thanks in advance for any help 1- i want to get what is the purpose of topology.max.spout.pending in the trident topology 2- when can i increase or decrease value of topology.max.spout.pending ? or wat are conditions that make me increade value of topology.max.spout.pending or decrease it

[jira] [Comment Edited] (STORM-1687) Divide by zero exception in stats

[ https://issues.apache.org/jira/browse/STORM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227517#comment-15227517 ] Zhuo Liu edited comment on STORM-1687 at 4/6/16 1:31 AM: - Just found that rc2 is

[jira] [Comment Edited] (STORM-1687) Divide by zero exception in stats

[ https://issues.apache.org/jira/browse/STORM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227517#comment-15227517 ] Zhuo Liu edited comment on STORM-1687 at 4/6/16 1:29 AM: - Just found that RC2 is

[jira] [Commented] (STORM-1687) Divide by zero exception in stats

[ https://issues.apache.org/jira/browse/STORM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227517#comment-15227517 ] Zhuo Liu commented on STORM-1687: - Just found that RC2 is already out, do we think we should add this bug

[jira] [Commented] (STORM-1687) Divide by zero exception in stats

[ https://issues.apache.org/jira/browse/STORM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227499#comment-15227499 ] Jungtaek Lim commented on STORM-1687: - [~zhuoliu] You added this issue to the epic. Does it mean that

[jira] [Commented] (STORM-1687) Divide by zero exception in stats

[ https://issues.apache.org/jira/browse/STORM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227487#comment-15227487 ] ASF GitHub Bot commented on STORM-1687: --- GitHub user zhuoliu opened a pull request:

[GitHub] storm pull request: [STORM-1687] divide by zero in StatsUtil

GitHub user zhuoliu opened a pull request: https://github.com/apache/storm/pull/1312 [STORM-1687] divide by zero in StatsUtil uptime sometimes equals to zero which causes divide exception. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] storm pull request: [STORM-1687]-1.x divide by zero in stats

GitHub user zhuoliu opened a pull request: https://github.com/apache/storm/pull/1311 [STORM-1687]-1.x divide by zero in stats This fixes the "divide by zero" error in stats/compute-agg-capacity. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (STORM-1687) Divide by zero exception in stats

[ https://issues.apache.org/jira/browse/STORM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227478#comment-15227478 ] ASF GitHub Bot commented on STORM-1687: --- GitHub user zhuoliu opened a pull request:

[jira] [Updated] (STORM-1580) Secure hdfs spout failed

[ https://issues.apache.org/jira/browse/STORM-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik updated STORM-1580: --- Attachment: HdfsSpoutTopology.java Sorry for the delayed update... kept getting pulled into other

[jira] [Updated] (STORM-1687) Divide by zero exception in stats

[ https://issues.apache.org/jira/browse/STORM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhuo Liu updated STORM-1687: Description: Since uptime can be 0, this will cause ArithmeticException: Divide by zero in

[jira] [Created] (STORM-1687) Divide by zero exception in stats

Zhuo Liu created STORM-1687: --- Summary: Divide by zero exception in stats Key: STORM-1687 URL: https://issues.apache.org/jira/browse/STORM-1687 Project: Apache Storm Issue Type: Bug

[jira] [Commented] (STORM-1632) Disable event logging by default

[ https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227134#comment-15227134 ] ASF GitHub Bot commented on STORM-1632: --- Github user roshannaik commented on the pull request:

[GitHub] storm pull request: STORM-1632 Disable event logging by default

Github user roshannaik commented on the pull request: https://github.com/apache/storm/pull/1217#issuecomment-205985587 On further thought... i feel it maybe ok to just remove the loggersTotal != null check here. Shall I just update this PR ? --- If your project is set up for it,

Re: [VOTE] Release Apache Storm 1.0.0 (rc2)

+1 (binding) - Verified build from source archive with `mvn clean install -P all-tests` - Checked LICENSE and NOTICE files - Deployed to a small cluster and tested a variety of topologies. -Taylor > On Apr 5, 2016, at 2:38 PM, P. Taylor Goetz wrote: > > This is a call to

[GitHub] storm pull request: [Storm 1683] ui viz uncheck sys streams

Github user d2r commented on the pull request: https://github.com/apache/storm/pull/1308#issuecomment-205963567 jdk7 core travis [error](https://travis-ci.org/apache/storm/jobs/120694897#L872) seems unrelated to ui. --- If your project is set up for it, you can reply to this email

[jira] [Commented] (STORM-1632) Disable event logging by default

[ https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226981#comment-15226981 ] ASF GitHub Bot commented on STORM-1632: --- Github user roshannaik commented on a diff in the pull

[GitHub] storm pull request: STORM-1632 Disable event logging by default

Github user roshannaik commented on a diff in the pull request: https://github.com/apache/storm/pull/1217#discussion_r58601713 --- Diff: storm-core/src/ui/public/js/script.js --- @@ -220,19 +220,21 @@ function topologyActionJson(id, encodedId, name, status, msgTimeout, debug, samp

Re: Not enough data to calculate spout lag

I checked in latest code KafkaUtils is class which is showing up this error (Same in previous version too) https://github.com/apache/storm/blob/master/external/storm-kafka/src/jvm/org/apache/storm/kafka/KafkaUtils.java From: Sachin Pasalkar

Re: Not enough data to calculate spout lag

Sorry, I missed your mail. We are using the 0.8 version ok Kafka & 0.10 version of storm. Yes its Trident topologies. From: Bobby Evans > Reply-To: "dev@storm.apache.org"

[VOTE] Release Apache Storm 1.0.0 (rc2)

This is a call to vote on releasing Apache Storm 1.0.0 (rc2) Full list of changes in this release: https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;hb=dba655a47aaad74f26b9bb9a75fa52c0eedd8b1e The tag/commit to be voted upon is v1.0.0:

[jira] [Created] (STORM-1686) Make local-grouping an independent option rather than just LOCAL_OR_SHUFFLE

Sachin Goyal created STORM-1686: --- Summary: Make local-grouping an independent option rather than just LOCAL_OR_SHUFFLE Key: STORM-1686 URL: https://issues.apache.org/jira/browse/STORM-1686 Project:

[jira] [Commented] (STORM-1632) Disable event logging by default

[ https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226684#comment-15226684 ] ASF GitHub Bot commented on STORM-1632: --- Github user arunmahadevan commented on a diff in the pull

[GitHub] storm pull request: STORM-1632 Disable event logging by default

Github user arunmahadevan commented on a diff in the pull request: https://github.com/apache/storm/pull/1217#discussion_r58577654 --- Diff: storm-core/src/ui/public/js/script.js --- @@ -220,19 +220,21 @@ function topologyActionJson(id, encodedId, name, status, msgTimeout, debug,

Re: [VOTE] Release Apache Storm 1.0.0 (rc1)

I guess it depends on how you interpret this [1], which implies that users interested in release candidates should be subscribed to the dev@ mailing list. Though I imagine some tweaks to the wording of a release VOTE could make it acceptable to CC @user. -Taylor [1]

答复: why don't we relocate the kryo by maven-shade-plugin?

Than you Bobby, we'd better not to expose kryo to the end users directly. Of course, there was nothing we could do due to historical

Re: [VOTE] Release Apache Storm 1.0.0 (rc1)

I was not suggesting to post to user@ instead of dev@ but simply to CC user@ . @Jungtaek : probably the case for the projects you mentioned but the ones I have been involved in (Tika, Nutch) do post to both lists. I can't think of any reason not to do it : the more people see it, the better. On

[jira] [Commented] (STORM-1632) Disable event logging by default

[ https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226457#comment-15226457 ] ASF GitHub Bot commented on STORM-1632: --- Github user abhishekagarwal87 commented on a diff in the

[jira] [Updated] (STORM-1682) Kafka spout can lose partitions

[ https://issues.apache.org/jira/browse/STORM-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated STORM-1682: -- Description: The KafkaSpout can lose partitions for a period, or hang because

[jira] [Updated] (STORM-1682) Kafka spout can lose partitions

[ https://issues.apache.org/jira/browse/STORM-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated STORM-1682: -- Description: The KafkaSpout can lose partitions for a period, or hang because

[GitHub] storm pull request: STORM-1632 Disable event logging by default

Github user abhishekagarwal87 commented on a diff in the pull request: https://github.com/apache/storm/pull/1217#discussion_r58558813 --- Diff: storm-core/src/ui/public/js/script.js --- @@ -220,19 +220,21 @@ function topologyActionJson(id, encodedId, name, status, msgTimeout,

Re: why don't we relocate the kryo by maven-shade-plugin?

Because we expose kryo to the end users.  They can add in their own plugins to serialize objects and if we shade it all of that will break.  - Bobby On Tuesday, April 5, 2016 9:40 AM, John Fang wrote:   why don't we relocate the kryo by

why don't we relocate the kryo by maven-shade-plugin?

why don't we relocate the kryo by maven-shade-plugin? Due to the carbonite ? The conflict with kryo’s version happened sometime. Regards John Fang

[jira] [Commented] (STORM-1469) Unable to deploy large topologies on apache storm

[ https://issues.apache.org/jira/browse/STORM-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226329#comment-15226329 ] ASF GitHub Bot commented on STORM-1469: --- Github user kishorvpatil commented on the pull request:

[GitHub] storm pull request: [STORM-1469] Remove SimpleTransportPlugin and ...

Github user kishorvpatil commented on the pull request: https://github.com/apache/storm/pull/1178#issuecomment-205829598 @abhishekagarwal87 I supposed we did not merge this PR in time. I think we should change default plugin to `PlainSaslTransportPlugin`. Let me upmerge this. --- If

[jira] [Commented] (STORM-1469) Unable to deploy large topologies on apache storm

[ https://issues.apache.org/jira/browse/STORM-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226315#comment-15226315 ] ASF GitHub Bot commented on STORM-1469: --- Github user abhishekagarwal87 commented on the pull

[GitHub] storm pull request: [STORM-1469] Remove SimpleTransportPlugin and ...

Github user abhishekagarwal87 commented on the pull request: https://github.com/apache/storm/pull/1178#issuecomment-205824333 @kishorvpatil can you rebase it? Also, I see that default transport plugin in 1.x is still SimpleTransportPlugin even though it is deprecated. Is it intended?

[GitHub] storm pull request: remove unnecessary registerSerialization about...

Github user satishd commented on the pull request: https://github.com/apache/storm/pull/1278#issuecomment-205817560 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[jira] [Commented] (STORM-1286) port backtype.storm.command.kill-workers to java

[ https://issues.apache.org/jira/browse/STORM-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226286#comment-15226286 ] ASF GitHub Bot commented on STORM-1286: --- Github user satishd commented on the pull request:

[GitHub] storm pull request: [STORM-1286] port kill_workers to java.

Github user satishd commented on the pull request: https://github.com/apache/storm/pull/1310#issuecomment-205816863 +1 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

Re: [VOTE] Release Apache Storm 1.0.0 (rc1)

It is also in the bylaws as the place that we will post it. http://storm.apache.org/contribute/BYLAWS.html#actions Look under the table for product release. | Product Release | A vote is required to accept a proposed release as an official release of the project. Any Committer may call for a

[CANCELED] [VOTE] Release Apache Storm 1.0.0 (rc1)

Canceling the vote due to issues raised with the source distribution. I will cut a new release candidate shortly. -Taylor > On Apr 1, 2016, at 7:50 PM, P. Taylor Goetz wrote: > > This is a call to vote on releasing Apache Storm 1.0.0 (rc1) > > Full list of changes in this

Re: [VOTE] Release Apache Storm 1.0.0 (rc1)

Hi Julien, AFAIK, posting VOTE to dev@ list meets common practice in Apache projects. I subscribed dev@ list of Storm, Spark, HBase, (incubating) Zeppelin, Kafka, and all projects only include dev@ to VOTE thread. Users and contributors can still vote as non-binding in VOTE thread in dev@ list.

Re: [VOTE] Release Apache Storm 1.0.0 (rc1)

Btw, since I only have one machines (for dev.), anyone does sanity check on huge cluster would be really appreciated. Thanks! Jungtaek Lim (HeartSaVioR) 2016년 4월 5일 (화) 오후 9:05, John Fang 님이 작성: > I hope we can release Apache storm 1.0.0 in mid, I am doing tests.

回复：[VOTE] Release Apache Storm 1.0.0 (rc1)

I hope we can release Apache storm 1.0.0 in mid, I am doing tests. Of course, now I can't find some bugs.

Re: [VOTE] Release Apache Storm 1.0.0 (rc1)

Lets just do an RC2.  I really would like to spend some time and try to do a more complete test of a 1.0.0 release.  No matter what happens we will likely have a 1.0.1 soon, but I would prefer to beat on it and do some perf testing before we release it to the world.  - Bobby On Tuesday,

Re: [VOTE] Release Apache Storm 1.0.0 (rc1)

What about including user@ in this discussion? Users' votes are non binding but it is a good way of getting more people to test the RCs. This is common practice in other Apache projects Julien On 5 April 2016 at 00:05, Jungtaek Lim wrote: > We're releasing the first major