2019-06-17 11:15:18 UTC - dipali: i tried with existing ones , it worked. thanks
----
2019-06-17 13:41:29 UTC - Ivan Kelly: well, yes. the message gets compressed 
before it even hits the broker. it only get decompressed then at the consumers. 
Theres no point in doing any more compression as the reduction in size would be 
minimal.
----
2019-06-17 14:21:41 UTC - Aaron: What TLS version is needed for TLS 
authentication with a java client?
----
2019-06-17 14:39:13 UTC - David Kjerrumgaard: @Aaron Pulsar supports TLSv1, 
TLSv1.1 and TLSv1.2.
----
2019-06-17 15:00:54 UTC - Aaron: I am getting a connection refused error when 
running my pulsar cli client with TLS authentication. I followed all the steps 
here - 
<https://pulsar.apache.org/docs/en/security-tls-authentication/#tls-authentication-overview>,
 and edited the broker.conf file and restarted my standalone pulsar server. 
There is nothing listening on port 6651 (where the Broker for TLS should 
be...). Am I missing something?
----
2019-06-17 15:06:13 UTC - David Kjerrumgaard: @Aaron For the standalone 
cluster, you need to make the changes in the `standalone.conf` file instead of 
the `broker.conf` file
----
2019-06-17 15:08:21 UTC - Aaron: So I should add the configuration options 
listed here - 
<https://pulsar.apache.org/docs/en/security-tls-transport/#broker-configuration>
 to the standalone.conf file?
----
2019-06-17 15:21:50 UTC - David Kjerrumgaard: Yes
+1 : Aaron
----
2019-06-17 16:05:07 UTC - Ben: @Ben has joined the channel
----
2019-06-18 00:24:36 UTC - Patrick Lange: I am using docker-compose to run 
pulsar in standalone mode together with dashboard. However, my dashboard stays 
empty until I run `bin/pulsar-admin clusters list` inside the pulsar container. 
 Is this normal behavior?

```
# docker-compose.yaml
version: "3.7"
services:
  apache-pulsar:
    hostname: apache-pulsar
    image: apachepulsar/pulsar:2.3.2
    command: ["bin/pulsar", "standalone"]
    ports:
      - "6650:6650"
      - "8080:8080"
  apache-pulsar-dashboard:
    hostname: apache-pulsar-dashboard
    image: apachepulsar/pulsar-dashboard
    ports:
      - "80:80"
    environment:
      - SERVICE_URL=<http://apache-pulsar:8080>
```
----
2019-06-18 00:32:07 UTC - David Kjerrumgaard: @Patrick Lange That doesn't seem 
right.  Can you file a JIRA for this?
----
2019-06-18 00:40:54 UTC - Patrick Lange: @David Kjerrumgaard sure, maybe this 
is related to 
<https://issues.apache.org/jira/projects/PULSAR/issues/PULSAR-2?filter=allopenissues>
----
2019-06-18 00:44:14 UTC - David Kjerrumgaard: @Patrick Lange That was actually 
a different issue, looking back at the Slack conversation.
----
2019-06-18 00:50:46 UTC - Patrick Lange: @David Kjerrumgaard since I don’t have 
an account i can only create a github issue
+1 : David Kjerrumgaard
----
2019-06-18 01:19:39 UTC - Patrick Lange: Another strange thing, I have created 
a new namespace (`test-namespace`) in the `public` tenant. Then I created a 
persistent topic and two non-persistent topics.

When trying to see if my topics exist, I noticed the following:

1) The dashboard only shows the persistent topic.
2) `bin/pulsar-admin persistent list public/test-namespace` shows all 3 topics
3) `bin/pulsar-admin non-persistent list public/test-namespace` shows all 3 
topics
4) 
`/admin/v2/non-persistent/public/test-namespace/admin/v2/persistent/public/test-namespace/`
 works as expected and shows the persistent topic
5) 
`/admin/v2/non-persistent/public/test-namespace/admin/v2/non-persistent/public/test-namespace/`
 wors as exppected and shows the two non-persistent topics
6) `bin/pulsar-admin list public/test-namespace` only shows the persistent topic
7) `bin/pulsar-admin topics list public/test-namespace` shows persistent and 
non-persistent topics
----
2019-06-18 01:20:15 UTC - Patrick Lange: I am not very familiar with the 
different commands so maybe this is supposed to be like this but it is 
certainly confusing.
----
2019-06-18 04:48:27 UTC - vikash: No  able  to  build  Apache  Pulsar  Cpp  on  
window
----
2019-06-18 04:48:49 UTC - vikash: getting  incorrect   no  of  argument
----
2019-06-18 04:48:54 UTC - vikash: 
----
2019-06-18 05:41:17 UTC - vikash: line  54  and  line  58
----
2019-06-18 05:41:18 UTC - vikash: 
<https://github.com/apache/pulsar/blob/master/pulsar-client-cpp/lib/CMakeLists.txt>
----

Reply via email to