+1 (binding)
Tested in a 3 node cluster with example topologies.
Checked the binaries.
Thanks,
Harsha
On Thu, Apr 7, 2016, at 10:02 PM, John Fang wrote:
> +1
>
> Regards
>John Fang
>
>
>
> -邮件原件-
> 发件人: Bobby Evans [mailto:ev...@yahoo-inc.com.INVALID]
> 发送时间: 2016年4月8日
+1 (Non binding)
- testing with source distribution(built using `mvn -P all-tests clean
install`) : OK
- testing with binary distribution (one machine) : OK
- launch daemons : OK
- run RollingTopWords (local) : OK
- run RollingTopWords (remote) : OK
- activate / deactivate / rebalance /
+1
Regards
John Fang
-邮件原件-
发件人: Bobby Evans [mailto:ev...@yahoo-inc.com.INVALID]
发送时间: 2016年4月8日 2:36
收件人: dev@storm.apache.org
主题: Re: [VOTE] Release Apache Storm 1.0.0 (rc2)
Forgot to say +1 binding
- Bobby
On Thursday, April 7, 2016 1:36 PM, Bobby Evans
Many storm users complain their links are broken. I field a
JIRA(STORM-1658) for fixing broken links in 0.9.6, 0.10.0, 1.0.0-SNAPSHOT,
2.0.0-SNAPSHOT documents. However I have no idea for redirecting storm site
urls from `/documentation/*.html` to `/releases/current/*.html` by changing
some code
[
https://issues.apache.org/jira/browse/STORM-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231627#comment-15231627
]
ASF GitHub Bot commented on STORM-1658:
---
GitHub user vesense opened a pull request:
GitHub user vesense opened a pull request:
https://github.com/apache/storm/pull/1321
STORM-1658: documents improvements and links fixes (for 0.9.x)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vesense/storm STORM-1658-0.9.x
This is included by https://issues.apache.org/jira/browse/STORM-1658
(documents improvements and links fixes).
Xin
2016-04-07 22:33 GMT+08:00 Bobby Evans :
> Just checked in a fix. Problem was that I tested it on a mac with a case
> insensitive file system and the
[
https://issues.apache.org/jira/browse/STORM-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231313#comment-15231313
]
ASF GitHub Bot commented on STORM-1696:
---
Github user zhuoliu commented on the pull request:
GitHub user zhuoliu opened a pull request:
https://github.com/apache/storm/pull/1320
[STORM-1696]-1.x-branch status not sync if zk fails in backpressure
This issue can cause a topology to be blocked.
You can merge this pull request into a Git repository by running:
$ git pull
Github user zhuoliu commented on the pull request:
https://github.com/apache/storm/pull/1320#issuecomment-207134141
I can either put the refactoring part as a separate pull request or within
this.
---
If your project is set up for it, you can reply to this email and have your
reply
[
https://issues.apache.org/jira/browse/STORM-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231311#comment-15231311
]
ASF GitHub Bot commented on STORM-1696:
---
GitHub user zhuoliu opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231301#comment-15231301
]
Zhuo Liu commented on STORM-1697:
-
Might be caused by supervisor.clj porting to java. 1.0 seems OK.
>
[
https://issues.apache.org/jira/browse/STORM-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1697:
Affects Version/s: (was: 1.0.0)
Fix Version/s: (was: 1.0.0)
> artifacts symlink not created
Zhuo Liu created STORM-1697:
---
Summary: artifacts symlink not created
Key: STORM-1697
URL: https://issues.apache.org/jira/browse/STORM-1697
Project: Apache Storm
Issue Type: Bug
[
https://issues.apache.org/jira/browse/STORM-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231214#comment-15231214
]
ASF GitHub Bot commented on STORM-1642:
---
Github user knusbaum commented on a diff in the pull
Github user knusbaum commented on a diff in the pull request:
https://github.com/apache/storm/pull/1316#discussion_r58954552
--- Diff: storm-core/src/clj/backtype/storm/daemon/executor.clj ---
@@ -431,13 +431,14 @@
(fn [tuple-batch sequence-id end-of-batch?]
[
https://issues.apache.org/jira/browse/STORM-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1696:
Description:
When there is a zk exception happens during worker-backpressure!,
there is a bad state which
[
https://issues.apache.org/jira/browse/STORM-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1696:
Description:
When there is a zk exception happens during worker-backpressure!,
there is a bad state which
Zhuo Liu created STORM-1696:
---
Summary: Backpressure flag not sync if zookeeper connection errors
Key: STORM-1696
URL: https://issues.apache.org/jira/browse/STORM-1696
Project: Apache Storm
Issue
Github user redsanket commented on the pull request:
https://github.com/apache/storm/pull/1313#issuecomment-207073888
+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
Forgot to say +1 binding
- Bobby
On Thursday, April 7, 2016 1:36 PM, Bobby Evans wrote:
With the default configs everything seems to work fine. I have run into a few
issues with not being able to set storm.workers.artifacts.dir, but I don't
think it is a
With the default configs everything seems to work fine. I have run into a few
issues with not being able to set storm.workers.artifacts.dir, but I don't
think it is a blocker.
- Bobby
On Wednesday, April 6, 2016 10:40 AM, Jungtaek Lim
wrote:
+1 (binding)
-
[
https://issues.apache.org/jira/browse/STORM-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230559#comment-15230559
]
ASF GitHub Bot commented on STORM-1464:
---
Github user dossett commented on the pull request:
Github user dossett commented on the pull request:
https://github.com/apache/storm/pull/1044#issuecomment-206992265
Merged. Thank you to everyone who provided feedback!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1044
---
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-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-822.
--
Resolution: Fixed
Fix Version/s: 1.0.0
This jira work is merged into
[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-822:
-
Assignee: Hugo Louro (was: Thomas Graves)
> As a storm developer I’d like to use
[
https://issues.apache.org/jira/browse/STORM-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hugo Louro reassigned STORM-1694:
-
Assignee: Hugo Louro
> TridentKafkaSpout using new consumer API
>
[
https://issues.apache.org/jira/browse/STORM-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1691.
Resolution: Fixed
[~satish.duggana],
I just checked in a fix for this. Please
[
https://issues.apache.org/jira/browse/STORM-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans reassigned STORM-1691:
--
Assignee: Robert Joseph Evans
> Earlier storm documentation links are broken.
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/1131#issuecomment-206972371
filed one here https://issues.apache.org/jira/browse/STORM-1694
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Thomas Graves created STORM-1695:
Summary: Create trident spout that uses the new kafka consumer API
Key: STORM-1695
URL: https://issues.apache.org/jira/browse/STORM-1695
Project: Apache Storm
Sriharsha Chintalapani created STORM-1694:
-
Summary: TridentKafkaSpout using new consumer API
Key: STORM-1694
URL: https://issues.apache.org/jira/browse/STORM-1694
Project: Apache Storm
[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230476#comment-15230476
]
ASF GitHub Bot commented on STORM-822:
--
Github user harshach commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230461#comment-15230461
]
ASF GitHub Bot commented on STORM-822:
--
Github user harshach commented on the pull request:
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/1131#issuecomment-206968509
@tgravescs we don't have JIRA yet on it.
---
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
[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230456#comment-15230456
]
ASF GitHub Bot commented on STORM-822:
--
Github user tgravescs commented on the pull request:
Github user tgravescs commented on the pull request:
https://github.com/apache/storm/pull/1131#issuecomment-206967402
@harshach @hmcl did we file a jira to add the trident support?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Graves reassigned STORM-822:
---
Assignee: Thomas Graves (was: Hugo Louro)
> As a storm developer I’d like to use the new
[
https://issues.apache.org/jira/browse/STORM-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230352#comment-15230352
]
Abhishek Agarwal edited comment on STORM-1693 at 4/7/16 2:52 PM:
-
I put up
[
https://issues.apache.org/jira/browse/STORM-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230352#comment-15230352
]
Abhishek Agarwal commented on STORM-1693:
-
I put up some code to catch any negative percentage
[
https://issues.apache.org/jira/browse/STORM-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Agarwal reassigned STORM-1693:
---
Assignee: Abhishek Agarwal
> Negative counts in the UI for __metrics stream
>
Just checked in a fix. Problem was that I tested it on a mac with a case
insensitive file system and the link should be Tutorial.html not tutorial.html
It should update the site shortly.
- Bobby
On Thursday, April 7, 2016 9:19 AM, "abhinav.x.gu...@barclays.com"
Hi Storm Developers,
I am unable to access http://storm.apache.org/releases/current/tutorial.html
It says
Not Found
The requested URL /releases/current/tutorial.html was not found on this server.
Regards,
Abhinav
+65-93583804
___
This message is
[
https://issues.apache.org/jira/browse/STORM-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230238#comment-15230238
]
ASF GitHub Bot commented on STORM-1658:
---
GitHub user vesense opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230249#comment-15230249
]
ASF GitHub Bot commented on STORM-1658:
---
GitHub user vesense opened a pull request:
GitHub user vesense opened a pull request:
https://github.com/apache/storm/pull/1319
STORM-1658: documents improvements and links fixes (for 0.10.x)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vesense/storm STORM-1658-0.10.x
[
https://issues.apache.org/jira/browse/STORM-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230242#comment-15230242
]
ASF GitHub Bot commented on STORM-1658:
---
GitHub user vesense opened a pull request:
GitHub user vesense opened a pull request:
https://github.com/apache/storm/pull/1318
STORM-1658: documents improvements and links fixes (for 1.x)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vesense/storm STORM-1658-1.x
[
https://issues.apache.org/jira/browse/STORM-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Agarwal updated STORM-1693:
Attachment: Screen Shot 2016-04-07 at 7.05.01 PM.png
> Negative counts in the UI for
Abhishek Agarwal created STORM-1693:
---
Summary: Negative counts in the UI for __metrics stream
Key: STORM-1693
URL: https://issues.apache.org/jira/browse/STORM-1693
Project: Apache Storm
GitHub user vesense opened a pull request:
https://github.com/apache/storm/pull/1317
STORM-1658: documents improvements and links fixes (for master)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vesense/storm STORM-1658
[
https://issues.apache.org/jira/browse/STORM-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xin Wang updated STORM-1658:
Summary: documents improvements and links fixes (was: documents 404 error)
> documents improvements and
[
https://issues.apache.org/jira/browse/STORM-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satish Duggana updated STORM-1369:
--
Component/s: storm-cassandra
> Add trident MapState to Cassandra
>
[
https://issues.apache.org/jira/browse/STORM-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated STORM-1692:
--
Summary: HBaseSecurityUtil#login modifies the current UGI causing issues if
two instances are
[
https://issues.apache.org/jira/browse/STORM-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satish Duggana reopened STORM-1692:
---
> org.apache.storm.hbase.security.HBaseSecurityUtil#login uses broken double
> checked locking.
[
https://issues.apache.org/jira/browse/STORM-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229845#comment-15229845
]
Arun Mahadevan commented on STORM-1692:
---
HBaseSecurityUtil uses legacyprovider.login(), which
[
https://issues.apache.org/jira/browse/STORM-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satish Duggana closed STORM-1692.
-
Resolution: Not A Bug
> org.apache.storm.hbase.security.HBaseSecurityUtil#login uses broken
Satish Duggana created STORM-1692:
-
Summary: org.apache.storm.hbase.security.HBaseSecurityUtil#login
uses broken double checked locking.
Key: STORM-1692
URL: https://issues.apache.org/jira/browse/STORM-1692
[
https://issues.apache.org/jira/browse/STORM-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229831#comment-15229831
]
ASF GitHub Bot commented on STORM-1642:
---
Github user liurenjie1024 commented on the pull request:
Github user liurenjie1024 commented on the pull request:
https://github.com/apache/storm/pull/1316#issuecomment-206732733
The reason why such a message is sent is that our security team is scanning
all the ports listened on each server and tries to detect potential weakness.
At
[
https://issues.apache.org/jira/browse/STORM-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229815#comment-15229815
]
ASF GitHub Bot commented on STORM-1642:
---
Github user abhishekagarwal87 commented on the pull
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1316#issuecomment-206724794
I can't think of a reason of why would such a message be sent to storm from
outside the cluster. Ideally only cluster machines and daemons should have
access
[
https://issues.apache.org/jira/browse/STORM-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229773#comment-15229773
]
ASF GitHub Bot commented on STORM-1642:
---
Github user liurenjie1024 commented on the pull request:
Github user liurenjie1024 commented on the pull request:
https://github.com/apache/storm/pull/1316#issuecomment-206713335
As I have mentioned in bug report, the reason why NPE happens is that storm
is vulnerable to fraud message from processes outside the cluster. To
reproduce the
65 matches
Mail list logo