[jira] [Resolved] (STORM-2427) Event logger enable/disable UI is not working as expected in master branch
[ https://issues.apache.org/jira/browse/STORM-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana resolved STORM-2427. --- Resolution: Fixed > Event logger enable/disable UI is not working as expected in master branch > -- > > Key: STORM-2427 > URL: https://issues.apache.org/jira/browse/STORM-2427 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Arun Mahadevan >Assignee: Arun Mahadevan > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to pull missing commits from 1.x branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STORM-2427) Event logger enable/disable UI is not working as expected in master branch
[ https://issues.apache.org/jira/browse/STORM-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana updated STORM-2427: -- Fix Version/s: 2.0.0 > Event logger enable/disable UI is not working as expected in master branch > -- > > Key: STORM-2427 > URL: https://issues.apache.org/jira/browse/STORM-2427 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Arun Mahadevan >Assignee: Arun Mahadevan > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to pull missing commits from 1.x branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (STORM-2427) Event logger enable/disable UI is not working as expected in master branch
[ https://issues.apache.org/jira/browse/STORM-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana reassigned STORM-2427: - Assignee: Satish Duggana (was: Arun Mahadevan) > Event logger enable/disable UI is not working as expected in master branch > -- > > Key: STORM-2427 > URL: https://issues.apache.org/jira/browse/STORM-2427 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Arun Mahadevan >Assignee: Satish Duggana > Time Spent: 20m > Remaining Estimate: 0h > > Need to pull missing commits from 1.x branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (STORM-2427) Event logger enable/disable UI is not working as expected in master branch
[ https://issues.apache.org/jira/browse/STORM-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana reassigned STORM-2427: - Assignee: Arun Mahadevan (was: Satish Duggana) > Event logger enable/disable UI is not working as expected in master branch > -- > > Key: STORM-2427 > URL: https://issues.apache.org/jira/browse/STORM-2427 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Arun Mahadevan >Assignee: Arun Mahadevan > Time Spent: 20m > Remaining Estimate: 0h > > Need to pull missing commits from 1.x branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STORM-2409) Storm-Kafka-Client KafkaSpout Support for Failed and Null Tuples
[ https://issues.apache.org/jira/browse/STORM-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana updated STORM-2409: -- Fix Version/s: 1.x 2.0.0 > Storm-Kafka-Client KafkaSpout Support for Failed and Null Tuples > > > Key: STORM-2409 > URL: https://issues.apache.org/jira/browse/STORM-2409 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka-client >Affects Versions: 2.0.0, 1.x >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Critical > Fix For: 2.0.0, 1.x > > Time Spent: 3.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STORM-2409) Storm-Kafka-Client KafkaSpout Support for Failed and Null Tuples
[ https://issues.apache.org/jira/browse/STORM-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana resolved STORM-2409. --- Resolution: Fixed > Storm-Kafka-Client KafkaSpout Support for Failed and Null Tuples > > > Key: STORM-2409 > URL: https://issues.apache.org/jira/browse/STORM-2409 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka-client >Affects Versions: 2.0.0, 1.x >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Critical > Time Spent: 3.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STORM-2425) Storm Hive Bolt not closing open transactions
[ https://issues.apache.org/jira/browse/STORM-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana resolved STORM-2425. --- Resolution: Fixed > Storm Hive Bolt not closing open transactions > - > > Key: STORM-2425 > URL: https://issues.apache.org/jira/browse/STORM-2425 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0, 1.x >Reporter: Arun Mahadevan >Assignee: Arun Mahadevan > Fix For: 2.0.0, 1.x > > Time Spent: 40m > Remaining Estimate: 0h > > Hive bolt will close connection only if parameter "max_connections" is > exceeded or bolt dies. So if we open a connection to Hive via Hive bolt and > some time later we stop producing messages to Hive bolt, connection will be > maintained and corresponding transactions will be opened. This can be a > problem if we launch two topologies and one of them will maintain open > transactions doing nothing, and other will work writing messages to hive. At > some point hive will launch compactions to collapse small delta files > generated by Hive Bolt into one base file. But compaction wont launch if we > have opened transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (STORM-2425) Storm Hive Bolt not closing open transactions
[ https://issues.apache.org/jira/browse/STORM-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana reassigned STORM-2425: - Assignee: Satish Duggana (was: Arun Mahadevan) > Storm Hive Bolt not closing open transactions > - > > Key: STORM-2425 > URL: https://issues.apache.org/jira/browse/STORM-2425 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0, 1.x >Reporter: Arun Mahadevan >Assignee: Satish Duggana > Fix For: 2.0.0, 1.x > > Time Spent: 40m > Remaining Estimate: 0h > > Hive bolt will close connection only if parameter "max_connections" is > exceeded or bolt dies. So if we open a connection to Hive via Hive bolt and > some time later we stop producing messages to Hive bolt, connection will be > maintained and corresponding transactions will be opened. This can be a > problem if we launch two topologies and one of them will maintain open > transactions doing nothing, and other will work writing messages to hive. At > some point hive will launch compactions to collapse small delta files > generated by Hive Bolt into one base file. But compaction wont launch if we > have opened transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STORM-2425) Storm Hive Bolt not closing open transactions
[ https://issues.apache.org/jira/browse/STORM-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana updated STORM-2425: -- Affects Version/s: 1.x 2.0.0 > Storm Hive Bolt not closing open transactions > - > > Key: STORM-2425 > URL: https://issues.apache.org/jira/browse/STORM-2425 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0, 1.x >Reporter: Arun Mahadevan >Assignee: Arun Mahadevan > Fix For: 2.0.0, 1.x > > Time Spent: 40m > Remaining Estimate: 0h > > Hive bolt will close connection only if parameter "max_connections" is > exceeded or bolt dies. So if we open a connection to Hive via Hive bolt and > some time later we stop producing messages to Hive bolt, connection will be > maintained and corresponding transactions will be opened. This can be a > problem if we launch two topologies and one of them will maintain open > transactions doing nothing, and other will work writing messages to hive. At > some point hive will launch compactions to collapse small delta files > generated by Hive Bolt into one base file. But compaction wont launch if we > have opened transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (STORM-2425) Storm Hive Bolt not closing open transactions
[ https://issues.apache.org/jira/browse/STORM-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana reassigned STORM-2425: - Assignee: Arun Mahadevan (was: Satish Duggana) > Storm Hive Bolt not closing open transactions > - > > Key: STORM-2425 > URL: https://issues.apache.org/jira/browse/STORM-2425 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0, 1.x >Reporter: Arun Mahadevan >Assignee: Arun Mahadevan > Fix For: 2.0.0, 1.x > > Time Spent: 40m > Remaining Estimate: 0h > > Hive bolt will close connection only if parameter "max_connections" is > exceeded or bolt dies. So if we open a connection to Hive via Hive bolt and > some time later we stop producing messages to Hive bolt, connection will be > maintained and corresponding transactions will be opened. This can be a > problem if we launch two topologies and one of them will maintain open > transactions doing nothing, and other will work writing messages to hive. At > some point hive will launch compactions to collapse small delta files > generated by Hive Bolt into one base file. But compaction wont launch if we > have opened transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STORM-2425) Storm Hive Bolt not closing open transactions
[ https://issues.apache.org/jira/browse/STORM-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana updated STORM-2425: -- Fix Version/s: 1.x 2.0.0 > Storm Hive Bolt not closing open transactions > - > > Key: STORM-2425 > URL: https://issues.apache.org/jira/browse/STORM-2425 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0, 1.x >Reporter: Arun Mahadevan >Assignee: Arun Mahadevan > Fix For: 2.0.0, 1.x > > Time Spent: 40m > Remaining Estimate: 0h > > Hive bolt will close connection only if parameter "max_connections" is > exceeded or bolt dies. So if we open a connection to Hive via Hive bolt and > some time later we stop producing messages to Hive bolt, connection will be > maintained and corresponding transactions will be opened. This can be a > problem if we launch two topologies and one of them will maintain open > transactions doing nothing, and other will work writing messages to hive. At > some point hive will launch compactions to collapse small delta files > generated by Hive Bolt into one base file. But compaction wont launch if we > have opened transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STORM-2416) Release Packaging Improvements
[ https://issues.apache.org/jira/browse/STORM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935673#comment-15935673 ] Roshan Naik commented on STORM-2416: Didnt notice this move of the perf module from top level to examples dir Is there a reason for this ? I felt the perf belongs outside of the examples since it isn't really intended to be examples for users. Perf module is intended to evolve for purposes of perf measurements and benchmarking... for now its mostly for Storm devs, but eventually it could be run by end users as well. > Release Packaging Improvements > -- > > Key: STORM-2416 > URL: https://issues.apache.org/jira/browse/STORM-2416 > Project: Apache Storm > Issue Type: Improvement > Components: build >Reporter: P. Taylor Goetz >Assignee: P. Taylor Goetz > Fix For: 1.1.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > This issue is to address distribution packaging improvements discussed on the > dev@ list: > 1. Move remaining examples to "examples" directory. > 2. Package examples as source-only, to be compiled by users > 3. Remove connector jars from binary distribution (since they are available > in Maven, and we want to discourage users from hand-crafting topology jars) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STORM-2429) non-string values in supervisor.scheduler.meta cause crash
David Judd created STORM-2429: - Summary: non-string values in supervisor.scheduler.meta cause crash Key: STORM-2429 URL: https://issues.apache.org/jira/browse/STORM-2429 Project: Apache Storm Issue Type: Bug Components: storm-core Affects Versions: 1.0.3 Reporter: David Judd Priority: Minor The type of values in supervisor.scheduler.meta is not validated, but if one is not a string, supervisors crash during Thrift serialization with: java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String at org.apache.storm.generated.SupervisorInfo$SupervisorInfoStandardScheme.write(SupervisorInfo.java:1241) at org.apache.storm.generated.SupervisorInfo$SupervisorInfoStandardScheme.write(SupervisorInfo.java:1049) at org.apache.storm.generated.SupervisorInfo.write(SupervisorInfo.java:923) at org.apache.storm.thrift.TSerializer.serialize(TSerializer.java:79) at org.apache.storm.serialization.GzipThriftSerializationDelegate.serialize(GzipThriftSerializationDelegate.java:40) at org.apache.storm.utils.Utils.serialize(Utils.java:210) at org.apache.storm.cluster.StormClusterStateImpl.supervisorHeartbeat(StormClusterStateImpl.java:419) at org.apache.storm.daemon.supervisor.timer.SupervisorHeartbeat.run(SupervisorHeartbeat.java:85) at org.apache.storm.daemon.supervisor.Supervisor.launch(Supervisor.java:202) at org.apache.storm.daemon.supervisor.Supervisor.launchDaemon(Supervisor.java:243) at org.apache.storm.daemon.supervisor.Supervisor.main(Supervisor.java:362) I will attach a PR with a simple fix -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STORM-2428) Flux-core jar contains unpacked dependencies
Julien Nioche created STORM-2428: Summary: Flux-core jar contains unpacked dependencies Key: STORM-2428 URL: https://issues.apache.org/jira/browse/STORM-2428 Project: Apache Storm Issue Type: Bug Components: Flux Affects Versions: 1.0.3 Reporter: Julien Nioche The jar file for flux-core contains classes from /org/apache/http/. This was not the case before and causes problems with projects which rely on a different version of http-client. I can't see any references to http-client in the pom though. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STORM-2055) Exception when running topology from Maven exec with Flux
[
https://issues.apache.org/jira/browse/STORM-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Nioche resolved STORM-2055.
--
Resolution: Fixed
Assignee: Julien Nioche
Fixed in Storm 1.0.3
> Exception when running topology from Maven exec with Flux
> -
>
> Key: STORM-2055
> URL: https://issues.apache.org/jira/browse/STORM-2055
> Project: Apache Storm
> Issue Type: Bug
> Components: Flux
>Affects Versions: 1.0.2
>Reporter: Julien Nioche
>Assignee: Julien Nioche
>
> When running a topology from Maven with Flux as a dependency, we get
> {code}
> 11335 [Thread-8] ERROR o.a.s.event - Error when processing event
> java.io.FileNotFoundException: Source
> 'file:/home/julien/.m2/repository/org/apache/storm/flux-core/1.0.1/flux-core-1.0.1.jar!/resources'
> does not exist
> at
> org.apache.storm.shade.org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1368)
> ~[storm-core-1.0.1.jar:1.0.1]
> at
> org.apache.storm.shade.org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1261)
> ~[storm-core-1.0.1.jar:1.0.1]
> at
> org.apache.storm.shade.org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1230)
> ~[storm-core-1.0.1.jar:1.0.1]
> at
> org.apache.storm.daemon.supervisor$fn__9359.invoke(supervisor.clj:1194)
> ~[storm-core-1.0.1.jar:1.0.1]
> at clojure.lang.MultiFn.invoke(MultiFn.java:243) ~[clojure-1.7.0.jar:?]
> at
> org.apache.storm.daemon.supervisor$mk_synchronize_supervisor$this__9078$fn__9096.invoke(supervisor.clj:582)
> ~[storm-core-1.0.1.jar:1.0.1]
> at
> org.apache.storm.daemon.supervisor$mk_synchronize_supervisor$this__9078.invoke(supervisor.clj:581)
> ~[storm-core-1.0.1.jar:1.0.1]
> at org.apache.storm.event$event_manager$fn__8630.invoke(event.clj:40)
> [storm-core-1.0.1.jar:1.0.1]
> at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101]
> {code}
> The same topology runs fine when executed with Eclipse or via the storm
> command.
> See [https://github.com/DigitalPebble/storm-crawler/issues/324]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
