pulsar

Due this I am unable to save the Enviroment

Change to the directory containing this file

here are the commands I ran
```docker pull apachepulsar/pulsar-manager:v0.1.0
docker run -it -p 9527:9527 -e REDIRECT_HOST=<http://192.168.0.104> -e REDIRECT_PORT=9527 -e DRIVER_CLASS_NAME=org.postgresql.Driver -e URL='jdbc:<postgresql://127.0.0.1:5432/pulsar_manager>' -e USERNAME=pulsar -e PASSWORD=pulsar -e LOG_LEVEL=DEBUG apachepulsar/pulsar-manager:v0.1.0 /bin/sh```
and I got a http  inter error
```<!doctype html>&lt;html lang="en"&gt;&lt;head&gt;&lt;title&gt;HTTP Status 500 – Internal Server Error&lt;/title&gt;&lt;style type="text/css"&gt;h1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} h2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} h3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} body {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} p {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;} a {color:black;} a.name {color:black;} .line {height:1px;background-color:#525D76;border:none;}&lt;/style&gt;&lt;/head&gt;&lt;body&gt;&lt;h1&gt;HTTP Status 500 – Internal Server Error&lt;/h1&gt;&lt;/body&gt;&lt;/html&gt;```
Later I used a community provided docker file
and ran the `docker-compose up`

It seems to me that it could be useful speeding up segment processing in brokers reading/writing segments, replication across brokers, migration to second tier storage, and last but not least prestoDB. I say "speeding up" but take that with a huge grain of salt: I have no idea how fast Arrow or Bookkeeper for that matter is. The interesting aspect is the single, efficient format for all kinds of integrations

You can see the FQDN of a broker belonging to the default namespace (which in my cluster it does not exist, there is only a broker within the namespace *pulsar1*)... but when i want to run the collector.. i specifically put the *pulsar1* namespace:

This is the output of the last two commands you mentioned:

If i do a nslookup to the broker name.. i also get this:

And finally.. this is the env variable passed when the pulsar-dashboard it's deployed:

the following properties had been defined in log4j2.yaml

I keep seeing the following error while trying to run build.sh in <https://github.com/apache/pulsar/blob/master/docker/build.sh>

<@UTN8994KY> 

It seems like you're expecting all of these operations to be synchronous and thread blocking. Pulsar is designed with parallelism and asynchronous I/O in mind. Think of it like a tree of dominoes falling. You can kick off many operations in parallel from a single event.

Attached are 3 sample files:
1. avro_schema -  the simplified avro schemas
2. pulsar_simplified_object - the pulsar generated schema
3. kafka_simplified_object - the confluent generated schema (this is what we expected pulsar would create)

Hi Guys, I am using the current dot client Pulsar, before I used and found some issue related to the consumer, consumer is not consuming as per the producers producing rate, afer discussion with <@U9L5AQLE8> and related to the issue of consumer that in dot client. now it's working far more better even better than websocket consumer, before websocket request rate was 5-10 seconds now after using dot client it has reduced to some milliseconds to 1 sec.

Hello.
We’ve increased number of brokers from 3 to 12 to have better availability when broker fails as <@U6E5YMRKR> suggested.

But after that latency for some operations increased significantly (For example `ConsumerBuilder.subscribe()` increased from 0.6s to 1.5s)

What is causing this latency growth? Can it be tuned with this number of brokers?

Also we’ve noticed that zookeeper is more loaded after adding brokers (see attached). Is this normal? What can we do with this to decrease latency?

Zookeeper node has 12 CPU cores, 64GB of RAM, CPU idle > 75%
On each zookeeper node there are also deployed 1 broker and 1 bookie.

System load is not high: after adding more brokers it is never more than 5 (less than 50%).
There are almost no processes blocked by I/O.

Also we have disabled fsync in Zookeeper.

All this looks like problem is not related to hardware/disk speed.

I've got some less clean results here, using the actual topic that's slow. I've just connected pulsar-perf using our actual subscription. This subscription has a backlog of around 400mm currently.

Here's the main stats from me testing last night. This is good pulsar perf behavior.

Here's a brief window of me consuming off the topic. Has about 1 billion messages in backlog total, ~230m per partition

And here's the trace from the consumer <@U6E5YMRKR>

像ignite这样的框架就有对类加载器的切换，我看pulsar有很多引用类的静态成员和方法，在osgi框架下会有我说的问题

<https://pulsar.apache.org/docs/ko-KR/standalone>

Run Functions-worker separately，Configure Proxies for Functions-workers，functionWorkerWebServiceURL/functionWorkerWebServiceURLTLS  like this，Port that discovery service listen on 8082,  then start pulsar proxy，but curl <http://hostname:8082/admin/v2/worker/cluster>

<@UUX7KS9EC> If you are using the LocalRunner, then you can configure the input schema type as shown in this snippet.