[
https://issues.apache.org/jira/browse/STORM-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469414#comment-15469414
]
Kamal edited comment on STORM-1985 at 9/7/16 3:40 AM:
--
Thanks for the
[
https://issues.apache.org/jira/browse/STORM-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469414#comment-15469414
]
Kamal edited comment on STORM-1985 at 9/7/16 3:40 AM:
--
Thanks for the
[
https://issues.apache.org/jira/browse/STORM-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469414#comment-15469414
]
Kamal commented on STORM-1985:
--
Thanks for this input and sorry for the delay from my side as
GitHub user kamleshbhatt opened a pull request:
https://github.com/apache/storm/pull/1677
STORM-1985: Admin Commands
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kamleshbhatt/storm master
Alternatively you can review and appl
Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1642
@knusbaum @srdo @harshach @HeartSaVioR @abellina I really would appreciate
it if you could take another look at this patch. I think everything is ready
to go except a final squash before merging it.
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1642#discussion_r77738006
--- Diff:
storm-core/src/jvm/org/apache/storm/daemon/supervisor/Supervisor.java ---
@@ -17,135 +17,231 @@
*/
package org.apache.storm.daemon.superv
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1642#discussion_r77726704
--- Diff:
storm-core/src/jvm/org/apache/storm/daemon/supervisor/Supervisor.java ---
@@ -17,135 +17,231 @@
*/
package org.apache.storm.daemon.superv
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1642#discussion_r77725278
--- Diff:
storm-core/src/jvm/org/apache/storm/daemon/supervisor/Supervisor.java ---
@@ -17,135 +17,231 @@
*/
package org.apache.storm.daemon.superv
Github user dossett commented on the issue:
https://github.com/apache/storm/pull/1639
@kojiisd Thanks for this contribution. We have a few different pull
requests related to support for ElasticSearch 2.X. I'll start a discussion on
the DEV list for the best way to handle them.
---
Github user knusbaum commented on the issue:
https://github.com/apache/storm/pull/1676
Do we want this on any of the 1.* branches?
---
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
This is intentional. We don't want user code to preempt any of storm's
libraries. Storm shades most of the libraries it uses, so you should be able to
bundle the libraries you want in with your topology jar.
For guava specifically, storm-core does not include it. You may just package it
in your
Github user kishorvpatil commented on the issue:
https://github.com/apache/storm/pull/728
@hsun-cnnxty, I think this is great change to have. Any way we can
implement this as a plugin for us to switch between current implementation? It
took substantial amount to get the current versio
GitHub user knusbaum opened a pull request:
https://github.com/apache/storm/pull/1676
STORM-2085: Remove guava from storm-core pom.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/knusbaum/incubator-storm STORM-2085-pick
Alterna
Kyle Nusbaum created STORM-2085:
---
Summary: Remove guava from storm-core pom.
Key: STORM-2085
URL: https://issues.apache.org/jira/browse/STORM-2085
Project: Apache Storm
Issue Type: Improvement
Github user knusbaum commented on the issue:
https://github.com/apache/storm/pull/1674
@revans2 +1 for that. That's simpler to understand and implement.
---
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
Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1674
For me either the supervisor works or it does not. If it doesn't work
don't use it. If it is slightly better then another supervisor does not tell
me much. If too many don't work let someone know
Github user knusbaum commented on the issue:
https://github.com/apache/storm/pull/1674
We could just have some "relative badness" heuristic. I would expect the
supervisors would be in a bell curve of "goodness/badness" and we can just
blacklist the ones in the bad part of the tail, th
Hi walid,
you can set no.of workers per topology, in your case it is 2. you have 4
typologies and each one has 2 i.e 8 worker slots required to run 4
typologies.
Do you have enough worker slots ? How many supervisor instances are running
? How many workers in total ?
You can find this information
Here is one effort on quantification the improvements Š
http://hortonworks.com/blog/microbenchmarking-storm-1-0-performance/
-roshan
On 9/6/16, 10:17 AM, "S G" wrote:
>Hi,
>
>On the http://storm.apache.org/2016/04/12/storm100-released.html page, I
>see a notice about performance improvemen
Hi,
On the http://storm.apache.org/2016/04/12/storm100-released.html page, I
see a notice about performance improvements to the order of 16 times.
Can someone please provide a little more details on the same? Is the
throughput of a topology increased 16 times (that sounds a lot, hence the
questio
Github user kamleshbhatt closed the pull request at:
https://github.com/apache/storm/pull/1675
---
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 and wishes so, or if the feature i
GitHub user kamleshbhatt opened a pull request:
https://github.com/apache/storm/pull/1675
Update
Update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kamleshbhatt/storm master
Alternatively you can review and apply these change
[
https://issues.apache.org/jira/browse/STORM-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467776#comment-15467776
]
Renjie Liu commented on STORM-1642:
---
I've proposed a patch for this issue but the PMC do
Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1674
My example was theoretical, I honestly don't know if in practice nimbus
would see the supervisor appear then disappear if nimbus's nic was bad. The
more common case would be if a ZK nic was bad, tha
Hi everyone,
In batch processing, as an example Mapreduce running in datacenters serves more
than job and there are a lot of research about the optimization as how to speed
up or jobs finishing time, ..etc?
The question:Is the real-time engines (like storm) designed to run more than
job (topolog
Hi Manu,
I do not need more slots because the topology I am running is only three
executors. However, Is it possible to set number of slots/supervisor to be more
than four to run as an example more than four typologies.
Thanks--WA
From: Manu Zhang
To: Walid Aljoby ; "u...@storm.apache.
Github user vesense commented on the issue:
https://github.com/apache/storm/pull/1674
Agree with @revans2 's opinion. Especially, make this feature as a part of
nimbus and show the blacklist nodes on the UI.
For the third point, I feel we can add a task(eg: `ping` the standby
ni
Ya I don't think what you are doing is going to work. We are doing some kind
of crazy things with clojure and I'm not sure that making your fork of
storm-core a maven project child of a modified storm-core is the right way to
go. In general it is a lot simpler if you leave storm-core in place
Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1673
@HeartSaVioR thanks, I should have looked more closely at the conflict.
+1 post-merge
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
+1 my group has used it and would love to see it as an official part of storm.
- Bobby
On Monday, September 5, 2016 11:40 PM, Satish Duggana
wrote:
+1 for getting this into Apache Storm.
I looked at this project earlier and I am open to be a committer sponsor
for storm-jms.
Thanks,
Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1674
Overall I like the concept here, and if a supervisor is
appearing/disappearing a lot we probably do want to blacklist that supervisor.
That said I have a few system concerns.
1) I would lik
Robert Joseph Evans created STORM-2084:
--
Summary: after supervisor v2 merge async localizer and localizer
Key: STORM-2084
URL: https://issues.apache.org/jira/browse/STORM-2084
Project: Apache Stor
[
https://issues.apache.org/jira/browse/STORM-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467112#comment-15467112
]
Kailas Janardhanan commented on STORM-1642:
---
Hello All,
I am using storm version
Do you have more required slots than available ? Topologies do not share
slots in storm.
Manu
On Tue, Sep 6, 2016 at 5:50 PM Walid Aljoby
wrote:
> Hi Manu,
> Number of workers is only two per topology.
> Thanks--WA From: Manu Zhang
> To: Walid Aljoby ; User ;
> "dev@storm.apache.org"
>
[
https://issues.apache.org/jira/browse/STORM-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xin Wang updated STORM-2083:
Fix Version/s: (was: 1.0.3)
(was: 1.1.0)
(was: 1.0.2)
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1674#discussion_r77605825
--- Diff:
storm-core/src/jvm/org/apache/storm/scheduler/blacklist/strategies/DefaultBlacklistStrategy.java
---
@@ -0,0 +1,142 @@
+/**
+ * Licensed to
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1674#discussion_r77605544
--- Diff:
storm-core/src/jvm/org/apache/storm/scheduler/blacklist/CircularBuffer.java ---
@@ -0,0 +1,182 @@
+/**
+ * Licensed to the Apache Software F
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1674#discussion_r77605365
--- Diff:
storm-core/src/jvm/org/apache/storm/scheduler/blacklist/CircularBuffer.java ---
@@ -0,0 +1,182 @@
+/**
+ * Licensed to the Apache Software F
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1674#discussion_r77605127
--- Diff:
storm-core/src/jvm/org/apache/storm/scheduler/blacklist/BlacklistScheduler.java
---
@@ -0,0 +1,212 @@
+package org.apache.storm.scheduler.black
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1674#discussion_r77605020
--- Diff:
storm-core/src/jvm/org/apache/storm/scheduler/blacklist/BlacklistScheduler.java
---
@@ -0,0 +1,212 @@
+package org.apache.storm.scheduler.black
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1674#discussion_r77604777
--- Diff:
storm-core/src/jvm/org/apache/storm/scheduler/blacklist/BlacklistScheduler.java
---
@@ -0,0 +1,212 @@
+package org.apache.storm.scheduler.black
Hi Manu,
Number of workers is only two per topology.
Thanks--WA From: Manu Zhang
To: Walid Aljoby ; User ;
"dev@storm.apache.org"
Sent: Tuesday, September 6, 2016 5:32 PM
Subject: Re: Max supervisor slots
Hi Walid,
What's the number of workers you set for each topology ?
Manu
On Tue
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1674#discussion_r77604642
--- Diff:
storm-core/src/jvm/org/apache/storm/scheduler/blacklist/BlacklistScheduler.java
---
@@ -0,0 +1,212 @@
+package org.apache.storm.scheduler.black
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1565
@vesense Thanks for the update. +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
enabl
Hi Walid,
What's the number of workers you set for each topology ?
Manu
On Tue, Sep 6, 2016 at 3:44 PM Walid Aljoby
wrote:
> Hi Everyone,
> I have a question please about the maximum typologies that can be
> processed by Apache storm production cluster?
> Although the number of slots per super
GitHub user nilday opened a pull request:
https://github.com/apache/storm/pull/1674
STORM-2083: Blacklist scheduler
A resolve of [STORM-2083](https://issues.apache.org/jira/browse/STORM-2083)
You can merge this pull request into a Git repository by running:
$ git pull https://g
Github user vesense commented on the issue:
https://github.com/apache/storm/pull/1565
@HeartSaVioR Could you take a look again?
---
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
en
[
https://issues.apache.org/jira/browse/STORM-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466809#comment-15466809
]
Howard Lee commented on STORM-2083:
---
We find that there is already a Blacklist in storm
Howard Lee created STORM-2083:
-
Summary: Blacklist Scheduler
Key: STORM-2083
URL: https://issues.apache.org/jira/browse/STORM-2083
Project: Apache Storm
Issue Type: New Feature
Componen
Hi Everyone,
I have a question please about the maximum typologies that can be processed by
Apache storm production cluster?
Although the number of slots per supervisor is four(6700,6701,6702,6703), but
when I submitted four typologies, I noted only three were running in parallel,
while one of t
50 matches
Mail list logo
