You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Apache Pulsar Slack <ap...@gmail.com> on 2020/05/06 09:11:05 UTC
Slack digest for #dev - 2020-05-06
2020-05-05 13:07:59 UTC - Nicolò Paganin: Hi @Sijie Guo, a question: is there a way to debug pulsar sources? We would like to give out contribute developing fetaures that are needed in our project. I found out a this page <https://pulsar.apache.org/en/contributing/> but there is not an answer. I already compiled the project and developed some modification for pulsar function, but I debugged using the log (printing values). I would like to know if there is a way to debug using Intellij or any other IDE.
Thanks
----
2020-05-05 13:15:49 UTC - Gilles Barbier: @Sijie Guo I’ve been doing some digging, and you are right, it’s an Avro issue
----
2020-05-05 15:39:37 UTC - David Kjerrumgaard: @Nicolò Paganin You can test them using the LocalRunner. <https://pulsar.apache.org/docs/en/functions-debug/#debug-with-localrun-mode>. Just use a `SourceConfig` instead of the `FunctionConfig` but everything else is the same.
----
2020-05-05 15:40:58 UTC - Nicolò Paganin: @David Kjerrumgaard I am not developing pulsar functions.. I am developing pulsar itself, the function-worker module… I would like, if possibile, to debug pulsar itself
----
2020-05-05 15:41:43 UTC - David Kjerrumgaard: @Nicolò Paganin My bad, I thought you were developing a Pulsar IO source connector.
----
2020-05-05 15:41:53 UTC - Nicolò Paganin: :slightly_smiling_face:
----
2020-05-05 15:42:17 UTC - Shivji Kumar Jha: 1. You could write a Junit test and run it in debug mode.
2. You could run this file (or another one in the same package)
```PulsarBrokerStarter.java```
----
2020-05-05 15:43:31 UTC - Shivji Kumar Jha: I generally see errors like this when i have a misconfiguration or bad network. Can you verify the network with telent perhaps?
```Error Checking/Getting Partition Metadata while creating producer on <persistent://public/default/my-topic> -- 5```
----
2020-05-05 16:07:07 UTC - Nicolò Paganin: ok thanks :slightly_smiling_face: I will look at it
----
2020-05-05 16:52:49 UTC - Robert Yokota: @Robert Yokota has joined the channel
----
2020-05-05 17:33:44 UTC - Sijie Guo: Cool. Good to know.
----
2020-05-05 17:39:59 UTC - Sajith Sebastian: Hello
Wanted to enable TLS 1.2 secure communication between broker and clients, followed the instructions documented at <https://pulsar.apache.org/docs/en/security-tls-transport/>
Getting the following error when a client tries to establish a connection. Really appreciate any help/direction. Note the rejected cipher is already installed. JCE has default as well as bouncy castle cipher providers.
----
2020-05-05 17:41:28 UTC - Sajith Sebastian: 17:36:01.438 [pulsar-io-22-2] ERROR org.apache.pulsar.common.util.SslContextAutoRefreshBuilder - Execption while trying to refresh ssl Context failed to set cipher suite: [ECDH-ECDSA-AES128-GCM-SHA256]
<http://javax.net|javax.net>.ssl.SSLException: failed to set cipher suite: [ECDH-ECDSA-AES128-GCM-SHA256]
at io.netty.handler.ssl.ReferenceCountedOpenSslContext.<init>(ReferenceCountedOpenSslContext.java:259) ~[io.netty-netty-handler-4.1.43.Final.jar:4.1.43.Final]
at io.netty.handler.ssl.OpenSslContext.<init>(OpenSslContext.java:43) ~[io.netty-netty-handler-4.1.43.Final.jar:4.1.43.Final]
at io.netty.handler.ssl.OpenSslServerContext.<init>(OpenSslServerContext.java:346) ~[io.netty-netty-handler-4.1.43.Final.jar:4.1.43.Final]
at io.netty.handler.ssl.OpenSslServerContext.<init>(OpenSslServerContext.java:334) ~[io.netty-netty-handler-4.1.43.Final.jar:4.1.43.Final]
at io.netty.handler.ssl.SslContext.newServerContextInternal(SslContext.java:471) ~[io.netty-netty-handler-4.1.43.Final.jar:4.1.43.Final]
at io.netty.handler.ssl.SslContextBuilder.build(SslContextBuilder.java:457) ~[io.netty-netty-handler-4.1.43.Final.jar:4.1.43.Final]
at org.apache.pulsar.common.util.SecurityUtility.createNettySslContextForServer(SecurityUtility.java:115) ~[org.apache.pulsar-pulsar-common-2.5.0.jar:2.5.0]
at org.apache.pulsar.common.util.NettySslContextBuilder.update(NettySslContextBuilder.java:44) ~[org.apache.pulsar-pulsar-common-2.5.0.jar:2.5.0]
at org.apache.pulsar.common.util.NettySslContextBuilder.update(NettySslContextBuilder.java:31) ~[org.apache.pulsar-pulsar-common-2.5.0.jar:2.5.0]
at org.apache.pulsar.common.util.SslContextAutoRefreshBuilder.get(SslContextAutoRefreshBuilder.java:90) [org.apache.pulsar-pulsar-common-2.5.0.jar:2.5.0]
at org.apache.pulsar.broker.service.PulsarChannelInitializer.initChannel(PulsarChannelInitializer.java:67) [org.apache.pulsar-pulsar-broker-2.5.0.jar:2.5.0]
at org.apache.pulsar.broker.service.PulsarChannelInitializer.initChannel(PulsarChannelInitializer.java:32) [org.apache.pulsar-pulsar-broker-2.5.0.jar:2.5.0]
at io.netty.channel.ChannelInitializer.initChannel(ChannelInitializer.java:129) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.ChannelInitializer.handlerAdded(ChannelInitializer.java:112) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.AbstractChannelHandlerContext.callHandlerAdded(AbstractChannelHandlerContext.java:964) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.DefaultChannelPipeline.callHandlerAdded0(DefaultChannelPipeline.java:613) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.DefaultChannelPipeline.access$100(DefaultChannelPipeline.java:46) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.DefaultChannelPipeline$PendingHandlerAddedTask.execute(DefaultChannelPipeline.java:1475) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.DefaultChannelPipeline.callHandlerAddedForAllHandlers(DefaultChannelPipeline.java:1127) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.DefaultChannelPipeline.invokeHandlerAddedIfNeeded(DefaultChannelPipeline.java:654) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.AbstractChannel$AbstractUnsafe.register0(AbstractChannel.java:503) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.AbstractChannel$AbstractUnsafe.access$200(AbstractChannel.java:416) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.AbstractChannel$AbstractUnsafe$1.run(AbstractChannel.java:475) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [io.netty-netty-common-4.1.43.Final.jar:4.1.43.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:510) [io.netty-netty-common-4.1.43.Final.jar:4.1.43.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:518) [io.netty-netty-transport-4.1.43.Final.jar:4.1.43.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1050) [io.netty-netty-common-4.1.43.Final.jar:4.1.43.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [io.netty-netty-common-4.1.43.Final.jar:4.1.43.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [io.netty-netty-common-4.1.43.Final.jar:4.1.43.Final]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_151]
Caused by: java.lang.IllegalArgumentException: unsupported cipher suite: ECDH-ECDSA-AES128-GCM-SHA256(ECDH-ECDSA-AES128-GCM-SHA256)
at io.netty.handler.ssl.CipherSuiteConverter.convertToCipherStrings(CipherSuiteConverter.java:470) ~[io.netty-netty-handler-4.1.43.Final.jar:4.1.43.Final]
at io.netty.handler.ssl.ReferenceCountedOpenSslContext.<init>(ReferenceCountedOpenSslContext.java:246) ~[io.netty-netty-handler-4.1.43.Final.jar:4.1.43.Final]
... 29 more
----
2020-05-05 18:21:48 UTC - Addison Higham: <https://github.com/apache/pulsar/pull/6881> <- a 1 line fix for a bug that has been causing me issues for months now... phew!
+1 : Shivji Kumar Jha
----
2020-05-05 18:36:53 UTC - Luke Lu: Is the main functionality (besides deployment) of pulsar functions over regular pulsar clients the global (for the same function across the nodes) context API? Is it possible (or how hard) to use pulsar function api directly without `pulsar-admin functions create...`? We would rather use k8s to deploy pulsar function pods directly (without using pulsar function-worker)
----
2020-05-05 22:37:21 UTC - Luke Lu: If the api allows us to register any pulsar function client itself, then the client can manage dependencies themselves without function workers. `querystate` is still useful though. This would allow people to develop pulsar functions in any languages with arbitrary dependencies without having to go through function workers.
----
2020-05-05 23:07:52 UTC - Santhi: @Santhi has joined the channel
----