[
https://issues.apache.org/jira/browse/STORM-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boyang Jerry Peng reassigned STORM-832:
---
Assignee: Boyang Jerry Peng
> Validation for configuration settings beyond those in
Github user hsun-cnnxty commented on the pull request:
https://github.com/apache/storm/pull/705#issuecomment-142364685
Erik,
Pushed the change to rename config from "storm" to "zookeeper" (also fixed
the typo). As of Kafka dependency, it is a good question. Actually I am
[
https://issues.apache.org/jira/browse/STORM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903091#comment-14903091
]
ASF GitHub Bot commented on STORM-1015:
---
Github user hsun-cnnxty commented on the pull request:
GitHub user knusbaum opened a pull request:
https://github.com/apache/storm/pull/755
STORM-1059: Upgrade Storm to use Clojure 1.7.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/knusbaum/incubator-storm STORM-1059
[
https://issues.apache.org/jira/browse/STORM-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903010#comment-14903010
]
ASF GitHub Bot commented on STORM-1059:
---
GitHub user knusbaum opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boyang Jerry Peng closed STORM-983.
---
Resolution: Invalid
> If stormconf.ser is not downloaded correctly, the supervisor will bounce
Haohui Mai created STORM-1060:
-
Summary: Serialize Calcite plans into JSON format
Key: STORM-1060
URL: https://issues.apache.org/jira/browse/STORM-1060
Project: Apache Storm
Issue Type: New
[
https://issues.apache.org/jira/browse/STORM-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903495#comment-14903495
]
ASF GitHub Bot commented on STORM-1058:
---
GitHub user zhuoliu opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Weathers updated STORM-763:
Description:
Debian 3.16.3-2~bpo70+1 (2014-09-21) x86_64 GNU/Linux
java version "1.7.0_03"
storm
My topology submits fine, and sometimes runs for a while. But eventually I
start seeing the below stacktrace over and over and it stops processing
messages.
I realize this is a bit vague, but any recommendations for troubleshooting?
2015-09-22T00:19:01.220-0400 b.s.d.supervisor [INFO] Starting
GitHub user zhuoliu opened a pull request:
https://github.com/apache/storm/pull/756
[STORM-1058] create CLI kill_workers to kill workers on a supervisor node
Kill all the workers running on this supervisor.
Currently there is no direct way to kill all the running workers on a
[
https://issues.apache.org/jira/browse/STORM-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai closed STORM-1045.
-
Resolution: Fixed
Thanks [~sriharsha] and [~dagit] for the reviews and commit.
> Parse CREATE TABLE
[
https://issues.apache.org/jira/browse/STORM-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-1063:
Description:
For current 0.11.0-SNAPSHOT, default value of storm.log4j2.conf.dir is "log4j2".
The
[
https://issues.apache.org/jira/browse/STORM-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903563#comment-14903563
]
ASF GitHub Bot commented on STORM-1045:
---
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903638#comment-14903638
]
ASF GitHub Bot commented on STORM-1017:
---
Github user priyank5485 commented on the pull request:
Haohui Mai created STORM-1062:
-
Summary: Establish the basic structure of the code generator
Key: STORM-1062
URL: https://issues.apache.org/jira/browse/STORM-1062
Project: Apache Storm
Issue
[
https://issues.apache.org/jira/browse/STORM-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai updated STORM-1062:
--
Description: This jira tracks the effort of creating the basic structures
of the code generator in
Github user erikdw commented on the pull request:
https://github.com/apache/storm/pull/733#issuecomment-142454751
Thanks @revans2 !@HeartSaVioR : please let me know if there's anything
I can do to help with the merge.
---
If your project is set up for it, you can reply to this
[
https://issues.apache.org/jira/browse/STORM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903611#comment-14903611
]
ASF GitHub Bot commented on STORM-350:
--
Github user HeartSaVioR commented on the pull request:
Priyank Shah created STORM-1061:
---
Summary: Create integration tests around ignoreZkOffsets config
for kafka spout - core and trident
Key: STORM-1061
URL: https://issues.apache.org/jira/browse/STORM-1061
GitHub user haohui opened a pull request:
https://github.com/apache/storm/pull/757
STORM-1060. Serialize Calcite plans into JSON format.
This PR provides an implementation to serialize the results of Calcite to
JSON strings. The JSON strings will be passed down to the optimizers
[
https://issues.apache.org/jira/browse/STORM-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903643#comment-14903643
]
ASF GitHub Bot commented on STORM-1060:
---
GitHub user haohui opened a pull request:
Jungtaek Lim created STORM-1063:
---
Summary: Workers cannot find log4j configuration files since
default value of storm.log4j2.conf.dir is relative
Key: STORM-1063
URL:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/734
---
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 is
[
https://issues.apache.org/jira/browse/STORM-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903609#comment-14903609
]
ASF GitHub Bot commented on STORM-1017:
---
Github user harshach commented on the pull request:
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/754#issuecomment-142443450
+1. @priyank5485 it will be great if you can add a integration test we can
do this in another jira.
---
If your project is set up for it, you can reply to this email
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/750#issuecomment-142443503
@revans2
I ran performance test from small cluster (three machines, each one has
zookeeper and supervisor, and only one has zookeeper, nimbus, supervisor)
[
https://issues.apache.org/jira/browse/STORM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyank Shah updated STORM-1061:
Description: Related to STORM-1017 changes. Add tests to make sure that
ignoreZkOffsets config is
Github user priyank5485 commented on the pull request:
https://github.com/apache/storm/pull/754#issuecomment-142448505
@harshach Created JIRA item for that. @ptgoetz can you please review this
as well?
---
If your project is set up for it, you can reply to this email and have your
Kyle Nusbaum created STORM-1059:
---
Summary: Upgrade Storm to use Clojure 1.7.0
Key: STORM-1059
URL: https://issues.apache.org/jira/browse/STORM-1059
Project: Apache Storm
Issue Type:
[
https://issues.apache.org/jira/browse/STORM-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Nusbaum reassigned STORM-1059:
---
Assignee: Kyle Nusbaum
> Upgrade Storm to use Clojure 1.7.0
>
GitHub user priyank5485 opened a pull request:
https://github.com/apache/storm/pull/754
Storm-1017: Ignore ignoreZkOffsets in case of worker crash and restart.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/priyank5485/storm
[
https://issues.apache.org/jira/browse/STORM-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14902893#comment-14902893
]
Priyank Shah commented on STORM-1017:
-
https://github.com/apache/storm/pull/754/files
> If
Matthias,
Personally I can't turn off github notification because of I'm also
collaborator of Jedis, which repository is belong to Github. ;(
I just wish to reduce notifications via same event (Github event &
JIRA automatic posting) from dev. mailing list.
Actually I don't have strong opinion
On Github, you can disable mail notification about each comment in your
profile configuration (at least for you personal email address -- I
guess it still goes over the mailing list)
Profile -> Settings -> Notification Center
-Matthias
On 09/22/2015 03:21 AM, Erik Weathers wrote:
> Sure,
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/733#issuecomment-142288795
I personally am fine with merging this into 0.9.6. It seems like a small
enough change and is very well defined.
---
If your project is set up for it, you can reply to
[
https://issues.apache.org/jira/browse/STORM-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1058:
Summary: create CLI kill_workers to kill workers on a supervisor node
(was: create CLI kill_workers to be
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/735
---
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 is
Zhuo Liu created STORM-1058:
---
Summary: create CLI kill_workers to be able to kill workers on a
supervisor node
Key: STORM-1058
URL: https://issues.apache.org/jira/browse/STORM-1058
Project: Apache Storm
[
https://issues.apache.org/jira/browse/STORM-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1058:
Description: Kill all the workers running on this supervisor. Currently
there is no direct way to kill all
[
https://issues.apache.org/jira/browse/STORM-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14902559#comment-14902559
]
ASF GitHub Bot commented on STORM-1057:
---
GitHub user wangli1426 opened a pull request:
GitHub user wangli1426 opened a pull request:
https://github.com/apache/storm/pull/753
[STORM-1057] Add throughput metrics to spouts/bolts and display them on web
ui
The throughputs for the spouts and bolts could help the user to identify
the performance bottleneck and detect the
42 matches
Mail list logo
