2020-10-19 12:32:54 UTC - Lari Hotari: @Addison Higham When does the cherry
picking onto the release branches happen? I see some commits cherry picked in
<https://github.com/apache/pulsar/commits/branch-2.6> . In particular, I'd be
interested in testing the fix for
<https://github.com/apache/pulsar/issues/8229> (1 commit).
I also hope the fixes for <https://github.com/apache/pulsar/issues/8138> (2
commits) get cherry picked to branch-2.6 (however I have already been able to
test them with a patched client that I have built locally).
Thank you
----
2020-10-19 12:34:24 UTC - Lari Hotari: I assume that there will be Docker
images available at <https://hub.docker.com/r/streamnative/pulsar/tags> once
the changes have been cherry picked to branch-2.6 . Is that so?
----
2020-10-19 15:45:12 UTC - Addison Higham: @Lari Hotari We just do the
cherry-picks periodically also we don't have that fully automated, but we are
happy to cut a release as needed.
It should be noted that building your own docker images is quite easy:
```# from the project root
mvn install -DskipTests
# that will take a while... once finished
cd docker
mvn install -DskipTests -Pdocker
# this creates images named apachepulsar/pulsar:latest
docker tag apachepulsar/pulsar:latest <myrepo>/pulsar:tag```
If you want to be able to try cherry picking that and build your own release
+1 : Lari Hotari
----
2020-10-19 15:48:36 UTC - Lari Hotari: Thanks @Addison Higham for the
instructions for building the docker image. I'll give that a try tomorrow.
----
2020-10-19 18:36:08 UTC - Gautam Kumar: Hi , We have upgraded from apache
pulsar 2.5.0 to 2.6.0 that has upgraded version 3.5.7 of zookeeper (on AWS
ec2 ) . After upgrade my zookeeper client-server ssl handshake is failing . It
is throwing `no cipher suites in common` error. Does zookeeper 3..5.7 have
different config for TLS ? . Can someone please help me on this ?
----
2020-10-19 18:36:15 UTC - Gautam Kumar: ```***
%% Initialized: [Session-657, SSL_NULL_WITH_NULL_NULL]
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
ssl: Ignoring alias localhost: key algorithm does not match
ssl: KeyMgr: no matching key found
epollEventLoopGroup-7-4, fatal error: 40: no cipher suites in common
javax.net.ssl.SSLHandshakeException: no cipher suites in common
%% Invalidated: [Session-657, SSL_NULL_WITH_NULL_NULL]
epollEventLoopGroup-7-4, SEND TLSv1.2 ALERT: fatal, description =
handshake_failure
epollEventLoopGroup-7-4, WRITE: TLSv1.2 Alert, length = 2
epollEventLoopGroup-7-4, fatal: engine already closed. Rethrowing
javax.net.ssl.SSLHandshakeException: no cipher suites in common
epollEventLoopGroup-7-4, called closeOutbound()
epollEventLoopGroup-7-4, closeOutboundInternal()
epollEventLoopGroup-7-4, called closeInbound()
epollEventLoopGroup-7-4, fatal: engine already closed. Rethrowing
javax.net.ssl.SSLException: Inbound closed before receiving peer's
close_notify: possible truncation attack?
epollEventLoopGroup-7-4, called closeOutbound()
epollEventLoopGroup-7-4, closeOutboundInternal()```
----
2020-10-19 18:38:08 UTC - Gautam Kumar: Client: pulsar_env.sh
```-Dzookeeper.ssl.hostnameVerification=false
-Dzookeeper.clientCnxnSocket=org.apache.zookeeper.ClientCnxnSocketNetty
-Dzookeeper.client.secure=true
-Dzookeeper.sasl.client=false
-Dzookeeper.ssl.keyStore.location=/opt/my-ca/bookie.keystore.jks
-Dzookeeper.ssl.keyStore.password=xxxxxx
-Dzookeeper.ssl.trustStore.location=/opt/my-ca/bookie.truststore.jks
-Dzookeeper.ssl.trustStore.password=xxxxxx```
----
2020-10-20 05:15:06 UTC - Lari Hotari: I wonder what is the correct way to
setup Pulsar development in IntelliJ? When I try running a test I get the error
message `java: package org.bouncycastle.asn1 does not exist` . I did find an
ugly workaround for this, by adding
``` <dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcpkix-jdk15on</artifactId>
<version>${bouncycastle.version}</version>
</dependency>
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-ext-jdk15on</artifactId>
<version>${bouncycastle.version}</version>
</dependency>```
to `pulsar-client-messagecrypto-bc/pom.xml` temporarily while working on the
source code in IntelliJ, but this seems wrong. Is there a better way to solve
this issue while working on Pulsar source code and opensource contributions?
----
2020-10-20 05:16:35 UTC - Ali Ahmed: This is intellij limitation I don’t think
there is a workaround
----