[jira] [Resolved] (STORM-2403) Fix KafkaBolt test failure: tick tuple should not be acked
[ https://issues.apache.org/jira/browse/STORM-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-2403. - Resolution: Fixed Fix Version/s: 1.0.4 1.1.0 2.0.0 Merged into master, 1.x, 1.0.x branches. > Fix KafkaBolt test failure: tick tuple should not be acked > -- > > Key: STORM-2403 > URL: https://issues.apache.org/jira/browse/STORM-2403 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Affects Versions: 2.0.0, 1.1.0, 1.0.4 >Reporter: Jungtaek Lim >Assignee: Jungtaek Lim >Priority: Blocker > Fix For: 2.0.0, 1.1.0, 1.0.4 > > Time Spent: 0.5h > Remaining Estimate: 0h > > From STORM-2387, I changed KafkaBolt to make sure it doesn't ack tick tuples. > (Tick tuples are generated from each executor and don't trigger ACK_INIT so > actually it should not be acked. Acker will keep them and remove some for > message timeout so not a big deal though.) > But I forgot to fix unit test for that, and also missed to check test result. > This issue is for making quick fix for that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STORM-2390) The storm-*-examples jars are missing in the binary distro
[ https://issues.apache.org/jira/browse/STORM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2390: Removing Epic Link since we're discussing exactly opposite way from dev@ mailing list. > The storm-*-examples jars are missing in the binary distro > -- > > Key: STORM-2390 > URL: https://issues.apache.org/jira/browse/STORM-2390 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Roshan Naik >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STORM-2408) build failed if storm.kafka.client.version = 0.10.2.0
[ https://issues.apache.org/jira/browse/STORM-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-2408. - Resolution: Fixed Assignee: Luke Sun Fix Version/s: 1.1.0 2.0.0 Thanks [~lukesun], I merged into master and 1.x branches. > build failed if storm.kafka.client.version = 0.10.2.0 > - > > Key: STORM-2408 > URL: https://issues.apache.org/jira/browse/STORM-2408 > Project: Apache Storm > Issue Type: Bug >Reporter: Luke Sun >Assignee: Luke Sun > Fix For: 2.0.0, 1.1.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Due to https://issues.apache.org/jira/browse/KAFKA-2247 the build will fail > if > mvn clean install -Dstorm.kafka.client.version=0.10.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STORM-2379) still refers 1.6 elastic
[
https://issues.apache.org/jira/browse/STORM-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907539#comment-15907539
]
Heather McCartney commented on STORM-2379:
--
I've done some work on this over at
https://github.com/hmcc/storm/tree/STORM-2379. I've used the new Elasticsearch
Java REST client so that we can (hopefully) support ES 2 and ES 5
simultaneously.
However, I'm wondering how best to test it. The existing integration tests use
the old Java client to create an Elasticsearch node during test setup. However,
Elasticsearch dropped support for running embedded nodes in this way in ES 5,
and in any case, I think it would be better if we could run tests against all
major versions of Elasticsearch in a single build.
I can't find anything "official" that allows us to do this. The
elasticsearch-maven-plugin only supports launching a single Elasticsearch
version, as does EsIntegTestCase.
However, there is an interesting blog post by someone at Elastic describing how
to install and start Elasticsearch for testing using Maven Ant tasks:
http://david.pilato.fr/blog/2016/10/18/elasticsearch-real-integration-tests-updated-for-ga/.
I think we could adapt this to start up multiple versions of Elasticsearch (on
different ports) and then connect to these for testing using the REST client.
What do you think?
> still refers 1.6 elastic
>
>
> Key: STORM-2379
> URL: https://issues.apache.org/jira/browse/STORM-2379
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-elasticsearch
>Affects Versions: 1.0.1, 1.0.2, 1.0.3
> Environment: storm 1.0.x
> elastic 5.0.0 and higher
>Reporter: Sree Vaddi
>Priority: Blocker
>
> following documentation:
> https://storm.apache.org/releases/1.0.1/storm-elasticsearch.html
> https://github.com/apache/storm/blob/master/external/storm-elasticsearch/pom.xml#L40
> this causes errors while writing to elastic 5.x
> {code:language=java}
> java.lang.NoClassDefFoundError: org/elasticsearch/common/base/Preconditions
> at
> org.apache.storm.elasticsearch.common.EsConfig.(EsConfig.java:62)
> ~[storm-elasticsearch-1.0.2.jar:1.0.2]
> at
> org.apache.storm.elasticsearch.common.EsConfig.(EsConfig.java:49)
> ~[storm-elasticsearch-1.0.2.jar:1.0.2]
> Caused by: java.lang.ClassNotFoundException:
> org.elasticsearch.common.base.Preconditions
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> ~[?:1.8.0_112]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_112]
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> ~[?:1.8.0_112]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_112]
> 261538 [elasticsearch[Ringleader][generic][T#2]] INFO o.e.c.transport -
> [Ringleader] failed to get node info for
> [#transport#-1][svaddi][inet[localhost/127.0.0.1:9200]], disconnecting...
> org.elasticsearch.transport.ReceiveTimeoutTransportException:
> [][inet[localhost/127.0.0.1:9200]][cluster:monitor/nodes/info] request_id
> [26] timed out after [5005ms]
> at
> org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:529)
> ~[elasticsearch-1.6.0.jar:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_112]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_112]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]
> {code}
> elastic logs:
> {code:language=java}
> [2017-02-23T15:47:04,487][WARN ][o.e.t.n.Netty4Transport ] [Qt9qlNV]
> exception caught on transport layer [[id: 0x8f15e875, L:/127.0.0.1:9300 -
> R:/127.0.0.1:52031]], closing connection
> java.lang.IllegalStateException: Received message from unsupported version:
> [1.0.0] minimal compatible version is: [5.0.0]
> at
> org.elasticsearch.transport.TcpTransport.messageReceived(TcpTransport.java:1199)
> ~[elasticsearch-5.0.0.jar:5.0.0]
> at
> org.elasticsearch.transport.netty4.Netty4MessageChannelHandler.channelRead(Netty4MessageChannelHandler.java:74)
> ~[transport-netty4-5.0.0.jar:5.0.0]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
> [netty-transport-4.1.5.Final.jar:4.1.5.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
> [netty-transport-4.1.5.Final.jar:4.1.5.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
> [netty-transport-4.1.5.Final.jar:4.1.5.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
> [netty-codec-4.1.5.Final.jar:4.1.5.Final]
>
[jira] [Created] (STORM-2409) Storm-Kafka-Client KafkaSpout Support for Failed and Null Tuples
Hugo Louro created STORM-2409: - Summary: 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 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STORM-2410) modify Trident-state.md
liuzhaokun created STORM-2410: - Summary: modify Trident-state.md Key: STORM-2410 URL: https://issues.apache.org/jira/browse/STORM-2410 Project: Apache Storm Issue Type: Documentation Components: documentation Affects Versions: 1.0.2 Reporter: liuzhaokun Attachments: trident_state.PNG The sentence, "(One side note – once Kafka supports replication, it will be possible to have transactional spouts that are fault-tolerant to node failure, but that feature does not exist yet.)" ,should be removed,because Kafka has supported replication. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STORM-2411) Event Logger count in defaults.yaml needs to be 0
Roshan Naik created STORM-2411: -- Summary: Event Logger count in defaults.yaml needs to be 0 Key: STORM-2411 URL: https://issues.apache.org/jira/browse/STORM-2411 Project: Apache Storm Issue Type: Bug Reporter: Roshan Naik Assignee: Roshan Naik Fix For: 2.0.0 Seems like a regression in master branch where the default setting for this has changed to null. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STORM-2411) Event Logger count in defaults.yaml needs to be 0
[ https://issues.apache.org/jira/browse/STORM-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923689#comment-15923689 ] Roshan Naik commented on STORM-2411: PR: https://github.com/apache/storm/pull/2000 > Event Logger count in defaults.yaml needs to be 0 > -- > > Key: STORM-2411 > URL: https://issues.apache.org/jira/browse/STORM-2411 > Project: Apache Storm > Issue Type: Bug >Reporter: Roshan Naik >Assignee: Roshan Naik > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Seems like a regression in master branch where the default setting for this > has changed to null. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
