2020-01-15 13:21:48 UTC - Naby: ```...
...
17:23:38.150 [public/default/influxdb-test-sink-1] ERROR
org.apache.pulsar.functions.instance.JavaInstanceRunnable - Sou
rce open produced uncaught exception:
java.util.concurrent.CompletionException:
org.apache.pulsar.client.api.PulsarClientException$NotFoundException: No lates
t schema found for topic test-topics
at
java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:326)
~[?:1.8.0_232]
at
java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:338)
~[?:1.8.0_232]
at
java.util.concurrent.CompletableFuture.uniRelay(CompletableFuture.java:925)
~[?:1.8.0_232]
at
java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:967)
~[?:1.8.0_232]
at
java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:940)
~[?:1.8.0_232]
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
~[?:1.8.0_232]
at
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
~[?:1.8.0_232]
at
org.apache.pulsar.client.impl.ClientCnx.handleGetSchemaResponse(ClientCnx.java:713)
~[org.apache.pulsar-pulsar-client-original-2.4.2.jar:2.4.2]
at
org.apache.pulsar.common.protocol.PulsarDecoder.channelRead(PulsarDecoder.java:303)
~[org.apache.pulsar-pulsar-common-2.4.2.jar:2.4.2]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:323)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:297)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:799)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:433)
~[io.netty-netty-all-4.1.32.Final
.jar:4.1.32.Final]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:330)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:909)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
Caused by:
org.apache.pulsar.client.api.PulsarClientException$NotFoundException: No latest
schema found for topic test-topics
at
org.apache.pulsar.client.impl.PulsarClientImpl.lambda$preProcessSchemaBeforeSubscribe$23(PulsarClientImpl.java:744)
~[org.apache.pulsar-pulsar-client-original-2.4.2.jar:2.4.2]
at
java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:966)
~[?:1.8.0_232]
... 23 more
17:23:38.165 [public/default/influxdb-test-sink-1] ERROR
org.apache.pulsar.functions.instance.JavaInstanceRunnable -
[public/default/influxdb-test-sink:1] Uncaught exception in Java Instance
java.util.concurrent.CompletionException:
org.apache.pulsar.client.api.PulsarClientException$NotFoundException: No latest
schema found for topic test-topics
...
...```
----
2020-01-15 14:44:44 UTC - Abraham: @Abraham has joined the channel
----
2020-01-15 16:15:33 UTC - David Kjerrumgaard: It appears that the issue is with
the source topic not having a schema associated with it. `
```org.apache.pulsar.client.api.PulsarClientException$NotFoundException: No
lates
t schema found for topic test-topics```
----
2020-01-15 16:15:45 UTC - David Kjerrumgaard: How did you create the topic?
----
2020-01-15 16:30:49 UTC - Renato Mintz: @Renato Mintz has joined the channel
----
2020-01-15 17:38:07 UTC - Narciso Guillen: @Narciso Guillen has joined the
channel
----
2020-01-15 17:46:29 UTC - Roman Popenov: Is there a setting somewhere how many
messages a Function’s client in a pod can pre-fetch?
----
2020-01-15 18:44:30 UTC - Guilherme Perinazzo: Is 2.5.0 out?
----
2020-01-15 18:56:00 UTC - Fernando: no
----
2020-01-15 19:11:30 UTC - Guilherme Perinazzo: The v2.5.0 tag seems to be out
on github
----
2020-01-15 19:12:14 UTC - Roman Popenov: dun dun dun! :smile:
----
2020-01-15 19:19:00 UTC - Naby: I am using pulsar python client. I created a
producer to the topic: once with Schema and once without a Schema. Then, I
published messages to the topic. If there’s no schema, the connector doesn’t
start running. With a schema, the connector starts running, but, as soon as a
message is published into the topic, it fails and throws an error. I did the
same process as above, but, I used pulsar-admin cli to upload the schema. Same
problem happened.
----
2020-01-15 19:33:05 UTC - Fernando: the plot thickens
----
2020-01-15 19:36:40 UTC - Fernando: the milestones are complete
<https://github.com/apache/pulsar/milestones?state=closed>
----
2020-01-15 19:36:43 UTC - Fernando: so soon maybe?
----
2020-01-15 19:37:53 UTC - Matteo Merli: Yes, it's already approved. Announce
will go out shortly
party-parrot : Fernando, Guilherme Perinazzo, Mathieu Druart, Julien, Martin
Raymond
----
2020-01-15 19:39:33 UTC - ravi satya durga prasad Yenugula: Do PULSAR works
with ram less than or equal to 2 gb?
----
2020-01-15 19:40:13 UTC - Matteo Merli: Yes, you can tune it down to 128MB
(with few options)
----
2020-01-15 19:40:29 UTC - Matteo Merli: always depends on the expected load and
performance
----
2020-01-15 19:41:22 UTC - ravi satya durga prasad Yenugula: I am trying to
setup Plusar on a ec2 linux (1.5 gb ram) and its failing
----
2020-01-15 19:42:00 UTC - ravi satya durga prasad Yenugula: do you have any
setup article ? the document I am following is failing
----
2020-01-15 19:42:51 UTC - ravi satya durga prasad Yenugula: docker image dont
have any document to setup
----
2020-01-15 19:47:03 UTC - David Kjerrumgaard: Interesting. What is the error
you get when using a schema ?
----
2020-01-15 21:45:42 UTC - Naby: I have to check the logs, but, I moved on. I
wrote my own custom function instead of using built-in connector. It was easier.
----
2020-01-15 21:55:28 UTC - David Kjerrumgaard: Ok, can you share what you did
differently to avoid the issue? I want to file a JIRA to get the issue fixed
in the built-in connector
----
2020-01-15 22:11:35 UTC - Matteo Merli: check `conf/pulsar_env.sh` to set the
JVM memory limit
----
2020-01-15 22:11:53 UTC - Matteo Merli: change it to `-Xmx512MB` or so
----
2020-01-15 22:49:04 UTC - Olav Groenaas Gjerde: Make sure the EC2 has some swap
:sweat_smile:
----
2020-01-16 04:09:23 UTC - ran: @ran has joined the channel
----
