Dongfang Qu created STORM-744:
-
Summary: downstream worker fail may lead to worker oom without
limit pending TaskMessage count
Key: STORM-744
URL: https://issues.apache.org/jira/browse/STORM-744
Project:
[
https://issues.apache.org/jira/browse/STORM-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongfang Qu updated STORM-744:
--
Description:
storm-core/src/jvm/backtype/storm/messaging/netty/Server.java
for (int i = 0; i < q
[
https://issues.apache.org/jira/browse/STORM-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongfang Qu updated STORM-744:
--
Description:
storm-core/src/jvm/backtype/storm/messaging/netty/Server.java
message_queue[i] = new LinkedB
Hi folks,
Today i came across a weird and annoying error in My Storm Topology Builder.
The problem is When i submit my jar file to storm cluster It always skips the
second argument passed to the main method.
public class ZMQTopology {
public static void main(String[] args) throws AlreadyAliveExce
jishnu created STORM-745:
Summary: Second Commandline Parameter passed to the main class is
skipped when run in windows
Key: STORM-745
URL: https://issues.apache.org/jira/browse/STORM-745
Project: Apache Stor
[
https://issues.apache.org/jira/browse/STORM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jishnu updated STORM-745:
-
Assignee: (was: jishnu)
> Second Commandline Parameter passed to the main class is skipped when run in
> windo
[
https://issues.apache.org/jira/browse/STORM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jishnu updated STORM-745:
-
Priority: Major (was: Minor)
> Second Commandline Parameter passed to the main class is skipped when run in
> win
You can open the JIRA yourself at http://issues.apache.org/jira under the STORM
component. That way you will be able to track it more clearly. I'm not really
sure what would be happening here. The command line is preprocessed by python
looking for a -c or a --config to pull those out, but I h
GitHub user d2r opened a pull request:
https://github.com/apache/storm/pull/499
[STORM-746] Skip ack init when there are no output tasks
See [STORM-746](https://issues.apache.org/jira/browse/STORM-746) for the
description.
You can merge this pull request into a Git repository by ru
[
https://issues.apache.org/jira/browse/STORM-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392735#comment-14392735
]
ASF GitHub Bot commented on STORM-746:
--
GitHub user d2r opened a pull request:
ht
Mansheng Yang created STORM-747:
---
Summary: assignment-version-callback/info-with-version-callback
are not fired when assignments change
Key: STORM-747
URL: https://issues.apache.org/jira/browse/STORM-747
Derek Dagit created STORM-746:
-
Summary: Disable Spout Ack Init when there is no output task
Key: STORM-746
URL: https://issues.apache.org/jira/browse/STORM-746
Project: Apache Storm
Issue Type:
[
https://issues.apache.org/jira/browse/STORM-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392988#comment-14392988
]
Yee commented on STORM-531:
---
oh shit ! this happened 0.9.4 when run with " bin/storm jar
exampl
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/275#issuecomment-89020139
@nathanmarz any update on your opinion of this. Your original concerns
were addressed, and I feel we should check this in. If I don't hear back soon
I'll assume that it
[
https://issues.apache.org/jira/browse/STORM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393230#comment-14393230
]
ASF GitHub Bot commented on STORM-512:
--
Github user revans2 commented on the pull requ
P. Taylor Goetz created STORM-748:
-
Summary: Package Multi-Lang scripts so they don't have to be
duplicated
Key: STORM-748
URL: https://issues.apache.org/jira/browse/STORM-748
Project: Apache Storm
GitHub user emulvaney opened a pull request:
https://github.com/apache/storm/pull/501
An option for new/updated Redis keys to expire in RedisMapState
This is much the same as the mechanism already available via
`RedisStateUpdater` for `RedisState` instances. Users can now set
`exp
Parth Brahmbhatt created STORM-749:
--
Summary: Remove CSRF check from rest API
Key: STORM-749
URL: https://issues.apache.org/jira/browse/STORM-749
Project: Apache Storm
Issue Type: Task
A
GitHub user Parth-Brahmbhatt opened a pull request:
https://github.com/apache/storm/pull/502
STORM-749: Remove CSRF check.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Parth-Brahmbhatt/incubator-storm STORM-749
Alternatively
[
https://issues.apache.org/jira/browse/STORM-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393871#comment-14393871
]
ASF GitHub Bot commented on STORM-749:
--
GitHub user Parth-Brahmbhatt opened a pull req
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/502#issuecomment-89117111
+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 and
[
https://issues.apache.org/jira/browse/STORM-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393932#comment-14393932
]
ASF GitHub Bot commented on STORM-749:
--
Github user harshach commented on the pull req
Based on code in RollingTopWords, the emitFrequencyInSeconds of
RollingCountBolt, IntermediateRankingsBolt and TotalRankingsBolt are 3, 2,
2 respectively. And the windowLengthInSeconds is 9 in
emitFrequencyInSeconds.
So can i assume that the app's target is getting the topK of last 9 seconds
every
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/502#issuecomment-89161672
LGTM.
Maybe it would be better to remove "antiForgeryToken" from
/api/v1/topology/:id's sample json.
---
If your project is set up for it, you can reply to this e
[
https://issues.apache.org/jira/browse/STORM-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394054#comment-14394054
]
ASF GitHub Bot commented on STORM-749:
--
Github user HeartSaVioR commented on the pull
[
https://issues.apache.org/jira/browse/STORM-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394106#comment-14394106
]
Jungtaek Lim commented on STORM-738:
I thought overflow-control once more, and there se
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/501#issuecomment-89184522
Looks good to me overall.
Btw, you're encouraged to request for pull to master branch.
If committer thinks that should be included for 0.10.0, it would be
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/501#issuecomment-89185553
Please see https://github.com/apache/storm/blob/master/DEVELOPER.md for how
to contribute.
---
If your project is set up for it, you can reply to this email and have
28 matches
Mail list logo
